Hygraph Reviews & Product Details

GraphCMS does a great job of balancing powerful content modeling capabilities with a simple-to-use user interface.

I haven’t found much to dislike about it, to be honest. I have noticed a couple of small glitches in the UI, but they were fixed with a page refresh.

I run a tiny nonprofit (all-volunteers). We started with a hand-coded website and have been integrating GraphCMS recently to make it easier to keep our content (e.g., our list of volunteers) up-to-date.

Easy to setup schema, add content and to get going with Gatsby. Deploy update to Netlify from directly inside interface. Interface is clean and well thought out.

Rich text and Markdown being two separate data types, instead of using a single Markdown field to either edit raw or visually. No ability to turn editor full screen, or even larger, for easier editing of content. Lack of Gatsby specific tutorials for certain parts of the system. For instance, sourcing images from Markdown fields.

I used it setup a very simple personal homepage with articles, pages and a few other content types, along with site settings and navigation control. It was very easy to setup and get connected. One great benefit is being able to re-build a Netlify site from right inside the content entry screen. Pretty slick.

The product is incredibly versatile. It's basically a cloud-based database with a nice UI and a GraphQL API. The support is outstanding, very fast and helpful. On top of that, we get new (and useful) features basically every month. You get a built-in CDN which ensures fast content delivery.

The UI can be a bit challenging for non-technical users. If someone is purely a content editor, they definitely need some time to wrap their head around it and to learn which parts they can ignore. Sometimes things are not very polished or a bit broken for certain cases, probably because of the fast paced development. But so far it has never affected our production systems, and never been unrecoverable. The great support team always helps managing these cases and bugs are fixed quickly.

Mostly building websites with content that is modifiable by editors. Being able to define your own schema with nested models and relations makes for endless flexibility. We're also maintaining an internal EAM-database of IT components which we query and visualize in different ways.

Im astound by the unlimited data structuring possibilities through "Models" and the the ability to change the content structures on the go! The GraphQL Union Types and the relational connections between models enables me to take full control over the site structure at build time. Content managers can easily decide where and how sections of the page are positioned. I would like to emphasize the astoundingly quick support. My questions are answered in realtime! And the support team asks me proactive, if I was able to resolve my issues. The team publishes new features on a constant basis and they are open to new suggestions too. If people are not sure if this CMS is something for them, they should take the advantage of the free tier and try it themself.

At the current moment its not possible to prevent certain users from editing specific models, but this is not going to be the case for long. The team is already working on it.

With this CMS the communication need between the content managers and the frontend developers was almost removed. Content managers are not only in charge over the content but also over the site structure.

We use GraphCMS for most of our client projects. We prefer the tool as our main CMS since the Content and Management API offer us a lot of options in regard to the frontend, the performance is great and the content modelling intuitive. As an agency, we use it for projects ranging from marketing websites to machine to machine applications.

From the developer perspective, the product is a game changer, nothing to complain here. Content editors need a few days to get used to the interface. The content editing experience has still some flaws - nothing major but could be improved.

We are using it for several clients and the range of the solution is wide. Examples: multi-language websites with thousands of articles, pages and inter-references; structured data for machine to machine integrations . Overall, the unlimited data structuring possibilities are one big plus. At the same time, the clean interface and the well-documented APIs help us to build on micro-service architecture appropriate for each and every customer project we get.

GraphQL CMS is easy to work with. Our developers are very happy to work with this tool - everything is fast and efficient. And I personally think: GraphCMS provides the best support I ever had with any other tool. The constant updates are great and the GraphCMS developers are always open for new features wishes of our clients :)

Well, sometimes it is hard for useres to adapt in ths modell of cms. But it really depense on the person and their exerience.

GraphCMS makes it very easy to implement new content and build new pages fast and reliable. We realized very different project with very different way to provide content on their sites - but every time it was easy to use and easy to implement.

GraphCMS has to be the most feature-complete GQL based CMS out there. Drop any preconceptions you may have about out-of-the-box solutions and give it a spin - the depth this product has is incredible and the support from Fabian is phenomenal, even at 8.30pm on a Friday evening. The free tier quotas are extremely generous for testing purposes and you could easily run a small project with no costs. The pricing scheme is well documented and extremely generous considering the A* support they give, the amount of effort gone into their documentation and the knowledge of their staff.

Webhooks are locked behind the paid tier, which, if you rely on them, requires you to take a dive into your wallet to access. That being said, now that we're ready to scale, it's a non-issue. Some CMS focus more on the author experience so if you're looking for a headless blogging platform such Ghost, you may not find what you want here. Saying that, I would 100% recommend trying it before coming to any conclusions.

With JAMstack becoming ever more popular, we tasked ourselves with building a scalable, revenue-driving app with minimal overheads and effort required. GraphCMS was integral to this and as is definitely our go-to choice!

When I first touched it, it was difficult to understand. However, after understanding the mechanism, I feel that it is easy to understand UI and UX. However, personally I would be happy if there were many more examples.

The window from the right side to enter data after defining the schema is small. I want to input more widely.

Japanese web marketing is behind the world. This is because there is no mechanism for individual learning. I made a React template that works with a combination of Firebase and GraphCMS Easily set up a member-based web service We offer you a site to personally try web marketing.

Having a native GraphQL CMS makes everything much easier to work with. Integrating webhooks and maintaining 10+ locales is seamless fo rus. Developers are much more efficient when building requests, and the product team has granular visibility over every integration step. 10/10 Support as well! They have constant product updates and periodic feature updates with a very well maintained feedback submission system.

It would be nice to have a few more custom roles for each individual contributor we work with, but its possible to circumvent this on the frontend with our own authentication permissions. Another nice-to-have would be integrations, but from their public roadmap I can see its being actively worked on.

We maintain about 10+ locales with the content for each managed in different locations. GraphCMS makes it much easier for us to structure the content needs for each website with granular accuracy. Their documentation is top notch to have a perfect implementation with React making it much faster to implement changes or new projects compared to other alternatives we've used in the past.

We love the crisp UI and the simple implementations. The entire migration of 3 websites and 2 mobile apps took a matter of weeks, and the scalability is brilliant. From all the CMSs we used, GraphCMS had the best internal feedback - frontend is thrilled with GQL and our marketing team loves the editor. And their support is top notch!

The interface looks a little dated but incremental updates trickle by. There's a few features missing, however they have an open feature request board that's updated regularly and taken into consideration.

Centralised all our content for our sites and apps into one hub, which makes it much easier to manage content for all our platforms. Frontend doesn't need to hassle backend for API maintenance, and marketing doesn't need to constantly approach frontend for debugging or deploying updates.