Automad
Flat-file PHP CMS with a built-in template engine. No database required — content lives in text files, editable through a browser-based dashboard with a live WYSIWYG editor
Quick Start
docker run -d -p 8080:80 -v automad_data:/var/www/html/data marcantondahmen/automad:latest Overview
Automad is a flat-file CMS written in PHP. Content lives in plain text files on disk rather than in a database, which means the entire site can be deployed by copying files to a web server. No MySQL, no Redis, no environment variables to configure for a database connection. If your hosting supports PHP, Automad runs on it.
The browser-based dashboard provides a WYSIWYG editor with live preview. Editors see changes as they make them without publishing to a staging environment first. The interface is straightforward enough for non-technical users to maintain content without guidance, which makes Automad a reasonable choice for handing off a small site to a client who does not need a complex workflow.
Templating is handled by Automad’s own lightweight language, which uses a tag-based syntax close to standard HTML. Theme developers can pick it up quickly without learning Twig, Blade, or another abstraction layer. A small set of community themes exists, though the ecosystem is significantly smaller than flat-file alternatives like Grav or statically-generated options like Hugo.
The tradeoffs of flat-file storage show up at scale. Relational content, taxonomy structures with many cross-references, or sites with thousands of pages start to feel constrained without a proper query layer. Automad is sized for small to medium sites: portfolios, documentation, small business pages, and personal blogs where the no-database simplicity is worth more than the flexibility of a full CMS stack.
With 898 GitHub stars, this is a niche tool maintained by a solo developer. It works well within its scope, but the limited contributor base is worth factoring in if you are building something that will need long-term maintenance.
Automad: Pros & Cons
| Pros (The Wins) | Cons (The Friction) |
|---|---|
| No database: Content in flat files; deploy by copying files. | Doesn’t scale well: Complex relational content or large volumes are awkward. |
| WYSIWYG with live preview: Dashboard editor works without plugin installs. | Small ecosystem: Few third-party themes or plugins available. |
| Simple templating: Tag-based syntax; designers learn it without a framework. | No multi-author roles: Built for single editor or very small teams. |
| Runs on shared hosting: Any PHP host works; no special server config. | Solo-maintained project: 898 stars; limited outside contributor activity. |
Use Cases
Specific ways to use Automad for your workflow.
Deployment Strategy
Recommended ways to host Automad in your own environment.