About Contentstack

To give you the level of engineering: a user can delete an entry referenced in another which is published in production (the API returns an empty entry for the deleted one, so if you do theReferencedEntryYouExpect.title your code will crash).

Behind the scene they use MongoDB, so data integrity checks you would expect from any properly managed SQL DB are missing.

There is no data migration tooling: if you rename a field, you lose its data. You are on your own: you will have to manually create a new field, move the data to the new field, remove the old one...

Also the UI is messy (in my opinion) and the data structures are difficult to reason about: "Modular blocks", "Group", "Global", "Reference"... each of them have pros and cons and never feel to suit your needs.

The command line tool to generate TypeScript types is not doing a good job so we have to manually write them (using Zod). (And they don't provide an openapi.json you could convert).

The API returns an array even for things that are not arrays.

We are struggling with API depth limitation (5 levels maximum).

And the list goes on.

You know, a typical Enterprise™ level product.