Headless CMS
for maximum flexibility

The bulk of the cost is not the CMS but content modelling and the front end. When scope is still unclear we start with the focus prototype at €4,900 (2–3 weeks): two or three real workflows run on a test URL before the full project is priced. For more complex portals the extended prototype at €7,500 applies. Vendor licence and hosting costs are billed to you directly, not through us.

Yes. Posts, pages, media and categories can be read via the WordPress API and mapped into the new content model. It gets laborious where content was built with page builders like Elementor or WPBakery: their layout lives in shortcodes and HTML fragments and has to be restructured. We check this on a sample beforehand so the effort is known before the quote.

Only if the work is sloppy. The risks are known and manageable: every old URL needs a 301 to its new target, titles, meta descriptions and structured data must move along, and pages should be rendered server-side or statically — not first in the browser. Build the front end purely client-side and you lose visibility. That is exactly why we use Astro or Next.js with static generation.

The system does not decide that, the operation does. Self-hosted Strapi on a server in Germany never leaves your control. With hosted vendors you need a data processing agreement and should watch the region — Storyblok and Sanity offer EU hosting. The critical part is usually not the content itself but attached services: image optimisation, search indexes and analytics quickly end up in third countries.

A manageable corporate site with a clear content model typically goes live within a few weeks. Two things really drive the timeline: how much legacy content has to move, and how long approvals take on your side. Technology is rarely the bottleneck. That is why we work in stages against a reachable test URL instead of building in the dark for months.

For maintaining content, yes — that is the normal case. For creating new page types or building blocks, no: content models are structure and get defined during the project. This is where the systems differ most. Storyblok comes closest to familiar editing because changes appear instantly in a real preview. Anyone coming from WordPress should try that once before choosing a system.

Yes, and because content is structured and reachable via an API this is far simpler than with a classic CMS. Common cases are automatic translations, meta description suggestions, tagging new posts, and search that finds by meaning rather than keyword. With personal data the question is which model runs where — the point at which self-hosting pays off.