Hygraph Reviews & Product Details

The schema editor is fast and snappy. The generated GQL API is working as expected, migrations run swiftly and if something goes wrong, the support team will respond within minutes.

Asset management is a big story of its own and while GraphCMS offers support for its inline "file uploader" asset handling can be quite painful and there aren't many options to work with assets. But that shouldn't be a feature of this kind of tool anyway - I'd love to see a deep integration with dedicated services like Cloudinary and a programmable "bridge" e.g. to query for rendering asset derivations on query time (Gatsby Image is basically doing that).

We're running a meetup hosting website on GCMS and it works just fine. Creating a new event with speakers and talks is a matter of seconds and the backend is flexible enough to have fields enabled in no time.

Easy to get started with, pairs well with GatsbyJS, very generous quotas.

honestly, no real complaints. Images/media sometimes take a bit long to handle uploading in poorer network conditions.

As a freelancer, a user friendly CMS for non-technical clients is a must, and GraphCMS does the job well, while remaining flexible enough to me molded by the dev.

The support is always fast and helpful! Really skilled and enthusiastic people.

Legacy environment was somehow limited at first

Creating a Gatsby/React website that can be maintained by non-technical people

We use ReasonML in our frontend and website. It’s an ML-based language with static type checking. Combined with GraphQL, it gives us the ability to import a schema using an introspection query, which in turn gives us the ability to do compile-time type checking. Contrary to similar services, GraphCMS implements those introspections—a huge win for us. Another huge win is speed. We’ve found GraphCMS appears to be much faster compared to similar services. Apart from that, we’ve found the platform to be quite flexible. Being able to not only specify relationships between content, but also the way it relates to other parts of the schema (one-to-one, one-to-many, etc.), makes for great control over the schema. We’ve internally started using it for prototypes that go beyond the scope of a simple CMS because of this flexibility.

We feel the interface could be slightly more tailored for content managers, as it seems more tailored towards developers now. Another (minor) thing is that we did not find a repeatable item field. While this is something that is easily solved with relationships (and sometimes maybe even beneficial to do so), there are other cases, specifically when dealing with things like pricing tables, or a list of features (in other terms; things that will only ever be shown in the context of their parent entity), where it may be much clearer to the content manager to communicate that the item can occur multiple times.

The biggest thing we’re currently using it for is as a CMS for our website. As the web ecosystem we use is built with ReasonML, we are trying to stay as type-safe as possible. Having a schema generated that is then interpreted by the compiler minimizes the risk of getting runtime bugs.

Hygraph makes it easy to create data schema and craft a CMS setup that meets the needs of multiple of my clients. Ingestion of the data is also very easy and straightforward.

There could be better documentation and warnings about changes coming to the API, especially when they could be breaking.

Hygraph allows my clients to manage their own data, decoupling it from the front-end side of things and making management of web properties easy for me and them while reducing the likelihood of my clients creating any issues on the site.

The best part about Hygraph is its ease of use through modular building blocks. It is very clean and modern in it's design. It is also a great platform for international businesses as it allows us to share assets between countries.

The least helpful parts about Hygraph are the lack of customizations available to alter the different modules. It feels limiting in designing our website overall. It would also be helpful to be able to see a preview of the page before it is published.

Hygraph is solving managing assets for an international company to be able to share with each other for their unique and individual websites. Website visits and interactions have increasing much more.

I like the simple way to add pages, images, text. Its good

Not much that i can think of at the moment

We are able to customise webpages via our platform for each new business that joins us. Its good.

Hygraph excels in both speed and user-friendliness. It's highly responsive and provides smooth navigation, ensuring a seamless user experience. The ability to customize the platform makes it really good. The standout characteristics in Hygraph for me are: Ease of use Scalability

Slightly buggy at times The confusions between 'Save' and 'Save and Publish' button Sometimes, hygraph refuses to open

Having a completely customizable platform has always been a problem for us. Hygraph totally solves this for us

Hygraph is a great CMS that can be used in many different scenarios and kind of projects due to it's flexibility and user interface. Also, the customer support is very helpful as well.

There are some features that aren't present in this CMS that we can find in other solutions, like WordPress (used as headless CMS).

Easy to use content management system, as our client has some users that only need a way to insert new content, as we need to implement as a headless CMS.

Hygrah is very easy to use and its very effective for small sites or landing pages

It can be improved in usage of components

Hygraph gives us flexiblity to manage the content with ease for our business needs

We recently required a headless CMS for managing the majority of the static content on a larger project im leading. Initially, I had started with Sanity, however there was too much of a learning curve for our devs to efficiently deploy it to production. While it did have almost limitless customizablity, it came at the cost of an overly complicated platform where you were responsible for having the backoffice in good and running order. After trying Sanity, I had demoed a few other headless CMS until I came across Hygraph. Hygraph seems to have the most mature back office with the most feature sets. Best of all, it's cloud based so we don't have to worry about whether it will build after making changes, or having to employ yet another thing to our CI/CD pipeline for not much gain. Initially I thought there would be limitations due to not being able to edit the source code, however this was not the case. The cloud based platform was more than enough to implement the CMS in a completely custom manner. They offer various methods of querying your data, including graphql which is what we opted to use. Unlike other platforms, Hygraph provides multiple graphql endpoints depending on the use case (ie. Read on CDN version). Schema development was much easier than other platforms and can be done from the back office gui rather than having to meddle around with yml files. This saved a significant amount of time due to the complexity of our nested data. Overall, I think Hygraph is the most fluid headless CMS solution for projects that need to develop and deploy rapidly. The work we completed with Hygraph woild have easily taken 3x longer in a platform such as Sanity.

Visualized pages to manage content on the backend could be a little nicer

To dynamically call static content in various areas of a site in an efficient manner

Not provided

Not provided

Not provided

The project setup is very straight-forward, and all process done on the Hygraph dashboard, we don't need to install any package to start the project. Other features I love the most, such as seamless integration with Next Js and even Hygraph provides rich text renderer for React to help us render smoothly in the front-end.

I hope Hygraph create new pricing to afford, because the paid version cost hundred of dollars

Hygraph helps full stack developer and content creator to set up backend service without headache so we can start project faster

They've put a lot of effort into the user experience which makes it a wonderful place to edit and manage content. The ability to pull in remote data and publish as part of the content API is also a wonderful feature.

They probably need more comprehensive examples of starter applications written in frontend frameworks (such as Nextjs). It would be great if they provided guided procedures (and tools) for migrating content from other well known CMSs such as WordPress.

Hygraph is opening the doors to future opportunities as they add more integrations to their Market Place.

The interface is very well laid out and user-friendly. The docs are very clear.

There are some advanced features missing (media domain optimization for SEO for instance), some are being introduced though.

Creating complex information architectures that can be used in different touchpoints.

Below are the things which I like the most. - The ease of use - Slick design - rich-text visual editor - Easy-to-use localization feature - Scalability - Good Speed - API integration - Support

Below are the things which I dislike the most. - Content should not migrate from one environment to another - Found the bugs during the adding the content If we add content using the 2 different tabs in the browser then it will be a mess. - Manually refresh the dashboard for new content to appear - Missing proper video tutorials

Using the graph cms we do not need individual cms like WordPress. Now I can manage all cms content using the graph cms.

GraphCMS has been great for us to have one place to store all of our content that can then feed into multiple instances of our learning system, so we can provide our content to multiple corporate clients

There are sometimes issues with content feeding from GraphCMS into our platform, where things like quizzes do not upload properly and we have to resend it or manually update in our platform

We are able to instantly upload content into our platforms with the click of a button, saving multiple hours of manual work that we would otherwise have to do, allowing us to make more sales and quicker

The most significant benefits are how fast we can now build content management systems. The development and initial prototype and live version takes less time, and things get ready rapidly fast

The only things that I wouldn't say I like it's not flexible and not extendable as much, not much customization available

I am myself, a freelance software engineer; I make apps and solve clients' data management requirements. Its make things get ready very fast

GraphCMS is a very flexible tool. From simple i18n to full-blown website organization, it's all possible. We use for two cases: first, we use GraphCMS as a localization tool for our platform. So all text that is displayed within the platform is identified by a unique key. In Graph we put a value for each language available for each key. That way, it is straightforward to change translations and text in general. The second use case is our landing page. We have several different content blocks available, e.g., news article, video+text, picture+text, etc. In Graph it is pretty simple to add, remove or edit these building blocks and also to change the content of each block, e.g., texts or pictures. The actual visual interpretation is done in the code.

You need to get used to the way of building stuff with GraphCMS. As the code makes the actual decision on how content looks in a given environment, it makes it harder to imagine the final result. However, after some time, you get used to it. Unfortunately, we have performance issues from time to time, where loading of localized content takes some time. Also, it would be great to publish entire sets of building blocks. For example we have a picture+text block which has an own component nested for uploading and configuring the picture. If you just publish the entire building block, it doesn't publish the picture automatically.

1) localization on our platform 2) Entire content management for our landing page -> both is pretty simple as soon as you got used to the way of working with an headless CMS

GraphQL (duh), union relations, the whole data modelling, etc.

Every model using in a union counts towards an item in the model system. I might have misunderstood the functionality what you guys had envisioned with the functionality. We want to give flexibility to create a page and wanted to keep it as flat as possible. Create a new model, create a new component and assign it to a content union relation field and the customer is good to go to create something beautiful. With the 'recen't addition to the strict content models we're very limited in what we're able to offer and we have to resort to other solution inside our models.

The content to component creation pipeline. GraphQL is directly used in our app with GraphQL codegen, this creates assurance that the application works as expected.