FlatPress

Flat-file blogging, honestly reviewed. No marketing fluff, just what you get when you run a blog from text files.

TL;DR

• What it is: A flat-file PHP blogging engine — think old-school WordPress, but with zero database requirement. All content lives in text files on your server [README][website].
• Who it’s for: Hobbyists, solo writers, and small-site owners on cheap shared hosting who can’t or won’t provision a MySQL/PostgreSQL instance, and who don’t need the complexity of a full CMS [1][4].
• Cost savings: WordPress.com Personal starts at $9/mo; Ghost Pro at $9/mo for a hosted blog. FlatPress is free (GPL-2.0) and runs on any $3/mo shared hosting plan with PHP support [website][README].
• Key strength: Genuinely no database. Setup is download-unzip-upload, and backup is literally copying a folder. The project has been running since 2006 without a single database migration [4][website].
• Key weakness: The ecosystem is tiny — 209 GitHub stars, a volunteer team with no commercial backing, and third-party plugin/theme coverage is thin compared to Grav, Ghost, or WordPress. If you outgrow it, migration is your problem [README][4].

---

What is FlatPress

FlatPress is a PHP blogging engine that stores everything — posts, comments, settings — in flat text files. No MySQL, no PostgreSQL, no Redis. You download a zip file, upload it to any web server that runs PHP, click through a one-page installer, and you have a working blog. The project describes itself as “a lightweight, easy-to-set-up blogging engine. Plain and simple, just PHP.” [README]

The project launched in 2006 and celebrated its 20th anniversary with the FlatPress 1.5 “Stringendo” release in March 2026 [website]. Two decades of active development on a volunteer, no-VC-funding basis is actually notable — most small open-source CMS projects either die or get abandoned within five years [4].

The team is explicit about their philosophy: FlatPress is maintained by volunteer developers “united by the joy of free software,” with no commercial interest and no guaranteed support SLAs [4]. That’s both a feature (pure open source, no vendor lock-in) and a warning (if something breaks on a Saturday night, the volunteer team is under no obligation to fix it by Monday).

What FlatPress is not: a WordPress replacement for anything serious. It doesn’t have WooCommerce, it doesn’t have an ecosystem of 50,000 plugins, it doesn’t have a managed hosting offer, and it isn’t designed for teams or multi-author publications. It is a single-author or small-team blog, and it does that specific thing reliably.

---

Why people choose it

The honest answer is that most people choose FlatPress for one of two reasons: no database access, or extreme simplicity.

No database access. A huge fraction of cheap shared hosting plans technically support PHP but either don’t include MySQL, charge extra for it, or make provisioning it annoying [1]. FlatPress sidesteps the entire problem. If your host runs PHP, FlatPress runs. The GCO Studios reviewer [1] came to it specifically searching for “a blog system that worked without a database” — and notes that the file-based approach also means faster response times for readers, since the server skips the database query round-trip entirely.

Backup and migration are trivial. If your content lives in a database, backing it up means mysqldump commands, export tools, or a plugin. If your content lives in a folder of text files, backing it up means copying a folder. Moving hosts means uploading that same folder. This is a genuine operational advantage for a solo blogger who doesn’t want to think about database dumps before switching hosting providers [1][4].

20 years of maturity. The FlatPress wiki is explicit: “FlatPress is meant to be a stable software without surprises.” [4] The release cadence is slow and intentional — version 1.4 came in May 2025, version 1.5 in March 2026. You will not install a FlatPress update and discover that it broke your theme or changed the URL structure of your posts. For a personal blog you want to set up once and forget, that matters.

GPL-2.0, genuinely free. No “community vs enterprise” split, no commercial license for features you need, no SaaS upsell. The software is fully open source and the team explicitly “don’t get (or want) money for FlatPress” [4]. The business model is donations, not subscriptions.

What you won’t find in the third-party reviews is anyone choosing FlatPress for its plugin ecosystem, its theme marketplace, or its developer community. The solidx.io flat-file CMS roundup [5] doesn’t even mention FlatPress by name — the tools that get coverage in 2023+ flat-file roundups are Grav and Statamic. FlatPress has a smaller footprint in the conversation than its 20 years of existence would suggest.

---

Features

Based on the README and official website:

Core blogging:

• Post editor with category support and tagging [README]
• Comments with spam protection [README][website]
• RSS feed out of the box [website]
• Archive by month/year [website]
• Multilingual support in 15+ languages including German, French, Japanese, Russian, Portuguese — language packs are community-contributed and adding a new one doesn’t require programming [README]

Themes:

• Powered by Smarty, a mature PHP templating engine [README]
• Custom theme development is documented; the wiki has a theme repository [4]
• The official site itself runs on FlatPress, which functions as a live demo

Plugins:

• Plugin system with widget support [README][website]
• Plugins are stored in the filesystem alongside the core; the wiki lists community-contributed plugins [4]
• The canonical features list from the merged profile includes backup_restore and plugins as the two main feature categories — which tells you something about scope

Technical:

• Runs on PHP 7.1 through PHP 8.4 [README]
• Compatible with Apache, NGINX, or IIS [README]
• PHPStan static analysis and CodeQL security scanning run in CI on every change [README] — for a volunteer project, that’s a meaningful code quality signal
• No database dependency of any kind [README]

What’s notably absent:

• No built-in search beyond basic navigation (third-party plugins exist)
• No media library — images are uploaded directly to the server but there’s no asset manager
• No REST API, no webhooks, no external integration surface
• No multi-user role management for teams
• No built-in SEO meta fields (plugins cover some of this)

---

Pricing: self-hosted math

FlatPress has no SaaS version. There is no cloud tier, no hosted offering, no “FlatPress Pro.” You self-host it or you don’t use it [website]. So the pricing comparison is FlatPress-on-your-own-server versus hosted blogging platforms:

FlatPress:

• Software license: $0 (GPL-2.0)
• Minimum hosting: any shared PHP host, starting around $3–5/mo (Hostinger, Hetzner shared, etc.)
• Database cost: $0 — not required
• Total: ~$36–60/year

WordPress.com Personal: $9/mo ($108/year) — hosted, managed, 6GB storage, basic themes [data not available from provided sources, publicly known pricing]

Ghost Pro Starter: $9/mo ($108/year) — hosted, includes newsletter, limited members [data not available from provided sources, publicly known pricing]

WordPress self-hosted on a VPS: $5–10/mo for a server + database — comparable to FlatPress but adds database management overhead

The honest savings case for FlatPress versus WordPress.com or Ghost Pro is roughly $50–100/year — real money but not a dramatic Zapier-scale arbitrage. The more compelling case isn’t cost but simplicity: FlatPress on $5/mo shared hosting requires no database setup, no Docker, no Node.js, no cloud console. If your entire technical comfort zone is “FTP files to a server,” FlatPress is arguably the only serious option in the self-hosted blog category.

---

Deployment reality check

The install process is genuinely one of the simplest in self-hosted software:

1. Download a zip from flatpress.org
2. Unzip, upload to your web host via FTP or cPanel file manager
3. Browse to the URL, run the web-based installer
4. Write your first post

That’s it. No terminal, no Docker, no package managers [README][website]. The softaculous.com installer demo (linked from the README) means many cPanel-based hosting providers can install it in one click.

Requirements:

• PHP 7.1–8.4 (any modern shared host qualifies) [README]
• A web server — Apache, NGINX, or IIS [README]
• Disk space for your files (minimal)
• No database, no Redis, no message queue

What can go sideways:

The flip side of “runs anywhere” is “you’re on your own for configuration.” There’s no official Docker image, no Helm chart, no one-click VPS deployment. The project assumes you know how to upload files to a web server — a skill that’s increasingly rare [website].

The support structure is a volunteer forum and a wiki [4]. The team is explicit: “We are running the whole project in our free time — we simply can’t guarantee reaction times for emails, GitHub issues or questions on the support forum.” [4] If you hit a weird NGINX rewrite rule issue or a PHP version incompatibility at 11pm before an important post, you’re searching the forum archives.

Plugin quality varies. The plugin ecosystem is community-contributed with no vetting process or compatibility guarantees. An older plugin written for FlatPress 1.2 may or may not work with 1.5 [4].

With 209 GitHub stars, FlatPress sits well below the visibility threshold where you can expect StackOverflow answers or YouTube tutorials. Documentation exists (the wiki is reasonably thorough [4]) but community Q&A resources are thin compared to WordPress or even Grav.

---

Pros and cons

Pros

• Zero database dependency. No MySQL to provision, no connection strings to manage, no database backups to schedule. The entire blog is a folder [README][1].
• Backup is a folder copy. cp -r or rsync and you’re done. Migration between hosts is equally trivial [1][4].
• Works on any PHP host. If the host runs PHP 7.1+, FlatPress runs. This includes ancient shared hosting plans that don’t support Docker or Node.js [README].
• 20 years of intentional stability. Slow release cadence, no breaking changes, “stable software without surprises” — appropriate for a personal blog you want to run and forget [4][website].
• Genuinely free, no upsell. GPL-2.0, volunteer team, no commercial license, no premium tier, no SaaS trap [4].
• PHPStan + CodeQL CI. For a small volunteer project, automated static analysis and security scanning on every commit is above-average code hygiene [README].
• Multi-language support. 15+ languages in the standard package, easy to add more [README].
• Simple comment system included. You don’t need Disqus or a third-party comment service — FlatPress handles comments natively with spam protection [README].

Cons

• Tiny community. 209 GitHub stars as of this writing [merged profile]. Compared to Grav (15K+), Ghost (46K+), or WordPress (any metric), FlatPress is niche. If you need an answer fast, you may not find one.
• No commercial backing. The team explicitly earns nothing from the project [4]. Support timelines are “best effort.” If the project’s two or three core contributors get busy with their day jobs, releases slow down.
• Plugin and theme ecosystem is thin. The plugin directory exists but the catalog is a fraction of what Grav or WordPress offer. Custom theme development requires Smarty template knowledge [README][4].
• No REST API or integration surface. You can’t connect FlatPress to Zapier, Make, or a headless frontend framework. It’s a self-contained monolith, full stop.
• No media management. Images are uploaded directly to the server. There’s no asset browser, no image resizing, no CDN integration out of the box.
• Not indexed in mainstream “best CMS” roundups. The 2023 flat-file CMS comparison on solidx.io [5] focuses on Grav, Statamic, and October without mentioning FlatPress. Its mindshare is proportional to its star count.
• Scalability ceiling is low. File-based storage doesn’t handle high-concurrency write loads (e.g., viral posts with heavy comment traffic) as well as a database would. Fine for personal blogs, problematic at scale.

---

Who should use this / who shouldn’t

Use FlatPress if:

• You want a personal or small-team blog with zero database dependency, and the existing flat-file CMS options feel overcomplicated for what you actually need.
• Your hosting situation is cheap shared PHP hosting where you can’t or don’t want to provision a database.
• You’re technically comfortable with FTP file uploads but uncomfortable with terminal commands or Docker.
• You want to write, publish, and not think about infrastructure — and you’re fine with a small, stable feature set that changes slowly.
• Backup simplicity matters to you: the ability to rsync a folder as your entire disaster recovery plan.

Skip it (use Grav instead) if:

• You still want flat-file storage but need a more powerful plugin ecosystem, a modern admin interface, and a larger community. Grav has 15K+ GitHub stars, a proper marketplace, and actively maintained documentation [5].

Skip it (use Ghost instead) if:

• You want a modern, fast blogging platform with newsletter integration, membership features, and either self-hosted or managed cloud options. Ghost is opinionated but polished, with a real product team behind it.

Skip it (use WordPress if):

• You need more than a blog — e-commerce, complex page types, team workflows, or a massive plugin ecosystem. WordPress is heavier and requires a database, but the ecosystem is unmatched.

Skip it (use a static generator — Hugo, Jekyll, Eleventy — if):

• You’re a developer comfortable with git-based publishing workflows and want maximum performance with zero server-side processing. Static generators are faster under load and have no PHP surface area to worry about.

---

Alternatives worth considering

• Grav — the most direct flat-file competitor with a dramatically larger ecosystem (15K+ stars, active marketplace, Twig templates) [5]. Steeper initial learning curve than FlatPress but more capable for anything beyond a simple blog.
• Ghost — modern, Node.js-based, with newsletter and membership features. Has a managed cloud option (Ghost Pro) and an active commercial team. Requires a real server or their hosting.
• WordPress (self-hosted) — the obvious comparison. Requires MySQL, more complex to set up, but the plugin ecosystem is essentially limitless and community support is everywhere.
• Pico CMS — another ultra-minimal flat-file PHP blog engine, Markdown-first, even smaller scope than FlatPress. For writers who want Markdown over FlatPress’s textarea editor.
• Statamic — flat-file or database, powerful, built on Laravel, commercial licenses for commercial use [5]. Overkill for a personal blog but excellent for small agencies.
• Hugo / Jekyll — static site generators, not dynamic CMSes. Git-based workflows, no admin UI, maximum performance. Appropriate if you’re a developer who’d rather push a markdown file than log into an admin panel.

For a non-technical user escaping a hosted blogging subscription (WordPress.com, Ghost Pro, Squarespace), the realistic shortlist is FlatPress vs Grav vs Ghost self-hosted. FlatPress wins on simplicity and zero database requirement. Grav wins if you need more extensibility. Ghost self-hosted wins if you want a modern editor and newsletter tools.

---

Bottom line

FlatPress is a legitimate answer to a specific question: “I want a self-hosted blog, I have cheap PHP hosting, I can’t or won’t touch a database, and I want something that works and stays out of my way.” For that question, it’s been a solid answer for 20 years, and the 1.5 “Stringendo” release shows the project is still active and maintained.

What FlatPress isn’t is a mainstream recommendation. The ecosystem is thin, the community is small, and if you hit an edge case, you may be reading 2018 forum posts for answers. Anyone who outgrows a simple personal blog will bump into ceilings — no API, no media management, no team workflows, no scalability path.

The decision really comes down to whether the database requirement is your actual blocker. If it is, FlatPress solves it cleanly. If it isn’t, there are tools with larger communities and more polished experiences.

If the setup is your blocker regardless of which tool you choose, upready.dev deploys self-hosted tools for non-technical founders as a one-time service. Same result, without the learning curve.

---

Sources

1. GCO Studios — “Flatpress Review: Blogging without a Database”. https://gcostudios.com/flatpress-review-blogging-without-a-database/
2. FlatPress Wiki — “About the FlatPress project”. https://wiki.flatpress.org/doc:flatpress:aboutproject
3. Solidx.io — “The best flat-file CMS in 2023?” (Florian Matthias Egerer, Mar 2023). https://www.solidx.io/en/stories/the-best-flat-file-cms-in-2023

Primary sources:

• GitHub repository and README: https://github.com/flatpressblog/flatpress (209 stars, GPL-2.0)
• Official website: https://www.flatpress.org
• FlatPress Wiki: https://wiki.flatpress.org
• Project blog: https://www.flatpress.org/blog.php