Agency proposes Strapi plus Next.js for twelve-page site updated twice a month. Budget doubled, deadlines extended, editor loses WordPress WYSIWYG. Headless was technically elegant — business unnecessary. Conversely, brand with iOS app, React shop and store kiosks gained editorial consistency through single content API.
A headless CMS exposes content via API (REST or GraphQL); front (site, app) consumes and displays. Decoupling frees when multiple surfaces or fast front cycles justify complexity — not when "modern" alone sells the quote.
When headless truly frees
| "Yes" signal | "No" signal |
|---|---|
| Mobile app + web + kiosk | Brochure site alone |
| Autonomous React/Vue front team | Editorial team only, no developer |
| Front releases independent of content | Need turnkey WordPress plugins |
| Multi-brand design system | Limited operational budget |
Hosting and architecture
Self-hosted CMS (Strapi, Directus) — VPS or PaaS, PostgreSQL database, backups, Node updates. Full control, maintenance your responsibility.
SaaS CMS (Sanity, Contentful) — less infrastructure, per-seat or API billing, region and DPA to verify.
Front — static build or server render on Vercel, Netlify or CDN; see Jamstack and static site.
Preview — draft environment for editors; often forgotten in proof of concept, blocking in production.
Webhooks — front rebuild on each publish; editorial latency vs content freshness.
Editorial workflow: the hidden cost
Headless shifts complexity to the publication pipeline. Each change can trigger a front rebuild, CDN invalidation and checks across several environments. Without a clear process — who validates, who publishes, who rolls back — editorial work slows instead of speeding up. Anticipate this workflow before signing the quote: that is often where headless projects slip, not on the Strapi versus Contentful choice.
Operational pitfalls
- No media strategy — heavy images served without CDN or optimization.
- API exposed without auth — draft or internal field leak.
- Double SEO — missing canonicals between preview and production.
- SaaS vendor lock-in — content export not tested before signing.
The peak: headless is not upgrade — it is trade-off
Here is the question the quote forgets to ask.
Compare Node hosts and CDN via the directory and comparison tool — pricing maintenance for both stacks, not just the CMS subscription.
Decide and move forward without blind spots
Before Strapi or Contentful, lock the decision with measurable criteria:
- Count fronts (web, app, others) and front release frequency.
- Estimate CMS, front and preview operational load over twelve months — not license alone.
- Run a proof of concept with content export and real editorial workflow.
- Choose monolithic if single front and light team.
- Document who maintains API and build pipeline after agency delivery.
Frequently asked questions
Headless for brochure site?
Rarely alone. WordPress or a static site stay simpler for a dozen pages updated twice a month. Headless makes sense when several channels consume the same content or the front team ships often.
Where to host?
The API can run on a European VPS or container, or with a SaaS vendor under signed DPA. The front deploys on CDN or build platform. Any personal data requires documented compliance, not just an "EU region" checkbox.
Headless SEO?
Fine with server rendering or static generation (Next, Nuxt). Problematic with a pure SPA without pre-rendering. Headless does not excuse a poor front-end choice.
vs WordPress?
WordPress offers editorial simplicity and turnkey plugins. Headless frees the front and multi-channel delivery, at the cost of heavier infrastructure and development.
Before Strapi or Contentful, one question: how many surfaces display this content? If the answer is "one website," headless is often a valid solution — not the simplest or cheapest to maintain.