What is Headless Architecture?

A headless architecture separates what users see (the 'head' — the frontend interface) from where content and data lives (the backend systems). The two communicate exclusively through APIs. This is the opposite of a monolithic system like a traditional WordPress site, where the template, content management, and serving layer are tightly coupled.

Common headless setups pair a Next.js or React frontend with a headless CMS (like Contentful or Sanity) for content, a headless commerce platform (like Shopify or Medusa) for e-commerce, and a REST or GraphQL API for any custom business logic. The frontend team can build and deploy independently of the backend team, and the same backend can serve multiple frontends — web, mobile app, and kiosk.

The trade-off is complexity. Headless architectures require more engineering discipline to maintain: API contracts need versioning, deployment pipelines need coordination, and error handling spans multiple systems. For large organisations with multiple teams and channels, this complexity is worth the flexibility. For smaller teams building a single-channel product, a coupled approach may be faster to ship.