Headless architecture

In headless architecture, the back-end systems and the interface are separated: content is fetched from the service through an API, and the interface is built as a separate implementation for presenting the content.

Tell us what you needGet a price

  • Over 200 clients
  • customer satisfaction
  • Over 30 employees

Updated

Our guiding principle for choosing technology is fitness for purpose, not novelty or appeal. This page describes the architecture and its use cases.

How the architecture works

In a traditional implementation, content management and the interface are one whole: the same system stores the content and shows it to the visitor through the interface. In headless architecture, these are split into two parts:

  • The content store holds the content and offers it through an API. We implement this most often with WordPress, because the block editor, users, roles and publishing workflow are already in place and familiar.
  • The interface is built separately, for example in React, and fetches the content it needs through the API. The same content store can serve several interfaces at once: a website, an intranet, a mobile app, and even an in-store display.

Maintaining and security-patching the content store works the same way as on an ordinary WordPress site. The architecture's complexity sits on the interface and API side, not in content management.

When headless is worthwhile

  • The same content in several channels. When a website, an app and other channels use the same content, one content store and several interfaces is a clearer solution than copying content between systems.
  • Large portals. News portals, member portals and learning systems with a lot of content and interactivity benefit from content management and the interface evolving separately.
  • Custom applications. Intranets, customer portals and other tools where the interface needs to behave like an app are not built in the best possible way on a traditional technology stack.

When we do not recommend headless

We do not recommend headless architecture for ordinary websites. There are more systems to maintain, expertise is needed across more technologies, development takes longer, and editing content is often more work, or more limited, than in WordPress' block editor. If the site's job is to tell your company's story, generate leads, and be editable by marketing itself, traditional WordPress does it better and more cheaply.

What headless costs

A headless implementation usually costs more than an equivalent traditional implementation, because there are more systems and APIs involved. The price is agreed as fixed before we start, on exactly the same principle as in our other web app projects.

FAQ

When is headless architecture worthwhile?

The choice is justified when the interface needs app-like functionality, or when it is a functional portal, intranet or customer portal. We do not recommend headless architecture for an ordinary company website.

Does the content store have to be WordPress?

Not necessarily, but we recommend it most often. Content creators already know WordPress' block editor, and users, roles and the publishing workflow are ready-made. The content store can also be, for example, Contentful or an entirely custom system, when the need calls for it.

Is headless more expensive than a traditional implementation?

Usually yes, because there are more systems to maintain: the interface, the content store, and the APIs connecting them. The price is agreed as fixed before we start, as in our other projects.

Summary

Headless is a tool for multi-channel content, large portals and app-like interfaces. For an ordinary company website it is an extra system to maintain, and we do not recommend it for that. Ask us which situation your project falls into.

More technologies

  • Technology

    We always choose technology based on need, never novelty or habit. We explain here how we build and on which platforms, when they are the right choice for your need.

  • WordPress

    WordPress is the world's most popular publishing system. Thanks to its open source code, it is a flexible and cost-effective platform on which we build almost all of our website and webshop projects. We explain when it is the right choice, when we recommend something else, and everything you can build with WordPress together with us.

Read more in the guide

  • Why choose WordPress?

    WordPress is the world's most popular content management system, and we use it for most of our projects. It offers excellent content management, scales with your needs and is supported by a large developer community.

  • API

    An API is an agreed way for two systems to exchange data. A webshop can, for example, fetch product data from a stock system or send an order to a checkout system. A well-made API removes manual work and errors, but building and maintaining it affect the price.

Which technology fits you?

Tell us what you are building, and we will tell you honestly which solution fits.

Get a priceTell us what you need

Get a price estimate or tell us what you need

The estimate takes a few minutes and does not ask for your contact details. You can also describe your need. We will get back to you by the next working day at the latest.

Get a priceTell us what you need