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.
Powerful Headless CMS With a Pricing Model That Scales Quickly
What do you like best about the product?
Hygraph’s API-first approach and performance are what stand out the most. The GraphQL API is fast, well-documented, and predictable, which makes integration with our frontend stack straightforward. Our developers can query exactly the data they need, which keeps the codebase cleaner and improves performance on the client side
What do you dislike about the product?
The main downside of Hygraph for us is the cost structure. As our usage and number of projects grow, the pricing can increase quickly, which makes it harder to justify compared to other headless CMS options in the market. We feel that some features that are essential for growing teams could be more accessible in lower tiers
What problems is the product solving and how is that benefiting you?
For us, Hygraph solves the problem of managing content for multiple client projects in a scalable way. We can create flexible schemas and environments per project, while still keeping everything under one platform. This makes it easier to maintain, update, and evolve content structures without rebuilding from scratch every time
Easy Team Collaboration & Clear Structure, but Missing AI Translation
What do you like best about the product?
- Very easy to use with a team
- Clear structure
- Integrated very easily with Vercel
- Clear structure
- Integrated very easily with Vercel
What do you dislike about the product?
- No AI translation for other languages
-
-
What problems is the product solving and how is that benefiting you?
- Making our website structure clear
- Making it easy to change things fast
- Translating into other languages
- Making it easy to change things fast
- Translating into other languages
Easy Content Editing in Minutes—Perfect for Non-Technical Marketing Teams
What do you like best about the product?
The ease of use with editing content within minutes. Perfect for a marketing team with little background knowledge in web development tools.
What do you dislike about the product?
It is limited from the variations you can apply to each page. Also in some cases the preview of the page layout doesn't work.
What problems is the product solving and how is that benefiting you?
As an internally built website, Hygraph allows for our marketing team to edit pages without the need to get product or eng involved.
Efficient, Developer-Friendly CMS with Room for Documentation Improvement
What do you like best about the product?
I like the way Hygraph makes things easier for developers. The ability to write GraphQL queries directly is a big plus, and it sometimes even allows me to avoid having an API. I appreciate the way you can manage data securely, especially with how you can set up specific permissions for tokens. The draft and publish features are great for previewing content deployments and display. I love that the platform is very user-friendly and easy to use.
What do you dislike about the product?
I guess the documentation could be improved. Maybe? I had a lot of issues writing GraphQL queries on the JavaScript site. Sometimes I struggle with the models and the relations I have to do to catch data from different tables together. Maybe the documentation could be something more step by step, ready to go. I was a bit lost in the beginning, and the docs were not helped me that much even because English is not my first language. It could be improved, especially for the onboarding of new users.
What problems is the product solving and how is that benefiting you?
I use Hygraph to quickly create and manage databases and APIs, ensuring the platform is interactive and secure. It simplifies managing event data, real-time updates, and controlling user access, making it easy and fun to engage with users.
Perfect for No-Code Designers—Simple and Powerful
What do you like best about the product?
This product has a simplicity that makes it work awesome for no-code designers and product designers. Easy to understand, even if you don't have dev skills.
What do you dislike about the product?
Hard to say, but I'm afraid the free tier could be a little more generous in terms of models, more than 20 could be helpful (I know you already are :D).
199$ for the second tier looks quite expensive for me, but it's something that I probably have to do if my MVPs start to work. If you guys can create a middle 50$ tier between free and the 199$ would be interesting.
199$ for the second tier looks quite expensive for me, but it's something that I probably have to do if my MVPs start to work. If you guys can create a middle 50$ tier between free and the 199$ would be interesting.
What problems is the product solving and how is that benefiting you?
I love it because it is simple to understand, suitable for MVP development, and generous free tier. Helps me deliver better quality products to my clients. WordPress and Movable Type are now past.
We use one Hygraph backend to feed both our iOS and Android apps, perfectly.
What do you like best about the product?
The content API is truly platform-agnostic. No matter if I'm developing in Swift for iOS or Kotlin for Android, I use the same GraphQL call to retrieve identical, structured recipe data. This approach guarantees a consistent user experience across both platforms. I also really appreciate the real-time content preview feature—it lets us see exactly how a new recipe will appear on a simulated mobile screen before publishing.
What do you dislike about the product?
Managing offline-first scenarios is our responsibility. Since the content is stored in the cloud, if someone opens the app while on the subway, we need to develop a reliable system to cache the recipes they've previously accessed. Hygraph does not offer a built-in offline solution.
What problems is the product solving and how is that benefiting you?
We organize our recipes by tagging them according to dietary preferences, such as "vegan" or "gluten-free." Within our app, users have the ability to filter recipes using these tags. This process is straightforward, as the filtering logic is integrated directly into the Hygraph GraphQL query, ensuring that we only retrieve the recipes the user is interested in viewing.
The Project Lead for a Travel Blog
What do you like best about the product?
The mobile app is a game-changer. My team and I are always on the move. If we find a new, great restaurant in Lisbon, we can open the Hygraph app on our phone, find the "Lisbon Travel Guide," and update the "Restaurants" section right then and there. It’s as easy as using a notes app, but the change goes live on our website instantly. It keeps our guides feeling fresh and authentic.
What do you dislike about the product?
The text editor sometimes fights with me. If I copy and paste text from a Word document, it can bring weird formatting with it that's hard to clean up. I have to use a "paste as plain text" shortcut first, which is an extra step I often forget.
What problems is the product solving and how is that benefiting you?
Real-Time Updates: Our ability to update content instantly has made us a go-to resource for travelers. This keeps people coming back, and our ad revenue has grown because of the steady traffic.
Local Guides for Different Travelers: We created separate content for "Budget Travelers" and "Luxury Travelers" all within the same city guide. This lets us attract a wider audience.
Local Guides for Different Travelers: We created separate content for "Budget Travelers" and "Luxury Travelers" all within the same city guide. This lets us attract a wider audience.
The Marketing Manager for an Online Plant Store
What do you like best about the product?
I am not a techie, but I love how I can create the "building blocks" for our content. For example, I set up a content model for a "Plant Care Guide." Now, when my writer creates a new guide, it automatically has spots for a video, sunlight needs, and watering schedule. I don't need to remind them every time. The best part? We can then attach that same guide to the relevant products on our website. So when a customer looks at a Monstera plant, they see its specific care guide right there. It makes our site feel smart and helpful.
What do you dislike about the product?
Getting started was a bit of a brain twister. Words like "components" and "references" were confusing at first. It took us a few tries to build our first content model correctly. Also, if I want to make a big change to how our content is structured, I still need to ask our web developer for help, which can sometimes slow us down.
What problems is the product solving and how is that benefiting you?
Smarter Product Pages: By linking blog content directly to our products, customers have access to all the information they need, which helps increase their confidence when making a purchase. We also developed a "Brand Voice" model specifically for our social media team. As a result, every social post sourced from Hygraph now features the appropriate hashtags and maintains a consistent tone, helping our brand appear more cohesive.
Easy to use and friendly interface
What do you like best about the product?
Easy to use. As a content creator and a developer the platform enables all functions to be easily implemented.
What do you dislike about the product?
Unfortunately the style when creating a content has a limited options to style it for a content creator. You need to be developer to give the style from custom css and this makes it a bit of a hard way of working with a team of different backgrounds
What problems is the product solving and how is that benefiting you?
Easy to give access to team collegues.
Solid CMS even non-technical teams can crack!
What do you like best about the product?
Hygraph has been a game-changer for our small team - the API is super fast, and setting up content models was relatively easy and clear. our dev team loves how well it fits into our workflow and especially the fact our non technical team was able to be onboarded and remove a huge bottleneck and dependency we had with the engineering team
it’s a solid, modern CMS that scales well
it’s a solid, modern CMS that scales well
What do you dislike about the product?
learning curve for non-tech users, took a minute but worth it
What problems is the product solving and how is that benefiting you?
managing content across channels and making it scalable
showing 11 - 20