Over the past few years, "headless CMS" has become one of the most talked-about terms in web development. Teams building large e-commerce sites, mobile apps and high-traffic publications are increasingly adopting this approach instead of a traditional CMS. This article explains what a headless CMS actually is, how its architecture differs from a regular WordPress site, its real advantages and trade-offs, which platforms are popular, and — most importantly — who each approach is right for. The correct answer is never "newer is better"; it is choosing the tool that matches your project and your team.
What Is a Headless CMS?
A CMS (Content Management System) lets you write articles, upload images and organize pages without hand-coding every screen. A traditional CMS such as WordPress, Joomla or Drupal bundles everything into one system: the backend where editors manage content, the database that stores it, and the frontend layer — the theme engine — that renders finished HTML pages for visitors.
A headless CMS removes the "head", meaning the presentation layer. What remains is a content backend plus an API for delivering that content as raw, structured data. Any number of "heads" can then consume it: a website built with Next.js, an iOS or Android app, in-store digital signage, even a smart-watch widget. Every channel pulls the same content from the same API, so there is a single source of truth for everything you publish.
In short: a traditional CMS couples the content backend and the display frontend in one system, while a headless CMS is backend-only and serves content through an API to any independently built frontend.
API-First Architecture vs the WordPress Monolith
Regular WordPress follows a monolithic architecture. Every time a visitor opens a page, PHP queries MySQL, runs the request through the theme and plugins, and returns fully rendered HTML in a single round trip. The upside is that everything works out of the box — install a theme and you instantly have a website. The limitation is that the presentation layer is tightly bound to PHP and the WordPress theme system.
A headless CMS is designed API-first: the API is the product, planned from day one rather than bolted on later. Content is delivered as JSON through one of two main standards:
- REST API — content is fetched from fixed endpoints such as
/api/articlesor/api/articles/42. Simple to understand, supported by every language and HTTP client, and a good fit for straightforward content models. - GraphQL — the client specifies exactly which fields it wants in a single query. This avoids over-fetching (receiving more data than needed) and under-fetching (having to make several requests per screen), which makes it popular for apps with many different views.
The frontend is a completely separate application, often deployed on a different server from the CMS altogether. Updating content in the CMS never touches frontend code, and redesigning the site never touches the content system. That decoupling is the entire point of the architecture.
Advantages of a Headless CMS
Omnichannel: one content source, every channel
The headline benefit is publishing to multiple channels from a single source. The content team writes an article once; the website, the mobile app and the kiosk display all pull it simultaneously, with no copy-pasting between systems. Businesses running both a website and an app eliminate a huge amount of duplicated editorial work.
Performance
Modern frontends typically pre-build pages as static files (Static Site Generation) or use Server-Side Rendering with aggressive caching. Pages load extremely fast because no PHP execution or database query happens per visitor. News sites and campaign pages that face sudden traffic spikes benefit the most, since static files scale almost effortlessly behind a CDN.
Security by architecture
When the public site is just static files or an app with no login surface, the actual CMS can sit behind a firewall or be restricted to the editorial team only. The attack surface shrinks dramatically. Compare that with regular WordPress, where wp-login.php and wp-admin are exposed to the whole internet and are among the most attacked URLs on the web.
Freedom of tech stack
Developers can use whatever tools they prefer — React, Vue, Svelte or anything else — and can replace the entire frontend in the future without migrating any content, because content lives in a CMS that only ever communicates over an API.
Disadvantages and Challenges to Know Before You Choose
- Development cost. There are no ready-made themes to install and use. Every page a visitor sees must be built by a developer, and developer time is by far the largest cost of the headless approach.
- No easy preview. In WordPress a single click shows you exactly how a draft will look. In a headless setup, preview must be engineered: the frontend needs a mode that fetches draft content, which is real development work.
- SEO becomes your job. Meta tags, Open Graph, sitemaps and structured data that plugins like Yoast handle automatically all become developer responsibilities, and you must ensure the frontend uses SSR or SSG so search engines see complete HTML.
- A much smaller plugin ecosystem. Features WordPress solves with thousands of ready plugins — contact forms, membership, shopping carts — usually have to be assembled from third-party services or written from scratch in the headless world.
- More systems to operate. Instead of one application you now run at least two (CMS + frontend) that must be deployed, monitored and updated separately.
Caution: do not choose a headless CMS just because it is trendy. If your team has no in-house developer, maintaining a headless stack long-term will end up far more expensive than an ordinary WordPress site.
Popular Headless CMS Options
Strapi
An open-source headless CMS built on Node.js and one of the most popular self-hosted choices. Its strength is letting you design content types visually in the admin panel, with both REST and GraphQL delivery. The code is fully customizable, and you can install it on your own server without license fees (a paid cloud offering also exists for teams who prefer managed hosting).
Ghost in headless mode
Ghost is a publishing-focused CMS that normally ships with its own theme layer, but it also exposes a Content API for headless use, letting an external frontend fetch posts as JSON. We covered Ghost in depth in What Is Ghost CMS? For Bloggers and Newsletters — recommended reading if publishing and newsletters are your main use case.
Directus
Also open source, with a distinctive twist: Directus wraps an existing SQL database directly, generating an admin app and API on top of your current schema. That makes it attractive for organizations that already have a database and want a management UI plus API without migrating anything.
Payload
A newer TypeScript/Node.js headless CMS where the content structure is defined in code (config as code), so the entire system can live under version control. Development teams that want everything reviewable in Git tend to love this model.
Headless WordPress
WordPress itself can serve as a headless CMS. It has shipped a built-in REST API since version 4.7, and the WPGraphQL plugin adds a GraphQL endpoint. This route suits teams who already know the WordPress admin inside out but want a modern frontend. See our primer Introduction to the WordPress REST API for the details.
SaaS platforms: Contentful and Sanity
For teams that do not want to run a server at all, hosted services such as Contentful and Sanity are ready to use the moment you create an account. Both offer free entry tiers for small projects and charge as usage grows, with the trade-off that your content lives on the provider's infrastructure.
Frontend Partners: Next.js, Astro and Nuxt
A headless CMS never works alone — a frontend framework consumes its data and renders the pages. The most common pairings are:
- Next.js — the React framework supporting SSR, SSG and ISR (Incremental Static Regeneration, which rebuilds only the pages whose content changed). It is the most popular companion to a headless CMS.
- Astro — built specifically for content-heavy sites, using an island architecture that ships as little JavaScript to the browser as possible, producing extremely light and fast article pages.
- Nuxt — the Vue equivalent of Next.js with comparable capabilities, ideal for teams whose expertise is in Vue.
The typical workflow: editors save content in the CMS; the frontend fetches it through the API at build time (SSG) or request time (SSR); the resulting pages are deployed. Many teams add a webhook so the CMS automatically triggers a rebuild every time someone clicks publish.
Comparison Table: Regular WordPress vs Headless CMS
| Aspect | Regular WordPress | Headless CMS |
|---|---|---|
| Architecture | Monolithic — backend + frontend combined | Content backend decoupled from frontend via API |
| Presentation | Ready-made PHP themes, works instantly | Frontend must be custom-built (Next.js, Astro, Nuxt…) |
| Channels | Primarily the website | Web, apps, signage — omnichannel |
| Skills required | Usable without writing code | Requires frontend developers |
| SEO | Ready plugins such as Yoast, Rank Math | Implemented entirely in code |
| Content preview | Built in, one click | Must be engineered separately |
| Performance | Depends on theme/plugins, relies on caching | Very high with SSG plus a CDN |
| Starting cost | Low — budget shared hosting is enough | Higher — frontend development plus two systems to run |
| Hosting | Ordinary PHP/MySQL shared hosting | VPS for the CMS (Node.js) + somewhere for the frontend |
Who Should Stay with Regular WordPress?
Traditional WordPress remains the right choice for most people, especially:
- Company sites, shops and blogs whose only channel is the website itself.
- Small teams or business owners who maintain the site themselves without a dedicated developer.
- Budget-constrained projects that need to launch quickly using ready themes and plugins.
- Sites that lean heavily on the WordPress ecosystem — WooCommerce, booking systems, SEO plugins and the like.
Who Should Go Headless?
- Teams with in-house frontend developers who want full control of the tech stack.
- Businesses that must deliver one content source to several channels — web, mobile apps and other displays.
- High-traffic sites that need static-site-level performance.
- Organizations with clearly separated content and development teams working in parallel.
- Projects that plan future redesigns or frontend rewrites without ever migrating content.
Hosting: Shared Hosting or VPS?
The final — and very practical — question is where to run all of this. The answer splits neatly along the technology of the CMS itself.
Regular WordPress (including the backend of a headless WordPress setup) runs on PHP + MySQL, so ordinary shared hosting is all you need. AsiaGB hosting plans come with the DirectAdmin control panel, one-click WordPress installation through Softaculous, SSD storage, a 99% uptime guarantee and twice-monthly automated backups (on the 1st and 15th of each month) — a cost-effective home for any standard WordPress site.
Node.js-based headless CMS platforms such as Strapi, Directus, Payload and Ghost need a more controllable environment: a specific Node.js version, a long-running process and a reverse proxy. That makes a VPS with full root access the natural fit. AsiaGB Linux VPS plans start at 500 THB/month with SSD storage and a choice of Thailand or Singapore datacenters for low latency in Southeast Asia. Our guide Running Node.js on a VPS with PM2 shows how to keep the CMS process alive and restart it automatically after a reboot.
The frontend, once built into static files, can live on the same hosting account, on the same VPS as the CMS, or on any static hosting service. And if you are still weighing which CMS fits your project, our review of popular CMS platforms for shared hosting is a good next read.
Frequently Asked Questions (FAQ)
How is a headless CMS different from regular WordPress?
Regular WordPress bundles the content-management backend and the presentation frontend (themes) into a single system. A headless CMS only stores and manages content, then delivers it as data over an API (REST or GraphQL) to a separately built frontend such as a Next.js site or a mobile app, which handles all rendering itself.
Can WordPress be used as a headless CMS?
Yes. WordPress has included a built-in REST API since version 4.7, and you can install the WPGraphQL plugin to add a GraphQL endpoint. Editors keep using the familiar admin screen to write content, while the public-facing site is built with another framework that pulls content through the API.
Who should use a headless CMS?
Teams with their own frontend developers, businesses that publish the same content to multiple channels, projects that need full control over performance and the tech stack, and larger organizations where content and development teams work in parallel. For a typical company site or blog without a developer, regular WordPress is usually the better value.
Does going headless hurt SEO?
Not necessarily. If the frontend uses Server-Side Rendering or Static Site Generation — for example with Next.js or Astro — search engines receive fully rendered HTML just like a normal site. However, developers must implement meta tags, sitemaps and structured data themselves, whereas WordPress offers ready-made SEO plugins.
What do I need to host a headless CMS?
Popular self-hosted options such as Strapi, Directus, Payload and Ghost run on Node.js, so they fit best on a VPS with root access where you can install Node.js, a database and a process manager like PM2. Headless WordPress keeps its backend on ordinary PHP/MySQL shared hosting with DirectAdmin.
Is a headless CMS free or paid?
Both models exist. Open-source options such as Strapi, Directus, Payload and Ghost can be installed on your own server without license fees. SaaS platforms such as Contentful and Sanity offer free entry tiers and charge as usage grows. For the self-hosted route, the main costs are the server and development time.
Ready to run your CMS?
Start WordPress today on AsiaGB DirectAdmin hosting (SSD, 99% uptime), or pick a Linux VPS from 500 THB/month for Strapi, Ghost and other Node.js headless platforms. Thailand and Singapore datacenters with low latency across Southeast Asia.
View Hosting Plans