Hygraph Reviews & Product Details

I have been using GraphCMS as BE in multiple MVPs, and so far, I am more than happy with the results. Great models and content editors. Fast responses, even with the free tier. Excellent support.

I dislike nothing so far. I think GraphCMS is a great product.

Having GraphCMS in your toolbox allows you have a solid BE up and running in no time. Very useful for MVPs and products where TTM is a must.

GraphCMS interface is very intuitive, making it easy to create complex relational data models, even for non-programmers. Furthermore, exploring the content through the GraphiQL interface is an absolute pleasure, making our developers way more productive. Another excellent attribute is the quality of the customer support team willing to hear our feedback and help us out.

The pricing might be a blocking factor for small projects and the interface is english only, what can be another blocking factor for some international businesses.

The main problem we are currently solving is the development speed. The tool helps us make quick iterations during development and helps us focus more on DEV, less on OPS.

Currently, I'm using GraphCMS to power this application: ios: https://apps.apple.com/us/app/rutgers-rumobile/id1036544263 android: https://play.google.com/store/apps/details?id=com.rumobile It works like a charm, I'm using the free version, and I honestly can't believe how much you can get from the free version of this software. GraphQL and being a headless CMS, everything just works perfectly. The platform has a very clean-looking UI, and the billing information is very clear. So far, I have not run into any major issues or outages, and I'm certainly looking forward to keeping using this platform for future apps, which I'm sure will be much more significant in scale. I would be happy to pay money for a platform that deserves it!

There isn't anything in particular that comes to mind. Still, I know one of the biggest challenges I'm currently facing right now, which isn't exactly the fault of the platform but rather the framework I'm using in my app, is that when I update markdown data in GraphCMS, it won't reflect the change right away on my app, I know there is some caching going on, maybe having some articles on their website or blogs or forums that talk about how to solve this would be a massive help for me.

The very fact that I don't have to go out of my way to deploy a database and put a WebUI around it for me to upload content so that my app feeds to it, it's a massive plus for me. It saves me so much time and hassle.

Very quick start. Nice user interface. Friendly community.

A bit steep price plan for professionals.

The product gives me a performant backend for mye frontend, that is easy to use and maintenance free. Development starts in seconds, almost no setup required. Just log in and press "create project" and you are good to go.

The support was ultra quick and amazingly helpful. GraphCMS goes beyond just providing a headless CMS into BAAS territoy

The management SDK could use some better error handling and docs

Using it more like a BAAS (Backend as a Service) solution

It's user a friendly feature. It is easy to work on it even if you are not so much techy. And there are many pre-made features are available so no extra stuff needed to be added through 3rd party apps. Moreover, it is very handy for my content creating team, they can access this using an app and work on it easily. My many writers are WordPress cms kinda users, so GraphCMS give the option to add WordPress API and here the writers easily work on it on their easy platform, and it is the best option available in GraphCMS.

Prices are a little high but still, it's worth it and they are also offering a free plan so that's great. Even their free plan fulfill the requirement which is the best I can say.

Native content management and its multiple models are actually helping a lot for managing content. And it's a huge thing I love is they give the option of API integration for the marketing or tech team to work on their favorite platform and this is the major thing I use and it solved my problem in many ways.

It's best for multi-language e-commerce platforms that have high tariffs.

The dashboard is not very user-friendly for editors rather it suits well for developers.

It is very easy to organize the entire thing and it helo me to localize API.

The interface - It's slick. Intuitive and best of all, rapid fast. You can get exactly what you need done in a fraction of the time for other headless CMS about.

I don't have a single complaint - the only negative experience I've had is my own misunderstanding, graphCMS makes it extremely easy for all skill levels to use, so when some of the more technical aspects pop up for a dev-in-training, I've been caught out by the technical skill level needed. Though every problem I've ever faced has been solved easily via the documentation, the slack community, or Fabian, who's a hero with the patience of a saint.

Automated Business growth. Vouchernaut is as Jamstack as they come; tons of content changing every day from multiple sources. I could use a traditional database for this, but the editing and CMS features are second to none and I'd hate to lose that. It's true when they say GraphCMS empowers teams; it really is for every one.

The ease of use and integration within nextjs apps, if you have any questions you can contact support and they will get back to you asap. Open source so you can contribute if you see something you want to add.

Nothing really, the tech is really ahead of its time and with any growing company, there are always areas of improvement which they are tackling.

CMS systems can get complicated, especially WYSIWYGs, and APIs, which use graphql, so it saves time and API calls, they have an awesome graphql playground to test out your APIs, there are a lot of benefits and I have yet scratched the surface of their offerings.

There is a great intuitive UI for editing your content. The schema editor is very flexible and the APIs are fast.

There is occasional instability when significant features are released. It is infrequent, but when it does happen, their support is responsive.

Content management for our public marketing site as well as content services for multiple applications. For applications, we can update content and messaging without a code push.

It is customizable and intuitive. As a developer, I would prefer all tasks be completed in code, and we can achieve that.

Nothing so far. For any issues, the team is prompt to provide solutions.

Data aggregation is less on our rest-API as we can use a combination of remote fields and CMS UI-extensions to grab data and use GraphCMS as a centralized source of truth.

A great overall CMS that's easy to use .

It is lacking some features that the other big headless CMSes have

I have used this CMS successfully for my portfolio. I usually reach for a graphql layer with the other CMSes I use anyways, so having it built-in was a great time saver!

APIs are mighty and simple to use. I also love the PIM functionality; this is not something that any CMS has.

I'd love to see a user management functionality (users login, logout, etc.)

I've been able to use GraphCMS to build a great e-commerce website with ease

fast support, high uptime, nice UI, rich functionality

There was no flexible plan for customizing features that are included in the plan. For example, plan X includes 10 users, 8 languages. Plan Y includes 20 users, 20 languages. But if we need 10 users and 9 languages, plan Y becomes too expensive. But this issue appeared during our research 1 year ago. It may have already been fixed.

CMS tasks. The main goal was to create a CMS for SEO configuration + Angular with no backend.

There are a number of managed CMS' out there. GraphCMS provides a robust API, easy web interface, but most importantly, world-class real-time support, which has been essential to me.

I have no real concerns. GraphCMS is my preferred CMS for building headless applications. The question is simply if you want to in-house or rely on a 3rd party CMS. If you're doing 3rd party CMS, then GraphCMS just makes sense.

We use GraphCMS to power remote displays and websites, writing our own custom interfaces and letting GraphCMS handle the heavy lifting. We focus on our core competency and let GraphCMS focus on data management and integrity.

- lots of different fields you can use for you models - the location field is from my perspective relative unique for headless CMS systems - Cool drag and drop solution - Intuitive UX which is helpful for non-technical content creators - Enumerations for drop-down menus - the graphql playground allows to explores the queries easily and has a very good auto complete -

- The naming convenction for enumerations could be improvement so they can also start with a number - Some more examples how to use the graphql API e.g. how to use it with curl or python

We use GrahpCMS as replacement for our django website and it fulfills all our needs. Everyone in the team can focus on delivering the content rather than worrying on how to learn programming. Content can be customised a lot more simple.

- API is very intuitive and easy to use if you already have experience with GraphQL - High flexibility in creating your content model - Integrated GraphQL Playground is very helpful when developing and debugging - Backend UI has a great and intuitive usability - Localization API is great and makes it very easy to build multi-language sites - GraphCMS team has fast response time and is very helpful

The price model is difficult to use for some use cases/projects because the jump from community to professional is very high.

We using GraphCMS to provide content for an employee portal as a PWA. The benefits are the high flexibility in the portal through the API and the content model. We were also able to easily implement offline functionality for the entire content in the portal.

Headless content management system which meets and exceeds our performance needs Powerful API and ecosystem support Smooth UX with the ability to do bulk operations Support for Role-based and Content-based permissions Supports GraphQL, a loosely coupled server-client model for faster development Cloud-hosted, scalable, reliable, highly available with the ability to snapshot and restore data Cost-efficient and simple licensing model

We have not discovered anything yet which we dislike in the product.

We were looking for a central storage system for our Video on Demand streaming platform, using which distribution of metadata to different consumption points (internal and external) becomes easy. It solved many drawbacks of legacy systems i.e. - It is not heavy, in-house, and monolith system - It does not bulky UX which supports single operations - It is not one of the slow-moving and expensive development cycles product

1. The UI is pretty amazing. 2. The ease of usability. 3. Auth tokens to provide specific API access. 4. Making GrahQL relationships is possible (whether it be 1 to 1, n to 1, or even an m to n relationship). 5. Integration with Vercel to make your apps JAMstack. 6. And above all, the best customer service.

As of now, GraphCMS does not allow specific mutations to be set as private and others as public. But a new update in the month of April is likely to resolve this issue. Therefore, in my opinion, there be won't any issues with GraphCMS after this.

I have been working on building an eCommerce application as of now. But planning to build more amazing apps with GraphCMS as it takes care of your backend very well.

For us GraphCMS is an excellent tool. Creating models and schemas is easy and adding content is simple. The API is clear and allows quick development. Providing GraphQL as the query language is big plus for us. I particularly like that you can easily add additional fields with default values and bulk update these fields to existing content, which helps in an agile environment.

Although bulk update is a strong feature it could have some improvements. Particularly, the message box that shows which fields actually get updated could be more precise. Modifying lists of rich text or markdown fields feels a bit clumsy.

We use GraphCMS as our headless content management system for the landing page of our company which is in the education and professional coaching sector.