Kirby
German file-based CMS with no database at all, licensed once per site rather than by subscription
Quick Overview
| Company | Bastian Allgeier GmbH |
|---|---|
| Category | Content Management |
| Headquarters | Berlin, Germany |
| Founded | 2012 |
| EU Presence | Yes - Germany (EU) |
| Data Location | Your own server; content is files |
| Open Source | Source-available, commercial licence |
| GDPR Compliant | Yes |
| Self-Hosting | Yes - self-hosted only |
| Main Features | Flat-file content storage, no database, customisable panel, full template control, blueprints for content structure, multi-language, PHP-based |
| Pricing | Free for local development / EUR 109 one-off per production site |
| Best For | Designers and developers building bespoke sites without database overhead |
| Replaces | WordPress, Craft CMS, Statamic |
Detailed Review
Kirby stores content as text files in folders. There is no database, no migration when you move the site, and no separate backup strategy — copying the directory copies everything, content and structure together, and the whole site can live in version control.
It is made by a small German company in Berlin and sold for a one-off fee per site rather than a subscription, which is increasingly unusual and is a substantial part of its appeal.
No Database
The practical consequences are larger than they sound. Deployment is a file copy. Staging is a branch. There is no database to secure, tune, back up separately or corrupt. Content changes appear in Git diffs alongside code, so a site's entire history is in one place.
For sites up to a few thousand pages this is simpler and faster than the database-backed alternative. Beyond that, the flat-file model starts to work against you.
Complete Template Control
Kirby imposes no front-end structure. You write the templates in PHP and the CMS gets out of the way, which is why it appeals to designers and studios producing bespoke sites rather than assembling themes. Blueprints define what editors see in the panel, so the editing interface is shaped to each project.
The Licence
A single payment of EUR 109 per production site, with no renewal. Over five years that is dramatically cheaper than any subscription CMS, and it is the reason many small studios standardise on it for client work. Local development is free, so you only pay when a site goes live.
Limitations to Consider
Flat-file storage does not suit content-heavy sites with complex relational queries or very large catalogues — a database CMS is the right tool there. Kirby is source-available rather than open source, so the code is readable but the licence is commercial. The ecosystem is small, and it is essentially a small-team product, which is a consideration for long-lived critical sites.
Who Should Use Kirby
Design studios and freelance developers building bespoke client sites, and anyone who wants a CMS with no database, no subscription and complete control over the templates.
Pros and Cons
Pros
- No database: deployment and backup are file copies
- Content lives in version control with code
- One-off EUR 109 licence per site
- Total control over templates
- Editing panel configured per project
Cons
- Not suited to very large or relational content
- Source-available, not open source
- Small ecosystem and small team
Alternatives to Kirby
Other European content management worth comparing before you decide:
Storyblok
Austria · Headless CMS with a genuine visual editor
Strapi
France · Open-source headless CMS you fully self-host
Ghost
United Kingdom · Open-source publishing with memberships built in
TYPO3
Germany · Enterprise CMS built for multi-site and multi-language estates
See all European content management or compare them directly against WordPress on our alternatives page.
Frequently Asked Questions
Correct. Content is stored as text files in folders, so deployment is a file copy, backups are a directory copy, and content history lives in Git alongside your code.
EUR 109 once per production site, with no renewal or subscription. Local development is free, so you pay only when a site goes live.
It is source-available: you can read and modify the code, but it is sold under a commercial licence rather than an OSI-approved open-source one.
For very large content catalogues or sites needing complex relational queries, where a database-backed CMS such as TYPO3 or a headless platform will handle the load far better.