Hygraph
HygraphReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
701 reviews
from
External reviews are not included in the AWS star rating for the product.
Great Product!
What do you like best about the product?
Really easy to use and set up. Intuitive UI, nice documentation, and very configurable.
What do you dislike about the product?
Non technical staff can struggle to understand some areas of the software.
What problems is the product solving and how is that benefiting you?
I am using Hygraph to store and display dynamic content for my website
Great tool for CMS
What do you like best about the product?
Very easy to use, very easy to integrate. We use this tool to give other teams (non-tech) the ability to manage our website content without knowing to code.
What do you dislike about the product?
The price. If the company grow just a little and reach the Hygraph limits, the cost expand in way disproportional to the growth.
What problems is the product solving and how is that benefiting you?
With Hygraph I was able to manage content without developing a client side front to my system.
Hygraph is a good CMS system
What do you like best about the product?
The webhooks feature of Hygraph is very good and easy to integrate and I use it to automate marketing.
What do you dislike about the product?
Nothing so far. I have had good experience so far
What problems is the product solving and how is that benefiting you?
Automating tasks has become easier with using Hygraph
Hygraph: An intuitive and versatile tool
What do you like best about the product?
What I like most about Hygraph is its ease of use. The interface is very intuitive, allowing even those who are not tech experts to navigate without issues. Additionally, its integration with GraphQL is exceptional, making it easy to connect with other services and customize queries.
What do you dislike about the product?
What I like least about Hygraph are some limitations in the documentation. Although the tool is powerful, sometimes I have felt that I lack more detailed guides to make the most of all its functionalities, especially for more complex situations.
What problems is the product solving and how is that benefiting you?
Implement multilingual content on my site.
Super-flexible data management capability of value beyond CMS use cases
What do you like best about the product?
- Flexible UI-based schema-generation
- Dynamic generation of content management UIs based on defined schemas (no hard-wiring)
- Dynamic generation of API interfaces
- Ability to limit functionality shown on UI to provide good UX for average users
- Good and fair chance to test the software
- No aggressive sales tactics
- Super-responsive support (hats off)
- Dynamic generation of content management UIs based on defined schemas (no hard-wiring)
- Dynamic generation of API interfaces
- Ability to limit functionality shown on UI to provide good UX for average users
- Good and fair chance to test the software
- No aggressive sales tactics
- Super-responsive support (hats off)
What do you dislike about the product?
- Would like even more options to further limit functionalities exposed to content editors
- So far I have not found a way to separate system objects and fields from user-defined ones in GraphQL API
- So far I have not found a way to separate system objects and fields from user-defined ones in GraphQL API
What problems is the product solving and how is that benefiting you?
Having a way to allow non-technical users to define schemas and manage related content for different things in a user-friendly way
Allows us to move quickly, with simplisty
What do you like best about the product?
It’s very easy to use, and extremely flexable, giving us all the functionality we need
What do you dislike about the product?
Nothing, we genuinely think it’s a very powerful peice of software that meets our needs
What problems is the product solving and how is that benefiting you?
We needed to keep our app config in a place that’s easy for our product owners to access, quick for use to change, and comes with the typing system of graphql so we can have certainty when we consume the data of its format (we generate type files from the schema definition)
Good configuration driven CMS
What do you like best about the product?
Very customizable and user friendly CMS.
What do you dislike about the product?
None as of now as I have just starting using it.
What problems is the product solving and how is that benefiting you?
Manual code writing and writing different code everytime a new cutomer is opting our solution.
Very good experience with GraphQL and content federation
What do you like best about the product?
Two things: first, content federation, and second, type inference with GraphQL.
GraphQL queries in Hygraph are easy and clear, mainly because they don't have all that typical Relay-like structure (with edges { node { ... } }) that other CMSs use. This makes writing queries simpler and more natural. They also use cursor-based pagination, and the structure remains quite clean.
Another useful thing is using something like gql.tada that automatically generates types from GraphQL queries, saving a lot of development time and reducing errors.
In our specific case, content federation is key because we have invested a lot of time in our own APIs. Being able to reuse all that directly in Hygraph, without having to synchronize data all the time, is very valuable, especially because we handle thousands of items with complicated relationships, and it's one less moving part we have to maintain.
Also, thanks to their support and sales team, who have supported us throughout the decision-making process.
GraphQL queries in Hygraph are easy and clear, mainly because they don't have all that typical Relay-like structure (with edges { node { ... } }) that other CMSs use. This makes writing queries simpler and more natural. They also use cursor-based pagination, and the structure remains quite clean.
Another useful thing is using something like gql.tada that automatically generates types from GraphQL queries, saving a lot of development time and reducing errors.
In our specific case, content federation is key because we have invested a lot of time in our own APIs. Being able to reuse all that directly in Hygraph, without having to synchronize data all the time, is very valuable, especially because we handle thousands of items with complicated relationships, and it's one less moving part we have to maintain.
Also, thanks to their support and sales team, who have supported us throughout the decision-making process.
What do you dislike about the product?
Perhaps what I like the least is that it doesn't come with any advanced function for customization or content segmentation. For those specific things, you have to integrate other tools separately. But on the other hand, this keeps our architecture more modular, which from my point of view is positive, but it requires changing the mindset from looking for an "all-in-one" CMS to "let's use the best tool for each problem."
What problems is the product solving and how is that benefiting you?
We needed a CMS to replace the CMS we have built over the years due to the continuous expansion of the business and the need to manage new brands and markets efficiently.
Very Good
What do you like best about the product?
easy to use, very intuitive, seems to be very fit for purpose
What do you dislike about the product?
not used it enough to notice any down side. SO far everything is very straight forward and customer friendly.
What problems is the product solving and how is that benefiting you?
Finally able to have all staff on same page and using same software which makes for a smoother operation. Live content updates.
I can finally grow my content
What do you like best about the product?
No need to overpay for CMS tools that provide little value. Hygraph is great product and the makers know it. I was able to easily build a custom blog page and publish the first article in 1 day. I'm not even a technical person but the process is straightforward. Posting content is super easy.
What do you dislike about the product?
If you have never set up a headless CMS the implementation process requires some thinking to do it but there is enough documentation and youtube videos that will guide you. If you are completely NOT technical I would consider help of a developer for setup.
What problems is the product solving and how is that benefiting you?
I can quickly deploy a blog page for custom built websites
showing 111 - 120