What is Flotiq?
Flotiq is an API-first headless CMS sold as a hosted service, with a free trial and paid plans on its pricing page. You define content types, and Flotiq generates an API from them with an OpenAPI schema, so you can create SDKs for your language. Editors get draft and public modes, version history with restore, live preview, scheduling and translation tools, including DeepL-powered translation. There is also a full-text search API. The company is smaller than Contentful or Strapi, and its GitHub repository has under a thousand stars, so the community is modest.
Who it suits
Flotiq suits developer-led teams building a website, mobile app or internal tool who want a typed API and generated clients without running a CMS server. It also fits agencies that value a small, focused product. Its documentation and landing page do not state a GraphQL endpoint, so if GraphQL is a requirement, verify it with the vendor before you commit.
What is the risk with a smaller platform?
Fewer people have shipped on Flotiq, so you will find fewer tutorials, fewer plugins and fewer engineers who already know it. Hosting is on the vendor side, so you accept its roadmap and its pricing changes. We cover that risk by keeping content models in version control and writing an export script on day one, so a move stays possible. The front end carries no vendor-specific code.
How does a Flotiq project run?
We begin with a content model workshop and write the types as code, so changes are reviewed like any other change. Then we generate an SDK from the OpenAPI schema and build the front end on it, which gives the team typed responses and catches breaking changes at build time. Editors get a staging space to review drafts before they publish. Before launch we load a full copy of the content, check media and relations, and test webhooks and search.
What does it cost to own?
The recurring costs are the Flotiq plan, front end hosting and any search or translation add-ons you switch on. The one-off cost is development, driven by the number of content types, relations, locales and imports. Check the pricing page for plan limits before you size a project. We scope the build after a short audit.
When we would pick something else
If you need a large plugin ecosystem and self-hosting, we usually go with Strapi. If you want an admin on top of your own SQL database, Directus is a better match. For editors who need a visual page editor, Storyblok is stronger. See the GraphQL CMS comparison if a GraphQL API decides the choice, and the wider headless CMS guide for the trade-offs.
What we build with Flotiq
- Content type design, relations and validation, with the schema kept in git.
- A typed front end in Next.js, Astro or a mobile client using the generated SDK.
- Preview and publishing flows so editors see changes before they go live.
- Import scripts from WordPress, spreadsheets or a legacy database.
- Webhook-driven rebuilds and search integration.
