Your marketing director wants to publish without a developer. Your CTO wants React and independent deploys. The agency proposes Strapi plus Next.js. Six months later, adding a local landing costs three dev days — fragile editor preview, webhook breaking CDN cache. The neighboring WordPress monolith changes hero in ten minutes.
The question is not "is headless modern?" It is: how much will each evolution you have not yet imagined cost?
Monolithic: low change cost, strong coupling
WordPress, Drupal, Typo3: content, theme, and admin in one runtime.
Low cost for: new page, form, SEO extension, editor role, A/B test via plugin. High cost for: native mobile front, multi-app, total front redesign without touching back, extreme scale without redesign.
Hosting: shared to VPS often suffices; stack known to European hosts.
Headless: front flexibility, permanent operating load
CMS — Strapi, Directus, Contentful, WordPress as API — plus separate front — Next, Nuxt, mobile app.
Low cost for: visual redesign, multichannel, front performance via static CDN. High cost for: each new content type means schema, front component, preview, and tests. Permanent development team required.
Hosting: more bricks — CMS, CI, CDN, sometimes serverless functions, Redis for preview.
| Change | Monolith | Headless |
|---|---|---|
| New marketing page | Hours | 0.5 to 3 days |
| New locale | Plugin / config | Schema + routing + translation |
| Mobile app | Webview / PWA | Native possible, initial cost |
| Visual redesign | Theme | Front rebuild |
| Monthly hosting | Low | Medium to high |
Model three-year cost
List foreseeable changes: two redesigns, four landings per year, one app, three languages.
Monolith: forty euros monthly hosting, premium theme, five days yearly maintenance — stable cost.
Headless: eighty euro managed CMS, front hosting, forty dev days per year — variable but plannable with internal team.
Without internal team, every change becomes agency quote. Headless TCO explodes.
The peak: architecture follows change frequency
Decide and move forward without blind spots
List ten probable changes over twenty-four months and cost them in both models. Assess whether editors can work alone or a permanent developer is available. Test headless editor preview before signing — often neglected criterion number one. Consider hybrid if uncertain, then compare suitable hosts on compare tool and guides.
Frequently asked questions
When to keep monolith?
Small team, marketing site, simple preview, modest budget — well-kept WordPress or Drupal often suffice.
Does headless reduce hosting?
Sometimes static front; CMS, API, and preview add cost and monitoring.
Headless hidden cost?
Front development on every change, schemas, preview, cache invalidation, multi-service monitoring.
Progressive migration?
Monolith plus API section, or WordPress source plus Next page by page — hybrid limits risk.
Every future change has a price — headless bills it in sprints, monolith in plugins and technical debt. Choose by who pays tomorrow.