Hygraph vs. Payload CMS

I would recommend GraphCMS to anyone who is also using Gatsby to build their website. If not, I would recommend them to consider GraphCMS but also consider other options. GraphCMS is a tool in which you are responsible to make the most out of it, but sometimes this requires more time and knowledge than a normal engineer may be able to handle. But with more time and attention, the reward of off-lifting content creation from the developers is a huge time saver in the long run.

Incentivized

• GraphCMS is easy to work with from the "non-engineer" side of things.
• GraphCMS is very flexible on what data models we can create and how those models are formed.
• GraphCMS uses Graph API, which is easy to write (compared to older API patterns).

Incentivized

• GraphCMS is very expensive at the enterprise level.
• GraphCMS requires deep knowledge of the system and requires lots of time to be efficient with it (especially around creating specific data patterns/relationships).
• Multiple times a day, the system will give us errors when attempting to save something but the errors are unclear as to what went wrong (can be irritating).

Incentivized

We picked GraphCMS since it used Graph API and easily integrated it into our Gatsby website. It was also cheap (free) and easy to test out the product, making it easier to prove to our company we should pay for the product in the long run. Lastly, it seems to have a bunch of support from other developers which makes us confident will be around for a while (and we won't need to replace it anytime soon). Note: I also looked at Directus and DatoCMS but these were not options within TrustRadius

Incentivized

• Better use of time for our engineers in the long run.
• More control of content for people outside of the engineer team.
• Allows people to edit the content on their own, so they don't need to wait until a developer is available to add something to the website.

Incentivized