Hygraph
HygraphReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
714 reviews
from
External reviews are not included in the AWS star rating for the product.
A CMS designed for large-scale multilingual content management
What do you like best about the product?
Hygraph is much more than a classic CMS: it is a structuring tool for teams working on complex international sites. As a copywriter specialized in localization, I use it within a team of 5-6 consultants led by the marketing department of a tech company recognized in its sector. The interface provides a clear and simultaneous view of content in all languages, which significantly reduces errors in tone, style, or inconsistency. The system also allows you to revisit any text, even months later, to make updates without losing track.
Before Hygraph, we used huge Excel files to manage translated content. Now, everything happens directly in the site's environment, without the need for manual importation. We work faster, more cleanly. For a company managing hundreds of pages, Hygraph is an indispensable advancement.
Before Hygraph, we used huge Excel files to manage translated content. Now, everything happens directly in the site's environment, without the need for manual importation. We work faster, more cleanly. For a company managing hundreds of pages, Hygraph is an indispensable advancement.
What do you dislike about the product?
Hygraph has a significant learning curve for new users, especially for those coming from more traditional environments like WordPress. The interface may seem a bit technical at first. Additionally, some publishing or updating actions still lack fluidity, particularly when working on mirrored content in multiple languages. Improved ergonomics for managing editorial workflows would be a plus.
What problems is the product solving and how is that benefiting you?
Hygraph has completely transformed our way of managing multilingual content on a large scale. Before, we had to juggle with endless Excel spreadsheets and management systems poorly suited to the needs of fine localization. This generated errors, considerable time loss, and a total lack of overall vision.
Today, Hygraph allows us to centralize and structure the management of hundreds of pages in multiple languages, while maintaining perfect editorial consistency. We gain in productivity, clarity, and content control. No more need to import/export texts: everything is done directly in the site's environment. It's a real leap forward for any team working on an international website.
Today, Hygraph allows us to centralize and structure the management of hundreds of pages in multiple languages, while maintaining perfect editorial consistency. We gain in productivity, clarity, and content control. No more need to import/export texts: everything is done directly in the site's environment. It's a real leap forward for any team working on an international website.
Still one of the best headless cms’s ive used
What do you like best about the product?
I’ve been using hygraph for a few projects now and this is still one of the easiest content management systems I’ve used. From model creation down to editing the features allow quick deployment and updates whilst development functionality is being built.
The api is easy and fast to use and the scheduled publishing and custom components have gone down a hit. I’ve also used the remote api schemes integration and this has saved multiple integrations per site as well as any downtime due to the caching behaviours on this.
The api is easy and fast to use and the scheduled publishing and custom components have gone down a hit. I’ve also used the remote api schemes integration and this has saved multiple integrations per site as well as any downtime due to the caching behaviours on this.
What do you dislike about the product?
One thing I’d like to improve on hygraph is the ability to try new features outside of paid plans. It’s hard for developers to try and test these out without having a chat with an account manager and then being tied into a limited trial. Personal time doesn’t always fit within trial windows and this is annoying
What problems is the product solving and how is that benefiting you?
We have an agnostic front end product built in next js and react. Using hygraph in the way we do gives us amazing flexibility and due to the api coupled with graphql generation libraries a really smooth integration. We don’t have to worry about the third party cms just the code we’re building. Any updates to schemas we can just regenerate and focus on anything new
It saved us days of developing a backend
What do you like best about the product?
With Hygraph, we can create content APIs and complex data structures in no time, with drag-and-drop ease. The information on our online course landing pages is almost entirely delivered by Hygraph.
What do you dislike about the product?
The GraphQL API playground area is a bit complex and confusing for non-technical users.
What problems is the product solving and how is that benefiting you?
We use it to support the content deliverability to our online courses landing pages on deploy... With Hygraph, our company's teaching staff can register courses information directly into the system, without having to handoff content to the technical area.
Empowered dynamic software with a Headless CMS
What do you like best about the product?
1. Headless Architecture with GraphQL API
2. Flexible Content Modeling
3. Localization and Multi-environment Support
4. Integration Ready
2. Flexible Content Modeling
3. Localization and Multi-environment Support
4. Integration Ready
What do you dislike about the product?
Sometimes editing content on multiple environments seem overwhelming.
What problems is the product solving and how is that benefiting you?
Deployment-less content management
Easy to use & flexible CMS
What do you like best about the product?
What I particularly appreciate is Hygraph's approach to structured content modeling, it allows us to think future-proof and create reusable content pieces that scale well as we grow. The documentation is solid, and support has been responsive whenever we’ve needed help.
What do you dislike about the product?
One area of improvement could be around more advanced native workflows or approval processes for editorial teams, but overall, Hygraph has allowed us to move faster and manage complex content relationships with ease.
What problems is the product solving and how is that benefiting you?
I work in the real estate and property development industry so we deal with a large amount of constantly changing property data, listings, images, agent profiles, neighborhood content, and more. All of which need to be presented consistently across our website, mobile apps, and internal tools. Traditional CMS platforms made this difficult, especially when trying to reuse content across different channels or maintain complex relationships between properties, agents, and locations.
Hygraph delivers great flexibility and user experience for modern content delivery.
What do you like best about the product?
As Head of IT, I’ve found Hygraph to be a highly effective and modern content platform. Its ease of use stands out—both developers and content editors were productive with minimal onboarding. The implementation process was fast and smooth, thanks to excellent documentation and a GraphQL-first approach.
Customer support has been consistently responsive and technically competent, resolving most issues within a day. We use Hygraph daily across multiple teams, and its features—from localization to role management and API flexibility—meet the demands of both content operations and scalable development.
Integration was seamless with our architecture and services like Vercel and TypeSense. Hygraph has become a core part of our stack, balancing flexibility, performance, and usability.
Overall: Reliable, scalable, and built with both dev and content teams in mind.
Customer support has been consistently responsive and technically competent, resolving most issues within a day. We use Hygraph daily across multiple teams, and its features—from localization to role management and API flexibility—meet the demands of both content operations and scalable development.
Integration was seamless with our architecture and services like Vercel and TypeSense. Hygraph has become a core part of our stack, balancing flexibility, performance, and usability.
Overall: Reliable, scalable, and built with both dev and content teams in mind.
What do you dislike about the product?
The greatest challenge for us was directly connected with usage limits. Costs can scale sharply with API operations, content entries, and user roles. We’ve had to monitor usage closely to avoid unexpected overages—especially around content models and API limits. It’s easy to hit caps on lower-tier plans, which forces earlier-than-expected upgrades. With that said Hygraph delivers great flexibility and user experience for modern content delivery, but requires careful cost management and architecture planning to scale effectively
What problems is the product solving and how is that benefiting you?
Hygraph empowers both technical and non-technical teams to collaborate seamlessly through an intuitive UI and structured content modeling.
This reduces dependency on developers for everyday content updates, speeding up publishing cycles and freeing up IT resources for higher-impact work.
This reduces dependency on developers for everyday content updates, speeding up publishing cycles and freeing up IT resources for higher-impact work.
Solid experience
What do you like best about the product?
My biggest work with Hygraph was the asset migration and felt pretty smooth with it and also the hygraph team was always helpful and easy to reach out
What do you dislike about the product?
Currently I have no negative points, although , as all tools, there might be something that I will dislike the more I work with it.
What problems is the product solving and how is that benefiting you?
Hard to tell as im just a developer/consultant but I'm glad I never had perfomances issues with fetching data
H
What do you like best about the product?
Hygraph offers a very intuitive user interface and powerful API, which makes content modeling and data querying extremely efficient. The flexible schema design and localization features are also a huge plus
What do you dislike about the product?
Some advanced features, like content staging or granular user permissions, can be a bit tricky to configure or are limited in lower-tier plans.
What problems is the product solving and how is that benefiting you?
Hygraph solves the problem of managing and delivering structured content across multiple channels. With its headless and API-first approach, we can easily build and scale frontends independently of the backend. This speeds up development, improves collaboration between teams, and ensures content is consistent and reusable across platforms like web, mobile, and apps
Powerful Headless CMS with Excellent Support, but Room for Improvement
What do you like best about the product?
We've been using Hygraph as our content management system for some time now, and overall it's been a very solid choice. The interface is intuitive and user-friendly, making it easy for both developers and non-technical team members to work with content efficiently. Depending on your setup, Hygraph offers a lot of flexibility and can support quite complex content structures—which has been a big plus for our growing content operations.
Another highlight is the support: responses are fast, friendly, and usually spot-on. It’s clear that the team behind Hygraph takes customer feedback seriously.
Another highlight is the support: responses are fast, friendly, and usually spot-on. It’s clear that the team behind Hygraph takes customer feedback seriously.
What do you dislike about the product?
That said, there are occasional hiccups. Every now and then, the studio UI experiences issues that can block our work temporarily. It’s nothing catastrophic, but when it happens, it’s disruptive. Also, pricing-wise, Hygraph isn’t the cheapest option out there—especially if you’re scaling up or using many advanced features.
Bottom line: Hygraph is a great CMS if you're looking for a modern, headless approach and value strong support and flexibility. Just keep in mind that you’re paying a premium, and be prepared for the occasional studio glitch.
Bottom line: Hygraph is a great CMS if you're looking for a modern, headless approach and value strong support and flexibility. Just keep in mind that you’re paying a premium, and be prepared for the occasional studio glitch.
What problems is the product solving and how is that benefiting you?
Hygraph helps us streamline the entire content publishing process. It allows us to quickly build and update pages—whether it's landing pages, blog articles, or other types of content—using reusable sections and a flexible content model. Even team members who don’t regularly work with CMS platforms can easily make changes without needing developer support. That ease of use has really improved our agility and helped us launch content faster across different channels.
More than just a headless CMS. Platform for growht!
What do you like best about the product?
We use HyGraph as CMS for our media organisation. I love that as our organisation grows and we add shows, people, and explore different concepts, we can adjust both content and entities as we move along. It is flexible, lean, and fast, and does not require backend changes, upgrades, or any other technical fuss. The API playground is also extremely useful when integrating the system with the rest of our stack. The freemium tier also allows us to do a lot, and that is helpful and enables us to explore and integrate the product before we need to scale up our engagement further.
What do you dislike about the product?
UI can sometimes feel sluggish, and I would love that the content would be a bit more in focus or exposed than the editing of entities and models.
What problems is the product solving and how is that benefiting you?
We use HyGraph as our headless CMS. We are media organisation. So we store things such as episodes, guests, staff, sponsors, shows etc...
showing 71 - 80