For editors, the UI is straightforward once the model is set up. Locales, publishing, and media workflows just work, and after a bit of modelling they can update navigation and pages without needing a developer.
On the engineering side, GraphQL integrates cleanly with our Next.js stack: typed queries, draft/preview support, and CDN-hosted assets have all been smooth. Performance has been solid for SSR as well; Prepr hasn’t been the bottleneck.
The pricing feels justified because editors can ship copy and menu changes without filing tickets or waiting on deploys. Support and onboarding were strong for a headless CMS, and the schema plus GraphQL were enough for us to get productive quickly. We barely use the AI features day to day; for us, Prepr is a reliable content API rather than an AI product. Review collected by and hosted on G2.com.
What I dislike most is the multi-locale workflow and the modelling overhead — powerful once set up, but easy for editors to miss a language, and every new section still costs real developer time. Review collected by and hosted on G2.com.