Flarum

Open-source community software, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (MIT) forum software — think phpBB rebuilt for 2024, with a clean UI and a modern extension API [4][5].
• Who it’s for: Non-technical founders and community managers who want a self-hosted discussion board without paying Discourse $100/mo or wrestling with phpBB’s dated interface [2][5].
• Cost savings: Discourse’s managed hosting starts at $100/mo. Flarum self-hosted runs on a $5–10/mo VPS. Same result, 95% of the cost gone [1].
• Key strength: Cleanest UI in the self-hosted forum category. Fast, mobile-responsive out of the box, no theme hacking required [2][3][4].
• Key weakness: Still on a 2.0 beta cycle as of this review — the API is in flux, extension compatibility is uncertain, and the ecosystem is smaller than phpBB’s or Discourse’s. Not production-stable if you need guarantees [website].

---

What is Flarum

Flarum is discussion forum software you install on your own server. You get a discussion board with threads, replies, tags, user groups, notifications, and a moderation system. The UI is single-page, built on Mithril (a lightweight JavaScript framework), so it feels faster than most forum software from the same era [4][README].

The project was created by Toby Zerner and is described as “the combined successor of esoTalk and FluxBB” — two older forum projects [4]. It’s been around since roughly 2014, though the 1.0 stable release only landed years later. As of this writing it sits at 6,694 GitHub stars and is actively maintained, currently shipping the 2.0 beta cycle with an RC milestone on the near horizon [website][merged profile].

The pitch on the homepage — “Forums made simple. Beautiful, fast, and free” — is accurate on all three counts, with the caveat that “simple” refers to the end-user experience, not the installation [website][README].

What distinguishes Flarum from its older competitors isn’t a massive feature list. It’s restraint. phpBB ships 400 admin settings. Flarum ships the 40 you actually need, styled in a way that doesn’t make your users feel like they’ve landed in 2008 [2][4][5].

---

Why people choose it over Discourse, phpBB, and XenForo

The comparison that comes up most in third-party reviews isn’t “Flarum vs. Discourse” — it’s “Flarum vs. the category.” Forum software has a bad reputation for either being technically ancient (phpBB, SMF) or expensive and resource-heavy (Discourse, XenForo). Flarum sits in the gap.

Versus Discourse. Discourse is the category leader for modern self-hosted forums. It’s feature-rich, well-maintained, and backed by a strong company. But it has two problems: it requires Docker and meaningful server resources (2GB RAM minimum, 4GB recommended for real load), and Discourse’s managed hosting starts at $100/mo — the cheapest tier for a proper community [5]. Flarum runs on a standard shared hosting plan with PHP 7.2+ and MySQL, costs nothing to license, and a managed provider like Elestio deploys it for $14/mo if you don’t want to touch a server yourself [1]. The trade-off is features: Discourse has a built-in trust system, email digests, wiki pages, and an extensive plugin library that Flarum doesn’t match yet.

Versus phpBB and SMF. These are both free, battle-tested, and have massive extension catalogs. They also look like they were designed in 2006, because they were [3][5]. Flarum’s competitive advantage here is purely UI — modern, responsive, fast. If your community members have ever complained that your forum looks broken on mobile, that’s the argument for switching [2][4].

Versus XenForo. XenForo is arguably the best feature-for-feature forum software available, but it’s not free — licenses start at $160 and require annual renewal for updates. For founders watching their monthly burn, that’s a different conversation [5].

Versus NodeBB. NodeBB is the other “modern” option in the open-source space — also real-time, also extensible, but built on Node.js instead of PHP. Reviews peg them as roughly equivalent in target audience, with NodeBB having a slight edge in real-time features (WebSocket-native) and Flarum winning on setup simplicity and hosting compatibility [5].

The practical translation: Flarum is the forum software you install when you want something that looks and feels contemporary, costs nothing, and runs on a standard PHP host. It is not the forum software you install when you need every feature Discourse has.

---

Features

Based on the README, website, and third-party descriptions:

Core discussion engine:

• Threaded discussions with tags (category system) [README]
• Markdown support, with optional WYSIWYG editor via extension [website]
• Real-time browser notifications [website]
• Email digests and notifications [website]
• Full-text search [README]
• Discussion locking, pinning, hiding [README]
• User groups with per-tag permission overrides — including tag-restricted discussions where authors can manage their own posts (fixed in beta.7) [website]

Admin and moderation:

• Built-in moderation queue and flagging [website]
• Intuitive admin panel — multiple reviewers call this out as notably clean [2][3]
• Custom CSS that propagates site-wide without theme hacking [website]
• Internationalization — 34 language packs [4]

Extensions:

• Extension API described as “amazingly flexible” [README]
• Hundreds of community-built extensions available [website]
• Extensions cover: SSO integrations, social login, real-time WebSockets, richer text editors, custom fields, analytics, and more
• Extension compatibility is a live concern during the 2.0 beta cycle — extensions built for 1.x may not work on 2.x until updated [website]

What’s missing from core (requires extensions or workarounds):

• No built-in wiki pages (unlike Discourse)
• No trust levels / automated reputation system out of the box
• No native private messaging in core (available via extension)
• No official REST API documented for external integration [merged profile]

2.0 status note: The current 2.0 cycle is at beta.7 as of this review. The website explicitly states the API is still in flux and breaking changes between betas are expected. One more beta is planned before the RC cycle begins [website]. Running 2.0 in production is described as appropriate for “early adopters” — not a stability guarantee.

---

Pricing: SaaS vs self-hosted math

Flarum itself: Free. MIT licensed. No per-seat, per-member, or per-post fees [4][5].

Self-hosting cost:

• A $6/mo Hetzner or Contabo VPS handles a small-to-medium community without issue
• PHP shared hosting (as cheap as $3–5/mo) works if your host meets the requirements: PHP 7.2.9+, MySQL 5.6+ or MariaDB 10.0.5+, Apache with mod_rewrite or Nginx, and SSH access for Composer [4]
• Total annual cost: $36–$120/year

Managed Flarum (via Elestio):

• Starting at $14/mo, includes automated backups, SSL, updates, and monitoring [1]
• Annual cost: ~$168/year

Discourse managed cloud (comparison):

• Starter: $100/mo (2 staff, 100GB storage)
• Annual cost: $1,200/year

Concrete savings:

A community that would pay Discourse $100/mo saves $1,032/year by running Flarum on a $6 VPS, or $864/year by using Elestio’s managed Flarum. That math is straightforward. The question is whether the feature gap matters for your specific community — and for many communities running basic Q&A or support forums, it doesn’t.

Note: pricing data not available for phpBB (free, self-hosted only), SMF (free, self-hosted only), or XenForo ($160 initial + renewal).

---

Deployment reality check

The install path is Composer-based, which is the PHP ecosystem’s package manager. You SSH into your server, run a composer create-project command pointing at the Flarum skeleton repository, configure a web server block, and set up the database. It’s not Docker Compose, which means it works on shared hosting — a meaningful advantage over Discourse [4][README].

What you actually need:

• A PHP host (Apache with mod_rewrite, or Nginx) or a Linux VPS
• PHP 7.2.9+ with extensions: curl, dom, gd, json, mbstring, openssl, pdo_mysql, tokenizer, zip [4]
• MySQL 5.6+ or MariaDB 10.0.5+
• SSH access (required for Composer) [4]
• A domain name

What can go sideways:

• The 2.0 beta has “APIs in flux” — if you install extensions for 1.x and then upgrade, they will likely break [website]. This is a real operational risk for anyone building on top of the extension ecosystem right now.
• The extension catalog, while growing, is younger than phpBB’s or Discourse’s. Some features you’d expect from older forum software simply aren’t available yet [2][3].
• SSH access is required for installation, which rules out the cheapest shared hosting tiers [4]. You need a host that gives you command-line access.
• No official REST API documentation means integrating Flarum with external tools (CRMs, analytics, Zapier) is more DIY than it should be [merged profile].

Realistic time estimates:

• Technical user on a VPS: 30–60 minutes to a working install
• Non-technical founder following a guide: 2–4 hours including domain and email setup
• Using Elestio managed hosting: under 10 minutes, no server knowledge required [1]

---

Pros and Cons

Pros

• MIT licensed, genuinely free. No per-user fees, no per-post limits, no commercial license required. Fork it, modify it, embed it in your product [4][5].
• Best UI in the self-hosted forum category. Repeatedly called out across reviews — mobile-responsive, clean admin panel, fast page loads [2][3][4].
• PHP-based, runs anywhere. Unlike Discourse (Docker required, 2GB RAM minimum), Flarum runs on standard shared hosting with PHP. Lower barrier to self-hosting [4].
• Tag-based permission system is genuinely flexible for organizing discussions by topic or access level [website][README].
• Active development. The 2.0 cycle is moving — beta.7 shipped with performance improvements and bug fixes, with RC on the near-term roadmap [website].
• 34 language packs. Good i18n support if your community isn’t English-only [4].
• Managed option exists. Elestio offers fully managed Flarum at $14/mo for those who don’t want to touch a server [1].

Cons

• 2.0 is beta, API is unstable. If you’re building on top of Flarum’s extension API right now, expect breaking changes before stable [website]. Extension developers are explicitly warned about this.
• Smaller extension catalog than phpBB, Discourse, or XenForo. Core gaps (private messaging, advanced search, REST API) require community extensions that may lag behind version updates [2][3][5].
• No native REST API. External integrations are harder than they should be [merged profile].
• Composer-required installation. Requires SSH access. Rules out the cheapest hosting tiers and raises the bar for non-technical users compared to WordPress-style point-and-click installs [4].
• No SSO in core. Available via extensions, but not built in — additional complexity for teams with existing auth systems [merged profile].
• Smaller company backing than Discourse. Flarum is maintained by the Flarum Foundation and community contributors; it doesn’t have Discourse’s commercial backing. This matters for long-term survival bets [README][5].
• No built-in trust/reputation system. Discourse’s trust levels (which auto-promote engaged members) have no Flarum equivalent in core.

---

Who should use this / who shouldn’t

Use Flarum if:

• You want a discussion board that looks contemporary without paying Discourse’s hosting bills.
• Your community is small-to-medium and your forum needs are straightforward: threads, tags, moderation, notifications.
• You’re comfortable with SSH and Composer, or you’ll use Elestio’s managed option.
• You’re running a hobby or indie community where a beta-cycle platform is an acceptable risk.
• You want MIT licensing with no commercial restrictions.

Skip it (use Discourse) if:

• You need a battle-tested, stable platform for a business-critical community.
• You need wiki-style documentation pages, a trust/reputation system, or deep email integration.
• You have a developer team and want a well-documented REST API for integrations.
• Downtime or extension breakage from a version upgrade is unacceptable.

Skip it (use phpBB or SMF) if:

• You need a massive extension catalog and are willing to accept the dated UI.
• Your hosting situation is shared PHP hosting with no Composer access.
• You want software that’s been in production stability for 15+ years.

Skip it (use XenForo) if:

• You’re running a large, high-traffic community where professional support and a polished feature set justify the license cost.
• Your community culture expects features like advanced user reputation, trophy systems, and paid memberships built in.

---

Alternatives worth considering

• Discourse — the obvious comparison. More features, more stable, more expensive to host managed, heavier resource requirements for self-hosting [5].
• phpBB — free, battle-tested, runs on ancient PHP hosts, massive extension library, looks like 2008 [5].
• NodeBB — also modern, also extensible, WebSocket-native for real-time updates, Node.js instead of PHP [5].
• XenForo — best overall feature set in the category, paid license, not open source [5].
• Simple Machines Forum (SMF) — free, feature-rich by default, well-established community, dated UI [3].
• bbPress — only consider this if you’re already on WordPress and want forum functionality without leaving that ecosystem [2].

For a non-technical founder who wants a self-hosted community without paying Discourse prices, the realistic shortlist is Flarum vs. NodeBB. Pick Flarum if you want PHP-based hosting and the cleaner admin experience. Pick NodeBB if you want real-time WebSocket updates and a more mature plugin ecosystem.

---

Bottom line

Flarum is the right answer to a specific question: can I have a modern-looking, self-hosted discussion board that doesn’t cost $100/month and doesn’t look like it was built during the Bush administration? The answer is yes, with caveats. The UI genuinely earns its reputation — it’s the cleanest in the self-hosted category. The MIT license is real. The PHP-based install is easier to run on commodity hosting than Discourse’s Docker setup. But you’re accepting a 2.0 beta platform where extension compatibility is a live concern, where the REST API is underdeveloped, and where the ecosystem depth of Discourse or phpBB doesn’t exist yet. For a hobby community, an indie project, or an early-stage startup running a support forum, the trade-offs are fine. For a business whose community is a core product — wait for 2.0 stable or use Discourse.

If the server setup is the blocker, Elestio’s managed Flarum at $14/mo removes that friction entirely. And if you want someone to handle the full deployment and leave you with a working forum to run — that’s exactly what upready.dev does for clients.

---

Sources

1. Elestio — “Managed Flarum as a Service”. https://elest.io/open-source/flarum
2. AppMus — “Flarum vs bbPress Comparison (2026)”. https://appmus.com/vs/flarum-vs-bbpress
3. AppMus — “Flarum vs Simple Machines Forum Comparison (2026)”. https://appmus.com/vs/flarum-vs-simple-machines-forum
4. LinuxLinks — “Flarum - simple discussion platform for your website”. https://www.linuxlinks.com/flarum-simple-discussion-platform/
5. SaaSHub — “Flarum Alternatives & Competitors”. https://www.saashub.com/flarum-alternatives

Primary sources:

• GitHub repository and README: https://github.com/flarum/framework (6,694 stars, MIT license)
• Official website: https://flarum.org
• Flarum blog / changelog: https://flarum.org (beta.7 release notes)