Guide
The best flat-file CMS in 2026
Five flat-file content management systems worth your time, what each is genuinely good at, and where each one will frustrate you. Written by the makers of one of them — which is exactly why every entry lists real tradeoffs.
A note on who wrote this. We make Total CMS, one of the five. That is a conflict of interest, so rather than pretend otherwise we have marked our own entry, listed real reasons to choose the others, and priced everything from each vendor's own page. If you only take one thing from this page, take the recommendation in the "How to choose" section — it does not always say us.
A flat-file CMS stores content as files on disk instead of rows in a database. No MySQL to provision, back up, or keep in sync with your files. A site becomes a folder: copy it, commit it to git, roll it back. The tradeoff is that flat files are less suited to very large datasets and to features that assume relational queries, and the ecosystems are smaller than WordPress's by orders of magnitude.
The short version: Grav if you want free and open source. Kirby if you want a long track record and plain PHP templates. Statamic if you already work in Laravel. Publii if you want a desktop app that publishes a static site. Total CMS if you want a commercially supported product that runs on ordinary hosting.
The options
5 to consider
-
Free, MIT-licensed, and unusually far ahead on AI agent tooling.
Strengths
- Genuinely free and MIT licensed — modify, redistribute, white-label, no fee
- First-party REST API, a first-party MCP server exposing 67 tools, and official Claude Code skills. Their tagline is "A CMS for humans & agents"
- Five-layer caching with Redis, Memcached and APCu drivers
- Twig templating, PHP 8.3, Symfony 7 — a modern stack, actively developed
- 479 plugins, 128 themes, and 56 free skeletons that are complete ready-to-run sites
Tradeoffs
- The admin is a separate plugin, and the ground-up rewrite (Admin2) is still self-labelled Alpha
- The REST API is a plugin that is off by default
- Access groups ship empty — you define them yourself in YAML
- Support is a community forum and Discord; there is no paid tier
- Development is concentrated: 90 of the last 100 commits came from the lead developer
-
Fourteen years of continuous shipping, plain PHP templates, no DSL to learn.
Strengths
- Shipping continuously since 2012, now on version 5 with version 6 in alpha
- Templates are plain PHP — no template language, no ceiling on what a template can do
- Blueprints build a bespoke admin panel per page type in YAML
- Multi-language content is built into core
- Over a thousand documentation pages, and a machine-readable security file cataloguing every past advisory with CVSS scores — a rare and genuinely admirable practice
- Free licences for students and educators; discounts for non-profits
Tradeoffs
- Licensed per site and per domain, so multi-site work multiplies cost linearly
- Updates are time-boxed to three years, then a paid upgrade for three more
- The Basic tier requires your (or your client's) revenue to be under €1 million
- Proprietary, not open source — the MIT fallback clause only triggers after a year with no stable release
- No first-party MCP server; the capable one is a community plugin
-
A Laravel package with a genuinely free tier and a superb control panel.
Strengths
- Core is free forever, open source and commercially usable, with every fieldtype and unlimited collections
- Statamic Pro runs indefinitely on non-public domains — excellent for agency and spec work
- The full Laravel ecosystem is available: Eloquent, queues, any Composer package
- Deep content modeling — reusable fieldsets, multiple blueprints per collection, 40+ fieldtypes
- Can move content into a database via a first-party Eloquent driver without changing templates
- A published support policy with concrete end-of-life dates
Tradeoffs
- You are running and maintaining a Laravel application; Composer is listed as a server requirement
- Deploys want a cache-rebuild command and scheduled content needs a per-minute cron
- They publish a list of hosts it does not work on, including GoDaddy and NameCheap
- Free Core allows one admin account and one form, and excludes the APIs and multi-site
- The REST and GraphQL APIs are read-only, and Pro-only
-
Total CMS
OursA standalone commercial CMS that runs on ordinary PHP hosting, with the AI tooling built in.
Strengths
- Runs on any PHP 8.2+ host — no Composer on the server, no cron requirement, no framework to maintain
- Commercial support included, and one vendor responsible for the whole product
- The MCP server, automations, access groups, image processing and REST API are part of the CMS rather than plugins to assemble
- Twig templating with 130+ custom filters and functions
- Editors fill in the fields you modelled, so a client cannot dismantle your layout
- Two years of updates included — longer than Statamic's one
Tradeoffs
- Proprietary and paid; there is no free tier, only a 45-day trial
- The smallest ecosystem and the smallest talent pool of the five
- Multi-language works through locale-keyed fields rather than separate content per locale — Kirby's core approach is more comprehensive
- No GraphQL, and no e-commerce
- Kirby includes three years of updates to our two
-
A desktop app that generates a static site — nothing dynamic runs on your server.
Strengths
- Content is edited in a desktop application and published as static HTML, so there is no CMS running on the server at all
- That makes the production attack surface close to zero, and the output hostable free on Netlify, GitHub Pages or S3
- No PHP requirement on the host whatsoever
- Free and open source
Tradeoffs
- It is a fundamentally different model — you must have the desktop app to publish, so there is no browser-based editing for clients
- Multiple editors is awkward by design
- No dynamic server-side features: no forms handling, no logged-in areas, no on-request content
- Not comparable to the others for client work where the client edits their own site
How to choose
Pick on constraints, not on feature counts. In practice one of these usually decides it:
- If the budget is zero, choose Grav. It is free, MIT licensed, actively developed, and you are not compromising to get that. If you want free but prefer a static output with no server-side CMS at all, choose Publii.
- If your team already writes Laravel, choose Statamic. The framework you would be "burdened" with is the one you already know, which turns the main tradeoff into an advantage.
- If you want the longest track record, choose Kirby. Fourteen years, five major versions, and an unusually disciplined approach to security disclosure.
- If the site must run on whatever hosting the client already pays for, choose Total CMS. No Composer on the server, no cron, no framework upgrade cycle — and someone to call when it breaks.
- If you need multi-language content today, choose Kirby or Statamic. Neither Grav's nor our own story here is as strong.
- If you need e-commerce, none of these is the answer. Look at WooCommerce or Shopify.
And if you are choosing between a flat-file CMS and WordPress rather than between these five, the real question is whether you want to maintain a database and a plugin stack. That is a different decision, and we have written it up separately.
FAQ
Common questions
What is a flat-file CMS?
A content management system that stores content as files on disk — usually Markdown, YAML or JSON — instead of rows in a database. There is no MySQL to install, secure, back up, or keep consistent with your files. A backup is a copy of a folder, and content can live in git alongside your code.
Is a flat-file CMS faster than WordPress?
Often, but not automatically, and the reason is usually simpler than the database. Flat-file systems tend to run less code per request and cache aggressively. A well-tuned WordPress site with good caching can be very fast, and a badly configured flat-file site can be slow. Treat speed as an outcome of how much is running, not of the storage format.
Do flat-file systems work for large sites?
Up to a point, and the point varies. Most of these index content into a cache so reads do not touch the filesystem for every request. For very large datasets — hundreds of thousands of entries — a database genuinely becomes the better tool, and Statamic is unusual in offering a first-party way to move content into one without rewriting templates.
Which flat-file CMS is free?
Grav and Publii are free and open source outright. Statamic has a free Core tier limited to one admin account and one form. Kirby and Total CMS are commercial, with a free unlimited development install and a 45-day trial respectively.
You make one of these. Why should I trust this page?
You should trust it exactly as far as you can check it. Every price and claim here comes from each vendor's own pages, our entry is marked as ours, and the tradeoffs section on our own product lists things our competitors do better — including that Kirby gives three years of updates to our two, and that both Kirby and Statamic handle multi-language content while we do not yet. If you find something inaccurate, tell us and we will fix it.
Head-to-head comparisons
- Total CMS vs Kirby Kirby is one of the best flat-file CMSs there is, and if its philosophy suits you it is a great choice. The question was never whether Kirby is good — it is whether plain PHP templates and a per-site licence match the way you build. Total CMS answers that differently.
- Total CMS vs Statamic Statamic is excellent, and if your team already lives in Laravel it is probably the natural pick. The real question is whether you want a CMS with a framework attached — because that is the trade, and it cuts both ways.
- Total CMS vs Grav Grav is free, fast, MIT licensed and genuinely well built. If budget decides this, go and use it — you will not be cutting corners. What is left to compare is not capability but how much you want to assemble yourself.
- Total CMS vs WordPress WordPress runs 41% of the web and it earned that. This is not a page about WordPress being bad — its core is well built and its ecosystem is unmatched. It is about what you sign up to maintain, and whether that trade suits the site you are building.
- Total CMS vs Craft CMS Craft is a genuinely good CMS with a free tier we cannot match. It is also the closest thing to Total CMS on this site — same language, same templating, same kind of structured content modelling. Which leaves one real question: should your content live in a database?
- Total CMS vs Webflow Webflow's designer is the best visual building tool there is, and nothing here replaces it. But two questions are worth asking before you commit a client's site to it: what can you actually take with you, and who is Webflow building for now?
- Total CMS vs Squarespace Squarespace is very good at what it does, and for a lot of people reading this it is the right answer. This page is not an argument that you should leave it. It is about what happens if you ever want to.
Details verified on . Software and pricing change — check each product's own site for their current details.
Sources
All prices and claims verified from each vendor's own site on 26 July 2026:
- getgrav.org and their GitHub
- getkirby.com/buy and their licence
- statamic.com/pricing and statamic.dev
- getpublii.com
- totalcms.co/pricing — our own
All product names and trademarks belong to their respective owners. We have no affiliation with Grav, Kirby, Statamic or Publii. If anything here is wrong or out of date, tell us and we will correct it.