Hygraph Reviews: 4.6/5 — Highly Rated

Hygraph is the most reliable CMS I've used. I've experimented with quite a few different options, but nothing came to the level of reliability & usability as Hygraph. Implementing it into our codebase is simple, the UI is no-frills & easy-to-manage, and most importantly, it has been reliable. Our team has increased the volume of content we're adding to the CMS and feel confident in housing it in Hygraph. We're excited to continue using it and see what else they come up with to improve the experience.

Some of the new kids on the block integrate easier with folks building website on top of the latest framworks (like Next.js). I'm sure this is something the Hygraph team is working on — I'd love to see easier integration of new schemas in a Next.js app.

- Non-technical stakeholder adding content to marketing site - Hosting content

Really enjoy the speed of api-responses on different geo's.

Can't think of anything. Even the team migration to new dashboard was easy.

Implemented on centralised content db and deliver across all platforms.

This is my goto CMS for any project I create. It's very intuitive, the free plan limitations are just enough for small projects. Helpful API playground makes any integration simple and fast. Customer support is very helpful and responsive, even outside the working hours. They were kind enough to grant me an access to the premium feature for a university project!

The localization of assets might be easier

As any content management system, Hygraph helps me separate the struggle of filling the client's content for their webpage by simply allowing them access to the project and do it themselves. Besides that, it has an excelent set of free features, perfect for creating all startup projects.

Both the Content and Management APIs are incredibly versatile and powerful. I was impressed that we could automate management tasks such as creating webhooks through an API.

Some features need a bit more love. Localisation is a bit janky, with weird treatment of the default language and not-so-intuitive mutations for updating data in localised fields. Overall it is manageable but could be better.

Having an automatically generated graphql API. Improved CMS experience for our content team. Automation via webhooks. A "source of truth" for our content metadata.

Very responsive to feedback when there's a bug or for feature requests. They don't implement everything we've asked them to, but they listen and make improvements to their product when the feature makes sense. Their webhook implementation is good, we use it to notify backend systems about content being updated, but we can opt out of receiving notifications when our automated systems performs the update. The user interface is intuitive enough that normal people can use it. The custom app integration is pretty nice. It allows us to do our own content quality checks and give instant feedback to the editor.

When you have a lot of data, the user interface can become slow. You'll have to manually update a default view of each model to reduce the amount of data you fetch when you're just trying to get the overview. If you have a lot of languages (10+) then the user interface can become a bit messy, but it's a lot nicer than many solutions out there.

Hygraph takes the burden of managing our content pieces, many of them very complex, without us having to update a single field. It enables us to move quickly in content creation, and update our content modeling without having to write many lines of code. We also don't have to worry about handling the database for the content (our data is easily in the hundreds of gigabytes, if not a few terabytes)

It's free to get started, and priced competitively to the market. Data schemas are easy to develop, and GraphQL is easy to work with. The static asset service is great - super easy to resize, crop, and change image formats for optimum cross-platform delivery.

Web interfaces are somewhat limited, although I know they are working to make improvements here.

It is our content management platform and allows us to have a single source of truth for all of our content and static asset needs.

GraphQL API. After migrating our blog from hubspot which uses rest api I realised how lucky I was to use Hygraph. I'm a content creator so I knew Hygraph before as Graphcms and created some blog generation content with it. So I was the one suggested it to my team :) Thank you for creating it! Its super fast easy learning curve and people value your ideas. Thank you

Changing the schema validations after you create 1000+ content on the schema is harsh. I added slug later on after adding 1000+ entries and wasnt able to autofill the slugs from blog titles

we are using it as cms for our lovely blog

Many content management systems focus on features and technology. GraphCMS focuses on the benefits and how we can help you get better results for your business or your customers. This focus on use to the user is what makes GraphCMS unique.

A project is an excellent way to get a website up and running quickly, without a lot of extra work, but the customization is limited.

I am a Freelance content writer; I help startups and SMBs solve their data management problems using graph databases. I build custom-made software solutions that are simple to implement.

User experience, powerful queries with content api

Content sync between environments (prod-staging) would be a useful feature

We needed a content storage app that we dont have to maintain. Hygraph does this job very well.

It is super easy to use, good documentations and I love the usage of graphQL. Having multiple branches also helped us a lot in our development. Its schema also provides everything we need.

I don't think there is anything we dislike about it. Maybe having an extra branch would have helped so we could have production, staging and dev. Other than that I think it is all right.

Considering that we have our own designs so we had to choose a Headless CMS so we tried different ones and we picked HyGraph. In addition, it had a good support team.

How easy it is to make the pages and add content

wish there was an easier way to preview as I edit

Creating a page for an event and its very easy

Hygraph helps me to easily create good looking content.

There could be even more options for formating the text and creating assets as tables easier.

Hygraph is used by us to create a helpful contenthub for our customers. In other words: We use Hygraph as a easy-to-use blog system.

I actually needed to choose a CMS for the project we started working few months ago. Here are some reasons why we decided to go with Hygraph - versatile - easy to use - support team is fast and helpful - has good/ cheap bandwidth/ API calls/ user seats options - graphql !

No CMS is perfect, these are few things I think needs improvement but I can live without: - no easy integration with media management platforms like Cloudinary - Hygraph supports assets upload, which is nice, but you can't query only the fields you need from the assets, you need to get its entire data

We needed a content management solution for our multilanguage website. Hygraph provided

The platform is really user friendly. Every component that helps you edit your content is well chosen and designed. You just don't need to be a high-end developer to get grip on the fundamentals of Hygraph. In our university we use Hygraph to teach our students how to model data. Well... Hypgraph made it so easy that our students really get prepared before they jump into an abstract programming layer. With Hygraph we wrote a tool to keep track of the learning progress of our students. We started 2 years ago, and really... Hygraph has 0 days of downtime. So realibale, we are greatful we can work with a tool that is fun to work and teach with.

Because Hygraph is well developed and designed, you can clearly see the extra oppurtunities you can get out of the tool. Development takes time... The roadmap of Hygraph is well built and chosen and fits the needs of their users. Maybe we are not to patient enough :-).

We needed a platform that was user friendly enough to work with, even for people who are not used to a CMS or tech in general. With the easy accesible dashboard, our users can immediatly edit and upload new content.

Create many entity and upload are best and simple uses

Price, to expensive to small companies and agency

Blog, updaload images, categories and entities of app

Hygraph has a clean look, useful features, and a simple GraphQL API. No extra junk. No competitor comes close. In addition, their support team is very responsive and helpful.

No major issues so far, we do not use Hygraph at a large scale though.

We needed a clean system to manage the data of our company website.

The thing I like the most about Hygraph is the ability to quickly add fields and create a page. I have used other CMS, but I found Hygraph very easy to use.

The things I disliked was the limitation on not being able to add link to images.

Page creation is extremely easy which makes it easier to take pages live.

The ease of intergration and the flexibility it offers, including the locals, this makes it work with many different complex sites. Also, their support is always there to help whenever you need.

The lack of being able to add HTML to the free text editor for complex nested lists in T&C documents etc this was in previous versions

It solves multiple issues by having the flexibility of being a headless CMS system and having the documentation and support, making the product stable and robust.

I love that it's built on GraphQL, which is easy to use and faster fo development. Dashboad is easy to use and allows to distinc between prod and stagin environments!

Missing a third-party backup solutin for media and query data

Hygraph is allowing me to serve and manage content wthout having to maintan such system on my own. It's also frontend agnostic which means it can be plugged into any app, or mutile apps at ounce

Easily navigatable and quick to learn, especially for new users.

Grammarly extension doesn't apply to the rich text within data models. I would like to be able to proofread my text.

Its simplified development is great for users that consume it for the first time, including junior content managers such as myself.

- Support for excellent GraphQL API - Webhook Service is top notch - The interface was very friendly to non-developers - Very easy to clone projects

- There could be an option for dark mode

We wanted to use it on a very static website as Headless CMS

Hygraph allows users to customize content templates, styles, and formats to suit their specific needs and brand guidelines, providing flexibility and creative control over the generated content.

free API limit is 1 M .which can be utilized in less time. Users may have concerns about the cost or pricing structure of Hygraph, as it may require a financial investment that may not be feasible for all budgets or business sizes.

it offers collaboration features that allow teams to work together on content creation projects, facilitating communication, coordination, and feedback among team members. This can help improve team productivity and streamline content creation workflows for businesses with multiple content creators or stakeholders.

It's straightforward to use. The best part about it is the playground to check and see how to format requests properly. Another good thing is that you can view deeply nested references of each content.

Nothing really, it's fantastic. Thank you !

Deeply nested referencing can be accessed using Hygraph

Easy to use, fast and has a free tier. GraphQL is quick to get things done and I like the API playground.

Free tier has issues on Next.js builds with too many requests. Need better documentation on workarounds.

Supports my blog website

The API playground is so helpful for testing the fetch requests and seeing how the data is rendered.

For a beginner to headless CMS the learning curve was quite steep but there are tonnes of educational material out there and once you get the hang of it, it's super simple

It's making scaling my amount of content much easier so I can focus on styling and other passion projects

The schema management is extremely powerful and flexible. Clients always change their minds about data structures and hygraph handles this very well.

I have been using hygraph on several projects now and still haven't found a dislike.

Providing a solid graphql api that makes building websites and apps a pleasure.

It it's very easy to setup and there are a lot of useful features right out of the box. It's also very easy to integrate with external services

I'm looking forward to their coming Algolia integration

Querying data for my front end application

As a developer, Hygraph makes integrations into whatever tech stack you are using very easy and seamless. The power of being able to edit records and schema in real time is powerful for collaboration and testing purposes. This is by far one of the best database/CMS management tools that I have ever used and so glad that we were able to get the most out of it.

It's 99% fantastic, a little steep pricing curve but worth it.

It's amazing at creating and managing a database that instantly adapts to our needs.

- The nodejs integration is flawless - API setup by region - Data primitives and connections

The pricing model, from 0 to 299. The free version lacks a very basic functionality: environments.

Quickly prototyping of models and forget about a backend just for CRUD operations,

The performative and quick UI. I noticed that I don't have to wait more than 1 second to run a query, create content, publish, list my content, etc. (I don't know how it would be if I had dozens of data, tho). I also like the docs; I resolved all my problems by reading them and rarely had to google for answers.

I wouldn't say I liked that I couldn't directly publish content; I first had to run a mutation to create content and then take the returned id and run another mutation to publish it. Also, I didn't like the limit of 100 items to query, but I understand that both of these limitations may have technical or product reasons to exist, and it didn't stop me from doing my work at all.

It provided an easy way to have a database and graphql API; it was everything I needed for my final college paper so that I could focus on the front end, which is my main stack.