PHP Headless CMS: Honest Options for PHP Developers (2026)
UnfoldCMS, Statamic, Craft CMS, October CMS, Pimcore — no Node.js required
Most headless CMS guides point you at Strapi, Payload, or Directus. All three run on Node.js. If your stack is PHP — Laravel, Symfony, shared hosting, VPS — you're looking at a list of tools built for a different runtime. This page is for PHP developers who want headless content delivery without switching languages.
Five PHP-native headless CMSes exist in 2026 that are production-ready. Here's the honest picker.
TL;DR — the PHP headless CMS picker
For most PHP/Laravel teams: UnfoldCMS (free Core, React admin, 42-endpoint REST API out of the box). For teams that need flat-file + editor polish: Statamic (REST API via paid addon, mature ecosystem). For enterprise budgets: Craft CMS (GraphQL, mature, expensive). Everything else is a corner case.
| 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 Pro + $99/yr | Content-first teams, flat-file workflow |
| Craft CMS | PHP + Yii2 | GraphQL (paid plan) + REST | $299/site Pro | Enterprise, complex content modelling |
| October CMS | Laravel + Twig | REST plugin (third-party) | Free core + paid plugins | Existing October projects, plugin marketplace |
| Pimcore | Symfony | REST + GraphQL | Open source (self-host) | Enterprise PIM/DAM use cases |
Why PHP headless at all
Three real reasons to stay on PHP for 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 either a separate server or a reverse proxy. That's operational 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. You don't gain anything by switching to Node except Node's problems.
The tradeoff is community size: Strapi has 63,000 GitHub stars; the PHP headless options have fewer. If community ecosystem size is a priority, factor that in. If your team runs PHP anyway, the community size delta disappears — you're already in the PHP ecosystem.
UnfoldCMS — REST API built in, modern admin
UnfoldCMS is the only PHP CMS on this list that ships headless-ready out of the box with no addon required. The v1 API covers 42 endpoints across posts, pages, categories, menus, search, settings, and media — authenticated via Laravel Sanctum tokens and signed HMAC webhooks for cache invalidation.
The admin is React 19 + shadcn/ui + Inertia 2 — not a Blade/Twig template. 51 shadcn/ui components across 205 admin pages. Editors get a modern UI; developers get the same component library they'd use on the public site.
Stack: Laravel 12, MySQL or SQLite, PHP 8.2+. Runs on a $5/month VPS, Hetzner, DigitalOcean, or shared hosting with PHP-FPM.
Pricing: Core tier is free and source-available. Pro and Agency are one-time licenses. No per-month API fees, no seat costs, no bandwidth charges.
What the API covers:
- Public read:
GET /api/v1/posts,/api/v1/posts/{slug},/api/v1/pages/{slug},/api/v1/categories,/api/v1/menus/{slug},/api/v1/search,/api/v1/settings - Authenticated write: create/update/delete via Sanctum token
- Outgoing webhooks: HMAC-signed, fired on publish/update/delete
- Media: Spatie Media Library with image transformations
What's missing: GraphQL is not available — REST only. No SDK packages for specific frameworks yet (you use plain fetch() or Axios). Content versioning/rollback is not yet shipped. If GraphQL or rollback history is a hard requirement, look at Craft CMS.
See the full REST vs GraphQL CMS comparison to decide whether REST covers your needs.
Pick UnfoldCMS if — you want headless PHP with zero addon fees, a modern React admin, and REST API coverage for the standard content types a CMS ships.
Statamic — mature, flat-file, REST via addon
Statamic is the most polished PHP CMS for content-first teams. Built on Laravel, content stored as Markdown + YAML by default (flat-file), editor UX that rivals commercial SaaS CMSes, and a genuine ecosystem of addons.
The headless story has one catch: REST API access requires the Statamic REST API addon, which is free but a separate installation step. GraphQL is also available via addon. Once installed, the API covers entries, terms, assets, globals, nav, forms, and users.
Pricing: Statamic Solo is free for single-developer personal projects. Statamic Pro is $349/site, with $99/year renewal after the first year for updates and support.
Pick Statamic if — your content editors need the best PHP CMS editing experience in 2026, you want flat-file storage with Git versioning, and the per-site licensing model fits your project economics. See our UnfoldCMS vs Statamic comparison for the full breakdown.
Craft CMS — GraphQL, mature, enterprise
Craft CMS is the oldest and most mature PHP headless CMS. PHP + Yii2 framework, a polished control panel, and a genuine GraphQL API (on paid plans). Content modelling in Craft is the most flexible on this list — custom fields, matrix blocks, nested structures, multi-site out of the box.
Pricing: Craft Solo is free for single-site. Craft Pro is $299/project, plus plugin marketplace costs for extended features (caching, SEO, forms, etc.). Craft Cloud (managed hosting) adds monthly fees.
The tradeoff: Craft assumes you're building a bespoke site. For multi-site agency work or standard blog/marketing CMS use cases, the custom field setup overhead is real. UnfoldCMS and Statamic ship those use cases faster.
Pick Craft if — you need GraphQL, complex content modelling (matrix fields, nested structures), enterprise PHP credentials, or you're already in the Craft ecosystem.
October CMS — traditional CMS, REST via plugin
October CMS has been around since 2014. Built on Laravel, Twig templates, a plugin marketplace. The headless/REST API is not built in — it's available through third-party plugins (the most maintained being the October CMS REST API plugin).
Honest assessment: October CMS is a traditional CMS that was adapted for headless via plugins, not designed headless-first. The plugin quality varies. If you're starting a new project with headless as a requirement, the other options on this list are better fits. October CMS is the right pick if you're maintaining an existing October project or specifically need something from its plugin marketplace.
Pick October CMS if — you're already running October, a specific plugin covers your requirement, or you want traditional CMS shape on Laravel without switching tools.
Pimcore — Symfony, enterprise PIM/DAM
Pimcore is an open-source Symfony application covering CMS, PIM (Product Information Management), DAM (Digital Asset Management), and ecommerce. REST and GraphQL APIs both included. Free to self-host.
The scope is enterprise. Pimcore's CMS is one module of a much larger platform. For teams that need product catalog management, multi-channel publishing, and complex data management alongside their CMS — Pimcore is worth evaluating. For teams that want a blog, a marketing site, or standard content delivery via API — Pimcore is far more than needed and the learning curve reflects it.
Pick Pimcore if — you have enterprise content + product data requirements, Symfony expertise on the team, and a genuine need for PIM/DAM alongside CMS.
PHP vs Node.js headless CMS — the honest comparison
The Node.js options (Strapi, Payload, Directus) are excellent. This isn't a "PHP is better" argument. It's a "use what fits your team" argument.
| Factor | PHP headless CMS | Node.js headless CMS |
|---|---|---|
| Hosting | Shared hosting, any VPS, PHP-FPM | Needs Node process, VPS or Docker |
| Team fit | PHP/Laravel developers | JavaScript/TypeScript developers |
| Ecosystem | Composer, Spatie, Eloquent | npm, Prisma, TypeScript-first |
| API standard | REST (PHP options), GraphQL (Craft/Pimcore) | REST + GraphQL (most Node options) |
| TypeScript admin | UnfoldCMS only | Payload, Directus, Strapi |
| Community size | Smaller for each tool | Larger (Strapi 63k stars) |
| Dev cost | Lower if team is PHP-native | Lower if team is Node-native |
If your team runs PHP, adding a Node CMS means hiring/training for a second runtime. The administrative overhead often outweighs the community-size advantage. See the Best Laravel CMS Options in 2026 post for more on the PHP-specific decision tree.
Frontend framework integrations
PHP headless CMSes serve content via REST or GraphQL to any frontend. The frontend can be any JavaScript framework — there's no coupling to the CMS's backend language.
- Next.js — fetch from UnfoldCMS REST API in
getServerSidePropsor React Server Components. See Best CMS for Next.js. - Astro — fetch at build time via
getStaticPaths. Works well with UnfoldCMS's REST endpoints. See Best CMS for Astro. - SvelteKit — server load functions call the REST API directly. See Best CMS for SvelteKit.
- Nuxt —
useFetchcomposable hits the REST API in SSR or SSG mode. See Best CMS for Nuxt. - Remix / React Router v7 — loader functions fetch from the PHP CMS API. See Best CMS for Remix.
The PHP CMS runs on one server. The frontend deploys to Vercel, Netlify, Cloudflare Pages, or any static host. The separation is clean — no runtime dependency between the two.
People Also Ask
Is there a PHP headless CMS that doesn't require Node.js?
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 teams on Laravel. Craft CMS is the best PHP option for GraphQL and enterprise content modelling.
Can I use Laravel as a headless CMS?
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.
Does UnfoldCMS have a GraphQL API?
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).
What is the best self-hosted PHP headless CMS?
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 CP, per-site license). For enterprise: Craft CMS (GraphQL, complex content modelling). See the best self-hosted CMS guide for the full comparison across PHP and Node options.
Can I connect a PHP headless CMS to a JavaScript frontend?
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.
How to decide
- Do you need GraphQL? Yes → Craft CMS (PHP) or Payload/Directus (Node). No → all PHP options work.
- Do you need flat-file / Git-based content? Yes → Statamic. No → UnfoldCMS or Craft.
- Is budget one-time vs recurring important? Free tier needed → UnfoldCMS Core. One-time license → UnfoldCMS Pro or Craft Pro. Per-site subscription → Statamic.
- Is this a standard content site (blog, marketing, docs)? Yes → UnfoldCMS. No, complex custom content models → Craft or Pimcore.
- Enterprise PIM/DAM scope? Yes → Pimcore. No → any of the others.
Try UnfoldCMS
UnfoldCMS ships a PHP/Laravel headless CMS with 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. Try the live demo or see pricing.
Related: I Tested 5 PHP Headless CMSes — Here's What Actually Works, Best CMS for Laravel in 2026, The Complete Guide to Headless CMS in 2026.