Flarum vs Discourse — an honest 2026 comparison

Discourse is the default when someone says "I need a managed forum". Flarum is the leaner option that doesn't get talked about as much. Both are actively maintained in 2026, both have happy communities running on them — but they're built for very different shapes of group. This is the side-by-side I wish I'd had before picking.

I run a managed-Flarum service (BrynForum), so I'm biased. The trade-off is that I've also spent more time than is healthy looking at where each piece of software actually fits. The honest answer is: it depends on what you're building. Below is the version that doesn't pretend otherwise.

The short version

If you have a few hundred members or fewer and your monthly budget is sub-£50, Flarum is almost always the right answer. If you have an active enterprise community with thousands of daily posters and a serious budget, Discourse is almost always the right answer. The interesting question is what happens in the middle — which is where most groups actually live.

Where they came from

Discourse launched in 2013. It was built by Jeff Atwood, Robin Ward, and Sam Saffron — the team that came out of Stack Overflow. The brief was to replace the older phpBB / vBulletin pattern with something built around modern web norms: real-time updates, single-page navigation, mobile-first, opinionated moderation tooling. The ambition was to be the forum software for the next twenty years of the internet, and it's a very respectable run at that goal.

Flarum grew out of esoTalk (a clean, lightweight forum project from the late 2000s) and FluxBB. The brief was different: a small, fast, extensible core that anyone could self-host on modest PHP hosting, with extensions as the way to add anything specialised. It hit stable in 2019 after years of public development. Where Discourse aimed for ambition, Flarum aimed for restraint.

That difference in starting point still shows in 2026.

Features — Discourse wins

There's no point pretending Flarum has feature parity. It doesn't. Here's where Discourse is clearly ahead:

• Trust levels and badges. Discourse has a built-in gamification system that grants users posting rights, moderation power, and visual recognition based on participation. Flarum can do this via extensions, but it isn't the core experience.
• Built-in chat. Discourse Chat is a separate threaded-chat surface alongside topics. It isn't a bolt-on; it's first-party. Flarum doesn't ship with chat.
• Onebox previews. Paste a YouTube URL, a tweet, or a GitHub PR link into a Discourse reply and you get a rich preview. Flarum has the s9e/mediaembed extension which covers most of this, but the polish is Discourse's.
• Mobile push notifications. Out of the box on Discourse. Available on Flarum via extension, slightly less polished.
• Enterprise SSO. SAML, OIDC, LDAP, Salesforce integration — Discourse ships with the lot. Flarum has SSO extensions but the enterprise-grade options are sparser.
• Anti-spam. Akismet integration is built in. Flarum has good extensions (fof/anti-spam, Akismet plugins), but configuration is on you.
• Default search. Discourse's default search is fast and good. Flarum's is basic — most operators add Algolia or a Sphinx/Elastic extension once the discussion count grows.

If your community is large and active and you need any of these out of the box, Discourse will save you a lot of glue work.

Resource economics — Flarum wins, by a lot

This is the difference that decides what you can actually afford to run.

A Discourse install runs a Ruby on Rails app server, Sidekiq for background jobs, Postgres, Redis, and Nginx. The official recommendation is 2 GB of RAM minimum, and most production installs are happier at 4 GB. The single-page-app frontend is JS-heavy; it ships a lot of UI to the browser on first load.

A Flarum install runs PHP-FPM, Nginx, and MariaDB. That's it. A bare install with no traffic sits comfortably under 100 MB. A typical small community under normal load lives in the 250–500 MB range. The frontend is server-rendered HTML with a small JS overlay for the interactive bits.

In practice that means:

• A €4.50/month Hetzner CX11 (2 GB) hosts one Discourse install with some breathing room. The same box happily hosts 10–20 Flarum instances.
• A 4 GB VM that runs one Discourse comfortably runs 25–30 Flarum communities side by side.

Why such a gap? Discourse holds a lot of state in long-lived Ruby workers — that's the price of the SPA + websocket model. Flarum is request-per-page; PHP-FPM workers spin up briefly and release. None of this is a knock on Discourse. The choices are deliberate. They make sense for a 100,000-member SaaS community. They don't make sense for a 60-person hobby group.

Pricing — what it actually costs

The headline numbers, with the caveats spelt out.

Self-hosted Discourse, monthly

• Hetzner CX21 (4 GB): around €5.20
• TLS via Let's Encrypt: free
• Transactional mail: $0–15 (Postmark, Resend, etc.)
• Off-site backups: a few pounds via restic to B2 or R2
• Your sysadmin time: 30–60 minutes a week for updates, plus the occasional fire-drill

Realistic monthly cost: £8–20, plus the time you don't get paid for.

Managed Discourse

• The lowest paid tier of the official service has historically started around $100/month and goes up sharply from there.
• Business and enterprise tiers run into the hundreds.

Self-hosted Flarum, monthly

• Hetzner CX11 (2 GB): around €4.50
• Same TLS / mail / backups story as above
• Your sysadmin time: 15–30 minutes a week, mostly composer updates

Realistic monthly cost: £5–12.

Managed Flarum (BrynForum)

• Small (up to 100 members): £10/month
• Medium (up to 1,000 members): £40/month
• Unlimited: £90/month

Each tier includes TLS, daily off-site backups, the standard extensions pre-installed, and email support from the person running the box.

The price floor matters. There's no managed-Discourse tier under £80–100/month, and there isn't going to be one — when each instance needs 2 GB of RAM, the unit economics don't bend. Flarum's lighter resource profile is what makes a £10 managed tier possible, and that opens up the whole "small communities deserve good forum hosting" segment.

UX and philosophy

Discourse looks like a conversation. Long topics scroll infinitely, replies are inline, the design heavily nudges towards continuous threading. Power users love it. New users sometimes find it disorienting if they're coming from older boards or Facebook groups.

Flarum looks like a forum. Discussions are threaded; pagination is traditional; tags organise content. The mental model is close to what someone migrating from a Facebook group or a phpBB board already has.

Neither is objectively better. It's a question of what your community recognises as "home". For a long-running niche group with members of mixed ages, Flarum's familiarity tends to be a feature. For a fast-moving developer community with Slack/Discord-adjacent expectations, Discourse's flow probably feels more natural.

Extensions and themes

Discourse has a larger plugin ecosystem with strong enterprise integrations: LDAP, SAML, Salesforce, Stripe, Slack relays, Zendesk bridges. Weaker for the small-community niceties that don't translate to enterprise demand.

Flarum's ecosystem is smaller but the well-maintained extensions are very well maintained — best-answer, polls, tags, gamification, mentions, embeds, anti-spam, custom user fields. The official directory and Extiverse cover most of what a small forum will reach for.

Themes are a draw. Discourse has more themes, but customising them goes deeper into Ember.js + handlebars. Flarum themes are simpler — there's less abstraction between you and the HTML, so a non-engineer can usually tweak the look without a build pipeline.

Hosting your data

Both can be self-hosted anywhere. The managed-comparison answer:

• Discourse.org hosts on AWS US-East by default. Other regions are available on Business and Enterprise tiers, with notice.
• BrynForum hosts on Hetzner Falkenstein, Germany. Everything we run is in the EU.

If your members are mostly EU and "where does my data live" is a sensitive question for your community, the difference is worth weighing. UK GDPR + EU GDPR alignment in 2026 means EU-resident hosting removes a whole class of paperwork.

When to choose which

Choose Discourse if

• You have or expect 1,000+ active members and engagement keeps growing.
• You need built-in chat, badges, and trust levels (not via plugins).
• You're a SaaS with enterprise customers asking for SAML/SSO and procurement-friendly compliance.
• You can comfortably spend £100+/month on managed hosting, or you have a sysadmin who actually wants to look after a Discourse instance.

Choose Flarum if

• A small or medium community — clubs, hobby groups, niche fan groups, indie SaaS support, schools.
• You want low monthly cost without giving up real features.
• You prefer server-rendered pages, traditional forum feel, low JS load.
• You want EU-resident data and a small, responsive operator on the other end of the email.
• You're already paying for cheap shared/VPS hosting and want forum software that fits.

There's an honest middle ground where either would work. If you're sitting at 200–500 members and growing slowly, it's mostly a question of which feels right to your community — and which monthly bill you'd rather pay.