Kirby CMS Alternatives: 5 Options When You Outgrow Flat Files

Kirby is a well-loved flat-file CMS: no database, content in files, a clean PHP templating system, and a one-time license. Developers pick it for small-to-medium sites where the file-based model just works. But it's not for everyone. Some teams outgrow the flat-file approach, want a database-backed content model, need a modern React admin, or want a headless API instead of Kirby's PHP-rendered front end. If that's you, here are the alternatives worth a look — and where each one fits.

TL;DR: If you liked Kirby's pay-once model but want a database-backed, headless CMS with a modern admin, look at UnfoldCMS. If you want to stay flat-file, Grav or Statamic are closest in spirit. For a JavaScript-native headless option, Payload or Directus. This post breaks down five, with the honest tradeoffs.

Why leave Kirby?

Kirby is good software. People move off it for specific reasons, not because it's bad:

• Flat-file limits. Content in files is simple until you need complex queries, relationships, or thousands of entries. A database handles that better.
• PHP-templated front end. Kirby renders your site in PHP. If you're building with React, Vue, or a static generator, you want a headless API, not a template engine.
• Admin feel. The Kirby Panel is clean but minimal. Some teams want a richer, modern admin.
• Scaling content ops. Scheduling, roles, a media library with variants — these get built-out further in database CMSes.

If none of these bite you, stay on Kirby. If one does, read on.

The alternatives

1. UnfoldCMS — pay-once, database-backed, headless

The closest match if what you liked about Kirby was owning your CMS with a one-time cost, but you've hit the flat-file ceiling. UnfoldCMS is a self-hosted CMS built on Laravel with a database (SQLite or MySQL), a React + shadcn/ui admin, and a REST API at /api/v1/*.

• Same ownership model — self-hosted, your server, your data.
• Database, not flat files — real queries, categories, relationships, scheduled publishing.
• Headless-ready — serve content to any front end over REST, or use its built-in themes.
• Modern admin — 51 shadcn/ui components, not a stripped-down panel.

Honest limits: it's REST-only (no GraphQL), has no revision history, and it's a database CMS — so you lose the "content is just files in git" simplicity that draws people to Kirby in the first place.

2. Grav — the flat-file sibling

If you want to stay flat-file, Grav is the natural neighbor. Also database-free, also PHP, with a large plugin ecosystem and a Twig-based templating system. It's a lateral move from Kirby, not an escape from flat files — so pick it only if the flat-file model is what you want to keep.

3. Statamic — flat-file with a Laravel backbone

Statamic is flat-file (with an optional database "Eloquent driver") built on Laravel. It has a polished control panel and strong templating. It's commercial, with a per-site license. Good middle ground: Kirby-like content model, more built-in features, Laravel underneath. See Statamic vs WordPress for how it compares to the mainstream.

4. Payload — TypeScript-native headless

If you're moving toward a JavaScript stack, Payload is a code-first, TypeScript headless CMS. You define collections in code, it generates an admin and an API. Self-hostable, developer-focused. The tradeoff versus Kirby: you're now in Node-land, defining schemas in TypeScript rather than dropping content files.

5. Directus — headless on your existing database

Directus wraps a REST/GraphQL API and an admin around an existing SQL database. If you already have data in Postgres or MySQL and want a CMS layer on top, it shines. It's more of a data platform than a content-first CMS, which can be overkill for a simple site but powerful for data-heavy ones.

Quick comparison

How to choose

• Keep flat-file + pay-once feel → Grav or Statamic.
• Database + pay-once + headless, PHP-friendly → UnfoldCMS.
• All-in on TypeScript → Payload.
• CMS over an existing SQL database → Directus.

The real question is whether you're leaving flat files or leaving Kirby specifically. If it's the flat-file model that's holding you back, a database CMS like UnfoldCMS or Directus is the move. If you just want a different flat-file experience, Grav and Statamic are home.

FAQ

What's the closest CMS to Kirby? For staying flat-file: Grav and Statamic are the closest in model and spirit. For keeping the pay-once, self-hosted feel while moving to a database and a headless API: UnfoldCMS.

Is there a Kirby alternative with a database? Yes — UnfoldCMS (Laravel, SQLite/MySQL), Directus, and Payload are all database-backed. They trade Kirby's file simplicity for queryable content and richer admin features.

Are these self-hosted like Kirby? UnfoldCMS, Grav, Statamic, Payload, and Directus can all be self-hosted. You keep your data on your own server, just like Kirby.

Which is cheapest long-term? Pay-once options (UnfoldCMS, Statamic per-site, Kirby itself) avoid recurring fees. Open-source options (Grav, Payload, Directus) are free but you carry all hosting and maintenance yourself.

Bottom line

Kirby is excellent for what it is — a flat-file, pay-once, PHP CMS. Teams leave it when the flat-file model or the minimal panel stops fitting. If you want to stay flat-file, Grav and Statamic are home. If you're hitting the database ceiling but still want to own your CMS with a one-time cost, UnfoldCMS is the closest match. For a JavaScript-native path, Payload or Directus.

See UnfoldCMS in the demo or read the self-hosted CMS guide.

Related: Best self-hosted CMS platforms · Statamic vs WordPress · Flat-file CMS vs database CMS