"Headless" explained in one paragraph
A traditional CMS (WordPress) stores content AND renders the site, one system. A headless CMS only stores and delivers content through an API; the website (the "head") is a separate build that fetches and renders it. The trade: freedom to build the front end in anything, serve multiple channels (site, app, kiosk) from one content source, and scale without CMS constraints, exchanged for more moving parts, a second hosting concern, and no visual editing unless you buy or build it. The architecture patterns live in the headless WordPress and headless CMS pages; this is the buyer's comparison.
The three, honestly profiled
- Strapi, the self-hosted open-source option. You run it (your server, your data), model content freely, and the editor experience is clean. Costs: hosting + your maintenance. Wins for data-control requirements and teams with (or hiring) technical capability; loses for "we want zero ops."
- Sanity, the developer-flexible hosted option. Real-time collaborative editing, a configurable studio, usage-based pricing that is generous at small scale. Wins for structured content at moderate scale with developer involvement; the pricing model needs watching as content volume grows.
- Contentful, the enterprise-grade hosted option. Mature, scalable, multi-space governance, priced accordingly, with seats and usage that bite at scale. Wins for larger organizations with content-ops discipline; overkill and overpriced for a small team's marketing site.
When headless earns its complexity, and when it does not
Headless wins when: content feeds multiple channels (site + app + kiosk), the front end is a custom build anyway, editorial teams need structured workflows, or the content model is genuinely specific. Plain WordPress (or a hosted CMS) wins when: the site is a website, the team edits pages visually, and one system doing everything is the point. The most expensive mistake in this category is headless for headless's sake, two systems to maintain where one would have been invisible. The honest test: name three concrete benefits headless delivers for YOUR channels; if the list has fewer than three, it is fashion. Bands and context: the rates page; the calculator prices the build either way; the decision happens in scoping with the reasoning written down.