PHP-native, no Node.js required

PHP Headless CMS — Honest Options for PHP Developers

Most headless CMS guides point you at Strapi or Payload. Both run on Node.js. If your stack is PHP, here's the developer-honest picker for 2026.

Laravel 12 backend 42-endpoint REST API built-in Free Core tier
42
REST API endpoints
$0
Core tier cost
8.2+
PHP minimum
$5
min. monthly hosting

The PHP Headless CMS Picker

Five PHP-native headless CMSes exist in 2026 that are production-ready. For most PHP/Laravel teams: UnfoldCMS (free Core, REST API built-in, React admin). For flat-file + editor polish: Statamic. For enterprise GraphQL: Craft CMS.

CMS Stack Headless API Pricing Best for
UnfoldCMS Laravel + React + shadcn/ui REST (42 endpoints, built-in) Core free; one-time Pro Modern PHP teams, no Node, no subscription
Statamic Laravel + Antlers/Blade REST via paid addon $349/site + $99/yr Content-first, flat-file workflow
Craft CMS PHP + Yii2 GraphQL (paid) + REST $299/site Pro Enterprise, complex content modelling
October CMS Laravel + Twig REST plugin (third-party) Free core + paid plugins Existing October projects
Pimcore Symfony REST + GraphQL Open source (self-host) Enterprise PIM/DAM use cases

Comparison reflects public documentation and API source inspection as of June 2026.

Why Stay on PHP for Headless?

This isn't a "PHP is better" argument. It's a "use what fits your team" argument. Three real reasons to keep PHP as your headless CMS backend.

Your Hosting Is PHP-Native

Shared hosting, most VPS setups, and cPanel environments run PHP-FPM. Running a Node.js process alongside them means a separate server or a reverse proxy — complexity that earns nothing for a content API.

Your Team Knows PHP

Hiring Laravel developers is straightforward. Asking a PHP team to maintain a Node.js CMS means onboarding a second runtime, a different package manager, and different deployment patterns.

The Ecosystem Fits

Spatie's Media Library, Laravel Sanctum, Eloquent, Composer — the PHP ecosystem has solved every CMS infrastructure problem cleanly. Switching to Node adds Node's problems without adding value.

Recommended for PHP teams

UnfoldCMS — REST API Built In, Modern Admin

The only PHP CMS on this list that ships headless-ready out of the box — no addon required. 42 endpoints covering posts, pages, categories, menus, search, settings, and media. Authenticated via Laravel Sanctum + HMAC-signed webhooks.

  • Public read: posts, pages, categories, menus, search, settings
  • Authenticated write: create/update/delete via Sanctum token
  • Outgoing webhooks: HMAC-signed, fired on publish/update/delete
  • React 19 + shadcn/ui admin — 51 components, 205 admin pages
  • Core tier free — no per-month API fees, no seat costs
GET /api/v1/posts
// Public endpoints — no auth needed
GET /api/v1/posts          // paginated post list
GET /api/v1/posts/{slug}   // single post by slug
GET /api/v1/pages/{slug}   // page content
GET /api/v1/categories    // category tree
GET /api/v1/menus/{slug}   // nav menu items
GET /api/v1/search        // full-text search

// Authenticated write (Sanctum token)
POST   /api/v1/admin/posts   // create post
PUT    /api/v1/admin/posts/{id}
DELETE /api/v1/admin/posts/{id}

// HMAC-signed outgoing webhooks
POST https://your-app.com/hook
// X-Unfold-Signature: sha256=...

PHP vs Node.js Headless CMS

Strapi, Payload, and Directus are excellent tools — built for Node.js teams. If your stack is PHP, here's what actually changes.

PHP Headless CMS

  • Hosting: shared hosting, any $5/month VPS, PHP-FPM — no extra processes
  • Team fit: PHP/Laravel developers on day one — no new runtime to learn
  • Ecosystem: Composer, Spatie packages, Eloquent ORM — all CMS infrastructure solved
  • Admin UI: UnfoldCMS ships a powerful React + shadcn/ui admin — 51 components, 205 pages
  • Cost: lower total cost when your team already knows PHP
  • GraphQL: only via Craft CMS or Pimcore — REST is the default
  • Community size: smaller than Strapi (60k+ GitHub stars)

Node.js Headless CMS

  • Hosting: needs a running Node process — VPS or Docker, no shared hosting
  • Team fit: ideal for JS/TS teams — friction if your team is PHP-native
  • Ecosystem: npm, Prisma, TypeScript-first — strong if you're already in JS
  • Admin UI: Payload, Directus, and Strapi all ship modern React admins
  • GraphQL: supported natively in most Node CMSes
  • Community: Strapi has 60k+ GitHub stars — largest headless CMS community
  • Cost: higher operational cost if adding Node to a PHP-first setup

Pick based on your team's runtime — not community size. A PHP team maintaining a Node CMS pays a hidden tax every day.

Connect Any Frontend Framework

The PHP CMS runs on one server. Your frontend deploys anywhere — Vercel, Netlify, Cloudflare Pages, or static hosting. No runtime dependency between the two.

Next.js

Fetch in getServerSideProps or React Server Components.

Best CMS for Next.js →

Astro

Fetch at build time via getStaticPaths.

Best CMS for Astro →

SvelteKit

Server load functions call the REST API directly.

Best CMS for SvelteKit →

Nuxt

useFetch composable hits the REST API in SSR or SSG mode.

Best CMS for Nuxt →

Remix / React Router

Loader functions fetch from the PHP CMS API.

Best CMS for Remix →

Any Frontend

Plain fetch() or Axios. No SDK required — it's just JSON over REST.

See the full API →

How to Decide in 5 Questions

Answer these in order. The first "yes" tells you which CMS to pick.

1. Do you need GraphQL?
Yes → Craft CMS (PHP) or Payload/Directus (Node.js). No → all PHP options work.
2. Do you need flat-file / Git-based content?
Yes → Statamic. No → UnfoldCMS or Craft.
3. Is budget one-time vs. recurring important?
Free tier needed → UnfoldCMS Core. One-time license → UnfoldCMS Pro or Craft Pro. Per-site subscription → Statamic.
4. Is this a standard content site (blog, marketing, docs)?
Yes → UnfoldCMS. No, complex custom content models → Craft or Pimcore.
5. Enterprise PIM/DAM scope?
Yes → Pimcore. No → any of the others.

Try UnfoldCMS — PHP Headless CMS, Free Core

42 REST endpoints, HMAC webhooks, a React + shadcn/ui admin, and a free Core tier. No Node.js, no subscription, no per-API-call pricing. Runs on a $5/month VPS.

Frequently Asked Questions

Yes — UnfoldCMS, Statamic, Craft CMS, October CMS, and Pimcore all run on PHP with no Node.js dependency. UnfoldCMS and Statamic are the strongest options for Laravel teams. Craft CMS is the best PHP option for GraphQL and enterprise content modelling.
You can build a headless CMS on Laravel from scratch — but why? UnfoldCMS and Statamic both ship on Laravel with headless APIs already built. Using one of those saves 2–6 months of building posts, pages, media, SEO, users, roles, permissions, webhooks, and admin UI yourself.
No — UnfoldCMS ships a REST API (42 endpoints) via Sanctum authentication. GraphQL is not available. If GraphQL is a hard requirement, use Craft CMS (PHP) or Payload/Directus (Node.js).
For most teams: UnfoldCMS (free Core, REST API, modern shadcn/ui admin, runs on $5/month VPS). For content-first editorial teams: Statamic (flat-file, polished control panel, per-site license). For enterprise: Craft CMS (GraphQL, complex content modelling).
Yes — and this is exactly the headless model. The PHP CMS serves JSON via REST or GraphQL. The JavaScript frontend (Next.js, Astro, SvelteKit, Nuxt, Remix) fetches that JSON and renders it. The two run independently, deploy independently, and scale independently.