HTMLy

Flat-file blogging, honestly reviewed. No marketing fluff, just what you get when you self-host a CMS with no MySQL required.

TL;DR

• What it is: Open-source (GPL-2.0) flat-file PHP blogging platform — no database, no MySQL, just files on disk [README].
• Who it’s for: Bloggers and small-site owners who want a lightweight, self-hosted CMS they can drop onto any PHP host without touching a database. A stronger fit for personal publishing than team operations [README][3].
• Cost savings: Ghost Pro starts at $9–25/month. WordPress.com paid plans start at ~$4/month but scale with features. HTMLy self-hosted runs on shared hosting for $2–5/month, or free if you already have a server [README].
• Key strength: Genuinely no database — installs on 512MB RAM, runs on shared hosting, deploys by uploading a zip file. One Indonesian blogger [4] calls it “powerful and resource-efficient” and stuck with it after cycling through WordPress twice. The LinuxLinks feature survey [3] counts more built-in tools than most flat-file competitors.
• Key weakness: 1,322 GitHub stars signals a small user base. English-language reviews are nearly nonexistent. No plugin marketplace — every feature is baked into the core or you go without [README][3].

---

What is HTMLy

HTMLy is a flat-file blogging platform written in PHP. “Flat-file” means content is stored as plain files on disk rather than rows in a MySQL database. You upload HTMLy to a web host, visit /install.php, follow a short wizard, and you have a running blog. There is no database to provision, no wp-config.php database credentials dance, no migration if you want to move hosts [README].

The project was created by Danang Probo Sayekti and is maintained under a GPL-2.0 license [3]. As of this review it has 1,322 GitHub stars — a fraction of what WordPress or Ghost pull, but a healthy number for a focused single-author blogging tool. The most active community discussion appears to live on Bersosial, an Indonesian web developer forum, which has a dedicated HTMLy subforum with threads running from 2016 through at least late 2023 [1].

The official pitch is performance: the homepage claims the platform handles 20,000+ posts and hundreds of tags on 512MB RAM, using “a unique algorithm to find or list any content based on date, type, category, tag, or author” [homepage][README]. Whether that algorithm is meaningfully faster than a well-tuned WordPress install with a caching plugin is hard to verify independently — no published benchmarks exist in the sources we found — but the claim is consistent: flat-file CMS removes the database query bottleneck at the cost of filesystem complexity [3].

What you are actually getting is a PHP blogging engine with a web-based admin panel, a Markdown editor, multi-author support, scheduled publishing, and a theme system built on traditional PHP templates. It is not headless, not API-first, not a static site generator. It renders pages on the server, caches aggressively, and serves them fast [README][3].

---

Why people choose it

The English-language review record for HTMLy is thin. We found no dedicated English reviews from major tech publications, no Trustpilot page, no G2 profile. The primary user testimony we found is from the Indonesian developer community [1][4], which limits the breadth of synthesis we can honestly offer.

That said, the pattern in what does exist is consistent.

The no-database argument is real. MasRud.com [4], a personal blog that switched between WordPress and HTMLy multiple times before settling on HTMLy in December 2016, describes it as “a flat-file CMS without a database that is powerful and resource-efficient.” The appeal is concrete: shared hosting plans frequently impose per-database limits, database-driven CMSes require separate backup strategies for files and SQL, and MySQL corruption has ended more than a few blogs. Removing the database removes a category of failure.

It beats WordPress on simplicity of migration. A Bersosial thread [1] asks directly whether HTMLy is “portable” — whether you can move it by moving the folder. The answer is yes. That is not true of a standard WordPress installation, where the database stores absolute URLs and requires search-replace tooling to migrate cleanly.

LinuxLinks [3] notes the built-in feature set is unusually complete for a project of this size: built-in full-text search, JSON API, OPML, RSS importer, online backup, 2FA, sitemap.xml, SEO-friendly URLs, and per-post navigation. Most flat-file CMSes in the same category (Pico, Grav, GetSimple) leave several of these to plugins or extensions. HTMLy bakes them in.

The core trade-off surfaces repeatedly: HTMLy is for people who want to publish and not maintain an infrastructure stack. If you know your post volume, don’t need an e-commerce layer, and would rather FTP files than manage database backups, HTMLy makes sense. If you need a plugin ecosystem, WooCommerce, or a large community of theme developers, it doesn’t.

---

Features

Based on the README, LinuxLinks [3], and the official website:

Content management:

• Markdown editor with live preview and image upload [3][README]
• Category and tag support with multiple tags per post [3][README]
• Static pages (About, Contact, etc.) alongside blog posts [3]
• Post drafts and scheduled publishing [3][README]
• Custom fields per post [README]
• Multi-author support with user roles (admin sees and can edit all users’ posts) [3][README]
• i18n / multilingual UI [README]

Discovery and SEO:

• SEO-friendly URLs [3]
• Meta canonical, description, and rich snippets per post [3]
• Sitemap.xml generation [3]
• Built-in full-text search [3][README]
• Related posts [3]
• Archive pages by year, year-month, year-month-day [3]
• Tag cloud widget [3]

Technical:

• JSON API [3]
• RSS 2.0 feed and importer [3]
• OPML export [3]
• File-based caching [3][README]
• One-click auto-update from the admin panel [README]
• Online backup [3][README]
• Two-factor authentication (2FA) [README]
• Menu editor [README]

Theming:

• Traditional PHP template engine (HTML mixed with PHP) [3]
• Responsive design on the default theme [3]
• Third-party themes available at htmly.com/theme/ [README]

Integrations (optional):

• Disqus comments [3]
• Facebook comments [3]
• Google Analytics [3]

What it does not have:

• No plugin/extension marketplace — if a feature isn’t in core, it isn’t available [README]
• No headless/API-first mode beyond the basic JSON API [3]
• No built-in e-commerce [README]
• No block editor — Markdown only [README]

---

Pricing: SaaS vs self-hosted math

HTMLy has no SaaS tier and no commercial license. The software is free under GPL-2.0, full stop [3][README]. Pricing math here is about what you save versus the hosted blogging alternatives.

Hosted blogging alternatives:

• WordPress.com: Free tier exists but is ad-supported. Personal plan ~$4/month. Creator ~$25/month. Business (which allows plugins) ~$45/month.
• Ghost Pro: Starter ~$9/month for 500 members. Creator ~$25/month. Team ~$50/month.
• Medium: Free to read but you lose SEO — Medium owns the domain.
• Substack: Free until you monetize (then 10% cut), but fully platform-locked.

HTMLy self-hosted:

• Software: $0 (GPL-2.0) [README]
• Shared hosting: $2–5/month (it requires PHP 7.2+ and works on shared hosting [README])
• VPS: $4–6/month on Hetzner or Contabo if you prefer
• Domain: $10–15/year regardless of what you pick

The honest math for a solo blogger:

If you would otherwise pay Ghost Pro $25/month for its clean writing experience, HTMLy self-hosted on a $5 shared hosting plan saves you $240/year. If you were on WordPress.com Business at $45/month to get plugin support, you save $480/year.

The catch is that “free” carries a real cost in maintenance. Flat-file CMSes are simpler to operate than WordPress (no database migrations, no plugin updates), but auto-update still requires you to click a button periodically, and security issues still require action. HTMLy’s security model — no database means no SQL injection surface — reduces one category of risk, but PHP vulnerabilities still apply [3][README].

---

Deployment reality check

HTMLy is genuinely easy to deploy by self-hosted CMS standards.

What the README says:

1. Download the latest release zip from GitHub
2. Upload and extract to your web server
3. Visit /install.php
4. Follow the wizard
5. Delete install.php when done [README]

There is also an online installer (online-installer.php) that downloads HTMLy directly to your server without a local download step [README].

What you actually need:

• Any web server (Apache, Nginx, LiteSpeed, IIS) [3]
• PHP 7.2 or greater [README]
• PHP extensions: Mbstring, XML, INTL, GD, ZIP [README]
• Write permissions on the cache/ and content/ directories [README]
• No database setup required

What shared hosting gives you for free: Most cPanel-based shared hosts have all of these installed by default. HTMLy is one of the few CMSes you can realistically deploy without any command-line access. MasRud.com [4] describes deploying it on Dewaweb shared hosting with no technical friction beyond uploading files.

Where things can go wrong:

• The PHP INTL extension is not always enabled by default on cheap shared hosts — you may need to toggle it in cPanel or contact support.
• File permissions on cache/ and content/ must be writable; some shared hosts restrict this and require manual chmoding.
• URL rewriting (.htaccess on Apache) must be enabled for clean URLs. Most hosts support this, but some minimal configurations don’t.
• There is no official Docker image in the main repository. Containerized deployment is possible but you set it up yourself.
• The Bersosial community [1] documents AMP integration and HTTPS migration as non-trivial customizations — they’re doable but require template editing.

Realistic time estimate: A technical user can deploy HTMLy in 15–30 minutes on a fresh shared hosting account. A non-technical blogger following a guide: 1–2 hours including domain pointing and theme setup. This is faster than a self-hosted WordPress install because there is no database provisioning step.

---

Pros and cons

Pros

• No database. No MySQL to provision, backup separately, or corrupt. Content is portable — migrate by moving a folder [README][4]. The failure surface for “blog goes down at 2am” is smaller.
• Runs on shared hosting. 512MB RAM is enough for 20K+ posts per the official claim [homepage]. You don’t need a VPS to self-host this [README].
• Unusually complete built-in feature set. 2FA, JSON API, RSS importer, online backup, full-text search, scheduled posts, custom fields, sitemap.xml — most flat-file alternatives charge you a plugin for several of these [3].
• Genuinely fast installation. Online installer or zip upload, no database wizard, no environment variables [README].
• Portable content. All your posts are files. No vendor lock-in, no export step. Switch hosts by zipping the directory [4][README].
• Multi-author with roles. Admins can edit all users’ posts; authors manage their own. More than most flat-file CMSes offer [3][README].
• GPL-2.0 license. You can self-host, fork, modify — no commercial restrictions on personal use [3][README].

Cons

• No plugin marketplace. Every feature is in core or doesn’t exist. If you need something HTMLy doesn’t do, you either edit PHP templates or choose a different CMS [README][3].
• Tiny English-language community. No Stack Overflow presence to speak of, minimal Reddit discussion, primary community is on an Indonesian forum [1]. Getting help in English is difficult.
• 1,322 GitHub stars. Small enough that long-term maintenance continuity is uncertain. The last notable updates documented in the Bersosial community [1] are from late 2023, and the project appears to be maintained by a single primary developer.
• PHP template theming. Building custom themes requires writing PHP, not a block editor or visual builder. The theme library at htmly.com/theme/ is small [README].
• No headless mode. The JSON API exists but isn’t documented as a first-class feature. If you want to use HTMLy as a backend for a React frontend, you’re on your own [3].
• No official Docker image. Containerized deployment requires manual setup [README].
• AMP and advanced SEO customization require template editing. Not a great sign for non-technical users who want to compete on search [1].

---

Who should use this / who shouldn’t

Use HTMLy if:

• You run a personal blog or small editorial site and want a flat-file CMS with less overhead than WordPress.
• You’re on shared hosting and don’t want to use up a database slot or deal with MySQL backup.
• You want content portability as a hard requirement — your posts need to be files you can move without export/import gymnastics.
• You’re comfortable with PHP basics and willing to edit templates when you need customization.
• You want built-in 2FA, scheduled posts, full-text search, and sitemap.xml without installing plugins.

Skip it (use WordPress instead) if:

• You need a plugin ecosystem. WooCommerce, SEO plugins, page builders — none of this exists for HTMLy [README].
• You want a large community to answer questions. WordPress has millions of users; HTMLy has a forum in Indonesian [1].
• Your team is larger than 2–3 people. The user roles are basic and there’s no workflow beyond admin/author [3][README].

Skip it (use Ghost instead) if:

• You want a clean, modern writing experience with a block editor and built-in newsletter/membership tools.
• You’re willing to pay $9–25/month for a managed, maintained platform with an active product team.
• You need email newsletters without building a third-party integration.

Skip it (use Grav instead) if:

• You want a flat-file CMS with a real plugin/theme marketplace and active English-language community.
• You need a headless CMS with a documented REST API.
• You want a block-based admin panel without writing PHP.

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

• You want the absolute fastest possible page delivery and are comfortable with a build step.
• You don’t need a web-based admin panel and prefer editing files in a text editor.

---

Alternatives worth considering

• WordPress (self-hosted) — The obvious comparison. Vastly more plugins, themes, and community. Requires MySQL. Performance requires caching plugins. The elephant in every room.
• Ghost — Modern, beautiful, built for publishing. Self-hostable (Node.js, requires a VPS). Managed tier starts at $9/month. Newsletter and membership built in. Much larger community than HTMLy.
• Grav — Flat-file CMS like HTMLy but with a real plugin and theme marketplace, better documentation, and a more active English-language community. More complex to configure, but more extensible [3].
• Pico — Minimalist flat-file CMS. Even simpler than HTMLy but has almost no built-in features — you add everything via plugins [3].
• GetSimple CMS — Older flat-file option in the same category. XML-based storage, smaller community. LinuxLinks lists it alongside HTMLy [3].
• WriteFreely — Clean, minimal, federated blogging (ActivityPub). Better fit if you want Mastodon/Fediverse integration and a distraction-free writing environment.
• Hugo — Static site generator. Not a CMS in the traditional sense, but if you’re comfortable with Markdown files and a build step, it generates faster sites with no server-side PHP [3 adjacent].

For a non-technical founder the realistic shortlist is HTMLy vs Grav vs Ghost self-hosted. Pick HTMLy if you want the simplest possible flat-file setup and database-free portability. Pick Grav if you need extensibility. Pick Ghost if you want a polished product with active development and are willing to pay for managed hosting or run Node.js.

---

Bottom line

HTMLy is a competent, underrated flat-file CMS that solves a real problem: deploying a blog without touching a database. It runs on shared hosting from 2006, installs in 20 minutes, and ships with more built-in features than most tools twice its complexity. The GPL-2.0 license means you own what you run.

The honest limitations are also real. The community is small and largely Indonesian-language [1]. There is no plugin ecosystem, so what the core doesn’t do, you don’t get. At 1,322 GitHub stars it occupies a precarious niche — useful enough that a dedicated community exists, not popular enough that its long-term maintenance is assured.

If you’re a blogger who has spent an afternoon battling a WordPress database migration or a $25 Ghost Pro bill that feels wrong for a personal site, HTMLy deserves a look. If you need a platform to build a business on, or if you want a community that can answer your questions in English at 11pm, the alternatives above are safer bets.

---

Sources

1. HTMLy | Bersosial.com — Dedicated HTMLy subforum with threads from 2016–2023, primarily Indonesian-language community discussion. https://forum.bersosial.com/tags/htmly/
2. HTMLy Demo — “What is Blog?” — Official demo instance showing default content and HTMLy rendering capabilities. https://demo.htmly.com/post/what-is-blog
3. LinuxLinks — “HTMLy: open source databaseless blogging platform” — Feature survey including requirements, key features list, and comparison to flat-file alternatives. https://www.linuxlinks.com/htmly-open-source-databaseless-blogging-platform/
4. MasRud.com — “Pengalaman menggunakan hosting Dewaweb” — Personal account of switching between WordPress and HTMLy, settling on HTMLy for resource efficiency. https://masrud.com/review-dewaweb/
5. rshweb.com — “What are the Best Blogging Scripts or Apps?” — Blogging platform roundup listing HTMLy among alternatives to WordPress and Ghost. https://rshweb.com/blog-best-blogging-platform

Primary sources:

• GitHub repository and README: https://github.com/danpros/htmly (1,322 stars, GPL-2.0 license)
• Official website: https://www.htmly.com/
• Documentation: https://docs.htmly.com/
• Theme library: https://www.htmly.com/theme/
• Live demo: https://demo.htmly.com/