Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Probably the best Headless CMS out there
What do you like best about the product?
APIs are mighty and simple to use. I also love the PIM functionality; this is not something that any CMS has.
What do you dislike about the product?
I'd love to see a user management functionality (users login, logout, etc.)
What problems is the product solving and how is that benefiting you?
I've been able to use GraphCMS to build a great e-commerce website with ease
- Leave a Comment |
- Mark review as helpful
Excellent
What do you like best about the product?
Ease of use, features, and support. Really impressed by this headless CMS.
What do you dislike about the product?
There is not anything that I dislike about GraphCMS.
What problems is the product solving and how is that benefiting you?
It has made developing a recent React website extremely straightforward.
Very nice product
What do you like best about the product?
fast support, high uptime, nice UI, rich functionality
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
CMS tasks. The main goal was to create a CMS for SEO configuration + Angular with no backend.
Good CMS, Exceptional Support
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
A headless CMS thought through from A to Z!
What do you like best about the product?
- 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 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
-
What do you dislike about the product?
- 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
- Some more examples how to use the graphql API e.g. how to use it with curl or python
What problems is the product solving and how is that benefiting you?
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.
Great Headless CMS with GraphQL nativity
What do you like best about the product?
- Full support of GraphQL - union types, mutations and more
- Full feature usage via API and strong performance
- Fast feature delivery
- Very good support
- Full feature usage via API and strong performance
- Fast feature delivery
- Very good support
What do you dislike about the product?
Nothing major. The UX could be improved for some edge cases. E.g. large content models are a bit difficult to navigate through.
What problems is the product solving and how is that benefiting you?
We are hosting a multitude of different website content covering our brands on GraphCMS.
GraphCMS
What do you like best about the product?
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
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
What do you dislike about the product?
We have not discovered anything yet which we dislike in the product.
What problems is the product solving and how is that benefiting you?
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
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
Flexible and performant HeadleassCMS with excellent developer experience
What do you like best about the product?
- 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
- 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
What do you dislike about the product?
The price model is difficult to use for some use cases/projects because the jump from community to professional is very high.
What problems is the product solving and how is that benefiting you?
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.
GraphCMS is one of the best Headless CMS for GraphQL that I have worked with.
What do you like best about the 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.
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
Great tool for headless CMS
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
showing 441 - 450