What is Hygraph and how does it work in a workout tracker project?
Hygraph is a GraphQL-native headless CMS used to store editorial content, such as workout movements and programming, in fitness applications. In the referenced workout tracker project, Hygraph manages structured workout data, which is combined with user activity and authentication data from Hasura and Auth0. The integration enables flexible schema modeling and content federation, allowing developers to merge multiple GraphQL schemas for a unified API. Note: Hygraph does not store user authentication or activity data; these are managed by Hasura and Auth0.
Does Hygraph support REST and GraphQL APIs?
Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs for content delivery and management. This allows developers to integrate Hygraph with any frontend or application. For more details, see Hygraph API documentation. Note: Only content-related APIs are managed by Hygraph; authentication and user activity APIs are handled by Hasura and Auth0 in the workout tracker project.
What technical documentation is available for Hygraph?
Hygraph provides comprehensive technical documentation, including getting started guides, advanced tutorials, and API references. These resources help users set up Hygraph, model schemas, and integrate with other platforms. Access documentation at Hygraph Docs. Note: Documentation for integrating with Auth0 and Hasura is not provided by Hygraph directly.
Features & Capabilities
What are the key features of Hygraph for fitness and workout tracking apps?
Hygraph offers flexible schema modeling, GraphQL-native architecture, content federation, and support for union types. In the workout tracker example, Hygraph enables storing base workout movements (e.g., Pushup), repetition-based movements, and equipment-based movements. Its editorial UI allows non-technical users to manage workout content, while developers can merge schemas with Hasura for unified APIs. Note: Hygraph does not provide built-in user authentication or activity tracking; these are handled by Auth0 and Hasura.
Does Hygraph support integration with other platforms like Hasura and Auth0?
Yes, Hygraph can be integrated with platforms like Hasura and Auth0. In the workout tracker project, editorial content is managed in Hygraph, while user authentication is handled by Auth0 and user activity by Hasura. Hasura's remote schema joins allow merging Hygraph's API with application data for a unified experience. Note: Integration setup requires developer expertise and is not natively automated by Hygraph.
What integrations are available for Hygraph?
Hygraph offers integrations with Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. These integrations extend content management, personalization, analytics, and workflow automation. For a full list, visit Hygraph Marketplace Apps. Note: Not all integrations are relevant for fitness apps; check compatibility before implementation.
Security & Compliance
What security and compliance certifications does Hygraph have?
Hygraph is SOC 2 Type 2 certified (since August 2022), uses ISO 27001-certified providers and data centers, and is GDPR and CCPA compliant. It offers encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. For more details, see Hygraph Security Features. Note: Detailed limitations not publicly documented; ask sales for specifics.
Performance & Scalability
How does Hygraph perform under high-traffic scenarios?
Hygraph's global CDN minimizes latency and supports region-based hosting. It handled 3.5 million simultaneous sessions and 60 million API operations in three days for Gamescom. Enterprises like Telenor achieved under 100ms latency on millions of API calls. Smart Edge Cache and advanced caching optimize content delivery. Note: Best fit for content-heavy applications; teams needing real-time transactional data may want to consider alternatives.
Implementation & Onboarding
How long does it take to implement Hygraph and start using it?
Implementation timelines depend on project complexity. Simple use cases can start within a few days using pre-configured starter projects. Structured onboarding includes introduction calls, account provisioning, and technical kickoffs. Extensive documentation, webinars, and community support are available. For more details, see Hygraph Getting Started Guide. Note: Complex integrations (e.g., with Hasura/Auth0) may require additional development time.
Use Cases & Benefits
Who can benefit from using Hygraph?
Hygraph is suited for marketing/content teams, product managers, developers, and enterprise IT teams. It is used in industries such as technology, consumer goods, telecommunications, media, retail, e-commerce, and scientific publishing. Case studies include Samsung (15% engagement lift), Komax (3x faster time-to-market), Gamescom (3.5M sessions), and Dr. Oetker (content for 40 countries). Note: Best fit for organizations needing scalable, multi-channel content management; teams requiring transactional data storage should consider alternatives.
What business impact can customers expect from using Hygraph?
Customers report up to 50% reduction in maintenance costs, 3x faster time-to-market (Komax), 20% higher monetization, and improved operational efficiency. Gamescom handled 3.5M simultaneous sessions, Samsung saw a 15% engagement lift, and Dr. Oetker manages content for 40 countries. Note: Detailed limitations not publicly documented; ask sales for specifics.
Pain Points & Problem Solving
What problems does Hygraph solve for fitness app developers?
Hygraph addresses dependency on developers for content updates, legacy tech stack modernization, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization challenges. In the workout tracker project, Hygraph enables flexible schema modeling and editorial content management. Note: Hygraph does not solve user authentication or activity tracking; these are handled by Auth0 and Hasura.
Customer Proof & Success Stories
Can you share specific case studies or success stories of Hygraph customers?
Yes. Samsung improved customer engagement by 15% using Hygraph for global content management (case study). Komax achieved 3x faster time-to-market (case study). Gamescom supported 3.5M simultaneous sessions and 60M API operations in three days (case study). Dr. Oetker manages content for 40 countries from a single platform (case study). Note: Results may vary based on implementation and use case.
Industry Coverage
What industries are represented in Hygraph's case studies?
Hygraph is used in technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media and entertainment (Gamescom), travel and hospitality (HolidayCheck), scientific publishing (GDCh), government/public sector (Statistics Finland), sports/events (DTM), and retail/e-commerce (Stobag). Note: Industry-specific limitations not documented; ask sales for details.
Build a Workout Tracker with Hygraph, Auth0 and Hasura
Warning, things are about to get meshy. Learn how to merge multiple GraphQL schema's together with Hasura's remote schema joins in this reference fitness app. We'll throw in user authenticated, too, just for fun.
If there's a cliche more pronounced than the perennial "starting a fitness resolution" only to abandon it later, it would be developers deciding to build their own fitness program/app instead of using an existing one. That being said, it is a very practical example of how we can solve common problems following well-established best-practices.
We've seen a rise in the popularity of micro-communities over the last years and the trend is likely to continue. Even massive social networks like Facebook excel, in part, thanks to the functionality of groups. People like forming micro-tribes in their day-to-day experiences and there will always be room for a new tribe to form. Embracing a lean architecture and best-of-breed service providers will help you build your community quickly and efficiently.
Our project combines two schemas. I will refer to them as the editorial content and the application content. For our exercise program, we'll store this content as editorial content in Hygraph. We want/need the flexibility of a robust data modeling solution like Hygraph to give us the kind of elegant schema that will play well with others. The second piece we need is application data such as user accounts, stored user activity, and exercise history. Application data will be stored in Hasura which will also act as our joining platform to combine the APIs together.
For this demo, we have created a website where you can sign-up, browse workouts, log a workout session, and browse your history.
This is the schema we’ll be building.
In our model we are create small entities composed of even smaller pieces. We are storing base workout movements like a Pushup, then we map that to either a repetition based movement such as "25 pushups" or something like an AMRAP movement (as many repetitions as possible within a minute). The base movements themselves are split between either a bodyweight movement or a movement that requires equipment. Our "repetition based" model, can take a base movement of either type, thanks to our new support for union types. Beyond that, we identify models that are stored in Hasura such as our user and user history.
The service map we will be building looks like this.
The core of our interaction/service model is that a user comes to the application and signs up for an account. This account is created in Auth0 which then creates a mirror of that account in Hasura via a webhook. The user then receives an auth token that includes additional permissions for the Hasura API. These permissions are passed via a bearer auth-token to Hasura in subsequent API requests to either log a new activity or to fetch workout details (in this case, our workout programming is behind an "auth wall" for members only.)
Once a user logs an activity, it creates a new entry in their user data in Hasura. When the user log data gets updated in Hasura, it triggers a webhook that updates Hygraph where our "workout PIM is" and updates a popularity field so that the workouts themselves could be queried based on popularity metrics without having to first authenticate and aggregate the total user data.
The power here lies in our merging of these two APIs into a unified one. We can use remote joins in Hasura to delegate part of the schema to another API which then lets us iterate our product data in isolation from our application data. This is an incredibly powerful paradigm and Hasura makes it quite trivial to create. In the figure below one can see how the two schemas come together to represent a final, queryable API.
I've again returned to the NextJS platform, as well as Vercel to host both the main application and a webhook service to handle incrementing our popularity field. I've talked before about the benefits of NextJS, and frankly, it's a great tool that I know how to use. But you can work with any stack you know how to use and the outcome will be the same. Our API has been designed to reflect product capability, not an implementation-specific coupling.
Enjoy the project, follow the guide and let us know what you think!
Blog Author
Jesse Martin
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.
Build a Workout Tracker with Hygraph, Auth0 and Hasura
Warning, things are about to get meshy. Learn how to merge multiple GraphQL schema's together with Hasura's remote schema joins in this reference fitness app. We'll throw in user authenticated, too, just for fun.
If there's a cliche more pronounced than the perennial "starting a fitness resolution" only to abandon it later, it would be developers deciding to build their own fitness program/app instead of using an existing one. That being said, it is a very practical example of how we can solve common problems following well-established best-practices.
We've seen a rise in the popularity of micro-communities over the last years and the trend is likely to continue. Even massive social networks like Facebook excel, in part, thanks to the functionality of groups. People like forming micro-tribes in their day-to-day experiences and there will always be room for a new tribe to form. Embracing a lean architecture and best-of-breed service providers will help you build your community quickly and efficiently.
Our project combines two schemas. I will refer to them as the editorial content and the application content. For our exercise program, we'll store this content as editorial content in Hygraph. We want/need the flexibility of a robust data modeling solution like Hygraph to give us the kind of elegant schema that will play well with others. The second piece we need is application data such as user accounts, stored user activity, and exercise history. Application data will be stored in Hasura which will also act as our joining platform to combine the APIs together.
For this demo, we have created a website where you can sign-up, browse workouts, log a workout session, and browse your history.
This is the schema we’ll be building.
In our model we are create small entities composed of even smaller pieces. We are storing base workout movements like a Pushup, then we map that to either a repetition based movement such as "25 pushups" or something like an AMRAP movement (as many repetitions as possible within a minute). The base movements themselves are split between either a bodyweight movement or a movement that requires equipment. Our "repetition based" model, can take a base movement of either type, thanks to our new support for union types. Beyond that, we identify models that are stored in Hasura such as our user and user history.
The service map we will be building looks like this.
The core of our interaction/service model is that a user comes to the application and signs up for an account. This account is created in Auth0 which then creates a mirror of that account in Hasura via a webhook. The user then receives an auth token that includes additional permissions for the Hasura API. These permissions are passed via a bearer auth-token to Hasura in subsequent API requests to either log a new activity or to fetch workout details (in this case, our workout programming is behind an "auth wall" for members only.)
Once a user logs an activity, it creates a new entry in their user data in Hasura. When the user log data gets updated in Hasura, it triggers a webhook that updates Hygraph where our "workout PIM is" and updates a popularity field so that the workouts themselves could be queried based on popularity metrics without having to first authenticate and aggregate the total user data.
The power here lies in our merging of these two APIs into a unified one. We can use remote joins in Hasura to delegate part of the schema to another API which then lets us iterate our product data in isolation from our application data. This is an incredibly powerful paradigm and Hasura makes it quite trivial to create. In the figure below one can see how the two schemas come together to represent a final, queryable API.
I've again returned to the NextJS platform, as well as Vercel to host both the main application and a webhook service to handle incrementing our popularity field. I've talked before about the benefits of NextJS, and frankly, it's a great tool that I know how to use. But you can work with any stack you know how to use and the outcome will be the same. Our API has been designed to reflect product capability, not an implementation-specific coupling.
Enjoy the project, follow the guide and let us know what you think!
Blog Author
Jesse Martin
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.