Flarum logo

Flarum

A free, fast, self-hosted forum you own outright, if you can run a server

Flarum is free and open source forum software released under the MIT licence, built on PHP and Laravel by the Flarum Foundation, that you install on your own hosting to run a fast, mobile friendly, publicly indexable discussion community with tags, threaded style replies, real time notifications, moderation and flagging tools, and hundreds of community built extensions; there is no subscription, no member limit, and no transaction fee of any kind, and the only costs are hosting, occasional premium extensions, and your own time.

Visit website

Overview

Flarum is the answer for anyone who looked at $89 a month for a community platform and thought, correctly, that a forum is not a hard piece of software. It is free under the MIT licence, it runs on ordinary PHP hosting, it has no member limit, it takes no cut of anything you sell, and every discussion in it is a public web page that Google can index. Where every hosted platform in this category rents you a community, Flarum gives you one and hands you the keys.

The project began publicly in December 2014 as a merger of two older forum codebases, FluxBB and esoTalk, when Toby Zerner open sourced the work and cancelled a Kickstarter campaign to make it free for everyone. It took a famously long time to stabilize: version 1.0 arrived in May 2021, after both original founders had moved on, with Daniel Klabbers leading the project since. Development is now stewarded by the Flarum Foundation, and version 2.0 has been in release candidate through 2026, already running in production on Flarum's own forum at discuss.flarum.org.

What you get is a deliberately small core with a large extension ecosystem. The core handles discussions, tags, mentions, likes, real time notifications, email digests, group permissions, flagging and moderation, markdown, and a genuinely good mobile experience that feels closer to a modern app than to a 2005 message board. Everything else, from single sign on to custom fields to gamification to private messaging, is a community built extension, most of them free, some of them sold through the unofficial Extiverse marketplace.

The honest limitation is that Flarum is a forum and nothing else. There is no course builder, no events product, no checkout, no memberships, no mobile app in the app stores, and no transaction fee to model because there is no transaction anything. If you want to charge for access you bolt on an extension or a payment tool, and if you want courses you run a separate platform. It is also software you have to operate: PHP 7.3 or later, MySQL or MariaDB, command line access, and someone who will apply updates.

Best for

Technically comfortable operators running a free, public, discussion first community who want the content indexed by Google, complete ownership of the data and the domain, no per member cost at any scale, and no platform taking a percentage of anything.

Not the right fit for

  • Anyone who cannot or will not administer a server. Flarum requires PHP, MySQL, command line access, and someone to apply updates and backups; there is no official managed hosting to fall back on.
  • Businesses selling courses or memberships. There is no checkout, no membership product, no entitlement system, and no course builder, so monetization is an extension project rather than a feature.
  • Communities that need real time chat, voice, or events. Flarum is asynchronous discussion only; the live layer that Discord gives away free simply does not exist here.
  • Buyers who need a mobile app in the app stores. Flarum is a very good mobile web experience and nothing more, with no native or branded app at any price.
  • Organizations that need vendor accountability, an SLA, or a compliance contract. There is no vendor: the Flarum Foundation stewards a volunteer project and owes you nothing.

How it works

  1. 1

    You obtain hosting. Flarum needs Apache with mod_rewrite or Nginx, PHP 7.3 or newer with the curl, dom, fileinfo, gd, json, mbstring, openssl, pdo_mysql, tokenizer, and zip extensions, and MySQL 5.6 or newer or MariaDB 10.0.5 or newer. A $5 to $20 a month virtual server or ordinary shared hosting is enough for most communities.

  2. 2

    You install it, either by uploading a prepackaged archive built for your PHP version or by running composer create-project from the command line. Command line access is required either way for maintenance tasks, so this is not a one click product for someone who has never used a terminal.

  3. 3

    You structure the community with tags rather than rigid categories. Tags can be primary or secondary, nested one level, restricted to specific user groups, and applied in combination, which is a more flexible model than the fixed board hierarchy older forum software imposes.

  4. 4

    You set permissions per group. Groups control who can see a tag, start a discussion, reply, edit, flag, or moderate, which is how a public forum with a private members area is built without a second product.

  5. 5

    You extend it. Extensions are installed with Composer and enabled from the admin panel, covering single sign on, custom user fields, private messaging, polls, gamification, spam control, search improvements, and integrations. The unofficial Extiverse marketplace lists both free and premium extensions.

  6. 6

    You keep it running. Updates are a Composer command, backups are your responsibility, and the security of the server is yours. This is the cost that does not appear on any price list and the reason most small businesses eventually pay someone else instead.

Feature breakdown

24 features in 4 modules

Discussion and structure

A small, fast, modern core that does the forum job properly.
Tag based organization
Discussions are organized by tags rather than fixed boards, with primary and secondary tags, one level of nesting, and per group visibility, which is more flexible than the rigid category trees of older forum software.
Infinite scrolling discussions
Long threads load continuously with a scrubber for navigating position, rather than paginating into twenty numbered pages.
Real time notifications
Live in browser notifications for mentions, replies, and likes, plus configurable email digests for members who are not watching.
Mentions and likes
User and post mentions with notification, and reactions, which are core rather than extensions.
Markdown and rich text editing
Markdown by default with a WYSIWYG option available, so both technical and non technical members are served.
Full text search
Search across discussions and posts in the core, with extensions available for more advanced indexing on large forums.
Genuinely good mobile web
The interface was designed mobile first and feels closer to an app than to a desktop forum shrunk down, which is unusual in open source forum software.

Moderation and safety

Solid fundamentals in the core, spam handling largely delegated to extensions.
Flagging
Members flag posts for moderator attention, with a moderation queue in the admin interface.
Group based permissions
Every capability, from viewing a tag to editing another user's post, is a permission attached to a group, which is the mechanism behind private areas, paid tiers, and staff access.
Post editing, locking, and deletion
Standard moderator actions with an edit history, so members can see when a post was changed.
User suspension and banning
Available through core and widely used extensions, with configurable durations.
Spam control via extensions
The core does not ship an automated spam classifier. Community extensions add Akismet, Stop Forum Spam, captcha, and approval queues, which work well but must be chosen and maintained by you.
Email confirmation and registration control
Require confirmed email addresses, close registration, or require approval, which are the basic defences against drive by signups.

Ownership and openness

The reason to choose Flarum over anything hosted.
MIT licence
Genuinely permissive. You can modify it, brand it, deploy it commercially, and never pay anyone, with no copyleft obligation.
Public content indexed by search engines
Every public discussion is a normal web page on your own domain with its own URL, so a forum that accumulates good answers becomes an organic acquisition channel. This is the single largest advantage over Discord, Slack, Circle, and every gated platform in this category.
Your own domain and complete white labelling
There is no vendor branding anywhere unless you put it there, and the community lives entirely on your domain with your CSS.
Direct database access
Your data is in your MySQL database. Export, migrate, analyse, or back it up however you like, which no hosted platform in this category permits.
No member limits and no fees
No per seat cost, no member cap, no transaction fee, and no revenue share at any scale. The cost curve is hosting alone.
REST API and extension framework
A documented API and a Laravel based extension framework, so custom functionality is a normal PHP project rather than a vendor feature request.

Extensions and ecosystem

A small core plus hundreds of community extensions, with the maintenance risk that implies.
Hundreds of community extensions
Private messaging, polls, custom user fields, gamification, badges, SSO, analytics, and integrations, most free and installed with Composer.
Extiverse marketplace
An unofficial marketplace listing free and premium extensions, which is where most commercial Flarum functionality is bought.
Themes and CSS customization
A theme system plus direct CSS control from the admin panel, so visual customization does not require a build pipeline.
Single sign on extensions
SSO against your own application or an identity provider is available through extensions rather than the core, which is how paid access is usually implemented.
Extension maintenance risk
Extensions are volunteer maintained. A major version upgrade can leave an extension you depend on unmaintained, which is the most common real world Flarum failure and the reason 2.0 has taken so long to stabilize.

Use cases

4 documented

Software product with a support community

Users ask the same questions repeatedly, and the answers currently live in a Discord where Google cannot see them and nobody can find them a month later.

A Flarum forum on community.yourproduct.com makes every answer a permanent indexed web page that deflects support tickets from people who never join, at the cost of a small server and some maintenance.

Hobby or interest community with no revenue

Thousands of enthusiasts, no business model, and no appetite for $89 a month or for handing the archive to a company that could change its terms.

Flarum runs the whole thing for the cost of hosting, with no member cap and no fees, and the community owns its own history permanently.

Operator escaping a hosted platform's fees

A community paying a percentage of member revenue plus a monthly subscription wants the content, the domain, and the money to be entirely its own.

Flarum removes the platform fee completely, and membership billing moves to Stripe or Memberful with an SSO extension controlling group membership on the forum.

Technical team that wants to modify the software

The community needs a workflow the vendor will not build, and every hosted platform's answer is a feature request into a queue.

The MIT licence and the Laravel based extension framework mean the team writes the extension themselves and ships it the same week, with direct database access for anything the API does not cover.

Pricing

from $0 for the software, plus roughly $5 to $20 per month for hosting

Free and open source under the MIT licence. There is no subscription, no per member fee, and no transaction fee. Costs are hosting, optional premium extensions, and your own maintenance time.

PlanPriceIncludes
Self hosted$0
for the software, forever
  • MIT licence with no restrictions
  • Unlimited members, discussions, and moderators
  • No transaction fee on anything you sell
  • Full source access and direct database access
  • Hundreds of free community extensions

You supply the server, the updates, the backups, and the security. That is the entire cost model.

Typical real world cost$5 to $20
per month for hosting
  • Shared PHP hosting or a small virtual server
  • MySQL 5.6 or newer, or MariaDB 10.0.5 or newer
  • PHP 7.3 or newer with standard extensions
  • Command line access required for maintenance
  • Scales to a larger server as traffic grows

A community of tens of thousands of members can run comfortably on hosting that costs less than one Circle subscription.

Premium extensionsVaries, typically one off or annual
per extension
  • Sold mainly through the unofficial Extiverse marketplace
  • Cover SSO, advanced search, gamification, and integrations
  • Optional; most functionality is available free

Billing notes

  • Reviewed August 2026. Flarum is MIT licensed and there is no commercial edition, no hosted tier, and no vendor to buy from.
  • There is no transaction fee on paid memberships because there is no payment layer at all. At $5,000 a month in member revenue you pay Flarum nothing, and at $50,000 a month you pay Flarum nothing. Your only cost is whatever billing tool you bolt on, typically Stripe at roughly 2.9 percent plus 30 cents or Memberful at $49 plus 4.9 percent.
  • That makes Flarum by a wide margin the cheapest option in this category at any revenue. The same $50,000 a month costs roughly $1,600 on Circle, $1,900 on Podia, and $6,750 or more on Patreon.
  • There are no member seat limits and no admin seat limits at any point, which is the structural difference from Slack, Thinkific, Teachable, and every other product here with a seat model.
  • The real cost is labour. Budget a few hours for installation and configuration, then ongoing time for updates, backups, spam tuning, and the occasional extension that breaks on a major version. If that time costs you more than $89 a month, Circle is cheaper.
  • Third party managed Flarum hosting exists from small providers, and community run free hosting has existed at various times, but there is no official managed option, which is the single biggest practical barrier for a non technical buyer.

Value assessment: On pure capability per dollar, nothing else in this category is close, because the denominator is hosting. Unlimited members, unlimited moderators, permanent history, complete data ownership, your own domain, full white labelling, source access, and public content that Google indexes, for the price of a small virtual server, is a proposition no hosted vendor can match on price. The cost is entirely in operations and scope. You are the sysadmin, the security patcher, and the person who works out why an extension broke on upgrade, and you get a forum rather than a platform: no courses, no events, no checkout, no chat, no app. The right way to evaluate it is to price your own time. A technically confident operator running a free public community should almost certainly use Flarum and spend the saved subscription on hosting and coffee. A non technical founder who wants to sell a membership should not, because everything Flarum does not do is exactly the part they need.

Strengths & limitations

Strengths

  • Free under the MIT licence with no member limits, no seat costs, no transaction fees, and no revenue share at any scale.
  • Public discussions are ordinary indexed web pages on your own domain, which turns an accumulating archive into an organic acquisition channel that no gated platform in this category can offer.
  • Complete ownership. Source access, direct database access, your own domain, and full white labelling with no vendor branding anywhere.
  • A genuinely modern and fast interface with real time notifications, infinite scrolling discussions, and a mobile web experience that does not feel like an old message board.
  • Tag based organization is more flexible than fixed category hierarchies, with per group visibility that makes private areas straightforward.
  • Hundreds of community extensions plus a Laravel based extension framework, so anything missing can be built rather than requested.
  • Modest hosting requirements. A community of tens of thousands can run on hosting costing less than one month of any hosted platform here.

Limitations

  • You have to run it. PHP, MySQL, Composer, command line access, updates, backups, and security are all yours, and there is no official managed hosting to escape to.
  • No payment layer of any kind: no checkout, no memberships, no entitlements, so charging for access is an integration project.
  • No courses, no events, no live streaming, no chat, and no voice, so everything beyond asynchronous discussion needs another product.
  • No mobile app in the app stores, branded or otherwise; members use the mobile web.
  • The core ships no automated spam classifier, so spam handling depends on choosing and maintaining the right extensions, where Discourse handles this out of the box.
  • Extension maintenance risk is real. Extensions are volunteer built, and a major version upgrade can strand one you depend on, which is part of why 2.0 spent so long in release candidate.
  • No vendor, no SLA, no support contract, and no compliance paperwork, which rules it out for buyers who need somebody accountable.
  • Both original founders left the project years ago, and development has historically been slow: version 1.0 took until 2021, and 2.0 has been in release candidate through 2026.

Head-to-head comparisons

5 alternatives

Flarum vs Discourse

from $0 (self-hosted, or the free managed plan), then $100 per month for Pro managed hosting

The direct comparison and the one that matters. Discourse is the more capable forum by a distance, with the best spam and moderation tooling in this category, better search, trust levels, and a mature hosted option with a vendor behind it. Flarum is lighter, faster, easier on cheap hosting, simpler to theme, and MIT licensed rather than GPL. Choose Discourse if you want the strongest forum and are willing to pay for hosting or run a heavier Ruby stack; choose Flarum if you want something small you can host anywhere for a few dollars and modify freely.

Full Flarum vs Discourse comparison

Flarum vs Discord

from $0

Opposite trade offs and often run together. Discord is free, real time, has voice and events, and is invisible to Google, with no data ownership and no export. Flarum is free, asynchronous, fully indexed, and entirely yours, with no chat or live layer at all. A mature community frequently runs both: Discord for conversation, Flarum for the answers that should be findable in three years. If you can only have one and search traffic matters, Flarum.

Full Flarum vs Discord comparison

Flarum vs Circle

from $89 per month (Professional)

Circle costs $89 a month plus 2 percent of member revenue and gives you a branded community with courses, events, live streaming, a member directory, mobile apps, and a checkout, all managed for you. Flarum gives you the forum for the price of hosting and none of the rest. At $50,000 a month in member revenue Circle costs roughly $1,600 a month and Flarum costs roughly $15. The question is whether the things Circle does that Flarum cannot are worth $19,000 a year to you, and for a business selling memberships they often are.

Full Flarum vs Circle comparison

Flarum vs Memberful

from $49 per month plus a 4.9 percent transaction fee

The natural pairing for anyone who wants to charge for a Flarum community. Memberful at $49 a month plus 4.9 percent handles the checkout, the recurring billing, and the entitlement, though its native integrations target Discord, Discourse, and WordPress rather than Flarum, so you would need an SSO extension in between. Stripe plus a custom extension is often simpler and cheaper for a technical operator.

Full Flarum vs Memberful comparison

Flarum vs Bettermode

from $399 per month billed annually ($4,788 per year); $499 per month billed monthly

Bettermode is the hosted, mid market, fully managed version of the same idea: a branded, indexable community on your own domain with a real permission model and no server for you to run. It costs several hundred dollars a month. Flarum does the discussion part for the price of hosting and expects you to be the operations team. If your company has budget but no engineer to spare, Bettermode; if it has an engineer but no budget, Flarum.

Full Flarum vs Bettermode comparison

Implementation & onboarding

Setup time
An hour for a technical operator using the prepackaged archive, a day to configure tags, groups, permissions, extensions, and theming properly. Considerably longer if you have never deployed a PHP application.
Learning curve
Low for members, who face a clean and obvious interface. Moderate for administrators, mainly because the permission model is group based and every capability is configured separately. High for anyone who has not administered a server before, since Composer and command line access are unavoidable.
Onboarding
There is no onboarding, because there is no vendor. Documentation at docs.flarum.org is good, and the official forum at discuss.flarum.org is the support channel. Third party developers and small agencies offer paid installation and customization.
Migration notes
Importers exist from older forum software including phpBB, vBulletin, and XenForo, with varying quality and community maintenance. Moving out is the easiest in this category by a wide margin because your data is in your own MySQL database: you can export it, transform it, or move it wherever you like without asking anyone's permission or losing anything. That single fact is the strongest argument for self hosting over any product on this page.

Platform, API & security

Platforms
Self hosted web applicationResponsive mobile webNo native or branded mobile apps
API
A documented REST API plus a Laravel based extension framework with frontend and backend extenders, so custom functionality is written as a normal PHP package.
Compliance
Whatever you implement yourself; there is no vendor certification of any kind
Data residency
Entirely your choice, because you choose the server. This is one of the few products in this category where EU data residency is trivially satisfied.
SSO
Available through community extensions rather than the core, including OAuth providers and custom SSO against your own application.
Security notes
Built on Laravel with regular security releases from the Flarum Foundation, but patching, server hardening, backups, and TLS are entirely your responsibility. There is no managed security posture, no penetration test report, and no SOC 2.

Support & resources

Channels
Community support onlyPaid help available from independent developers and small agencies
Documentation
Thorough documentation at docs.flarum.org covering installation, requirements, extension development, and the 2.0 upgrade path.
Community
An active official forum at discuss.flarum.org, which itself runs on Flarum 2.0 in production, plus GitHub and the unofficial Extiverse marketplace.

Company

Founded
2014
Headquarters
Distributed; stewarded by the Flarum Foundation
Ownership
Open source, MIT licensed, stewarded by the Flarum Foundation
Founders
Toby Zerner, Franz Liedke
Employees
None; a volunteer project with a foundation and a small group of maintainers
Funding
No venture funding. Development began after Toby Zerner cancelled a Kickstarter campaign in December 2014 in order to open source the project. The Flarum Foundation now stewards the work, supported by donations and sponsorship.

Timeline

  1. 2014Development begins publicly in December as a merger of FluxBB and esoTalk, when Toby Zerner cancels a Kickstarter campaign and open sources the project under the MIT licence.
  2. 2019Toby Zerner announces his departure from the project in July, leaving Franz Liedke and Daniel Klabbers to lead it.
  3. 2021Franz Liedke also steps back in February, leaving Daniel Klabbers leading the project; the first stable release, version 1.0, ships in May after years in beta.
  4. 2022The Flarum Foundation is established to steward the project, and the extension ecosystem matures around the Extiverse marketplace.
  5. 2025Flarum 2.0 enters release candidate, with a modernized extension API and a substantial internal rewrite.
  6. 2026Release candidate 3 of 2.0 ships and runs in production on discuss.flarum.org and other forums while the stable release is finalized.

Integrations

  • Stripe and other payment tools via extensions
  • OAuth providers including Google, GitHub, and Discord via extensions
  • Akismet and Stop Forum Spam via extensions
  • Mailgun, SES, and SMTP for outbound email
  • Webhooks and Zapier via extensions
  • REST API for custom integrations
  • Composer based extension installation from Packagist and Extiverse

Frequently asked questions

10 questions

What is Flarum and what job does it do here?

Flarum is free, open source, self hosted forum software under the MIT licence. In this category it is squarely a discussion community: asynchronous threaded conversation organized by tags, publicly indexable, on your own domain. It is not a course platform, not a membership business, and not a chat tool, and it does not pretend to be any of them.

How much does Flarum cost?

The software is free forever with no member limits and no feature gating. Realistically you will spend $5 to $20 a month on hosting, occasionally something on a premium extension from the Extiverse marketplace, and a few hours a month of your own time on updates, backups, and spam tuning. There is no vendor to pay.

What transaction fee applies to paid memberships?

None, because Flarum has no payment layer. At $5,000 a month in member revenue you pay Flarum nothing, and at $50,000 a month you pay Flarum nothing. The only cost is whatever billing tool you attach, typically Stripe at roughly 2.9 percent plus 30 cents. For comparison, the same $50,000 a month costs about $1,600 on Circle, $1,900 on Podia, and $6,750 or more on Patreon, so Flarum is the cheapest option here at any scale by an enormous margin.

Are there member or admin seat limits?

No, none, at any point. There is no per seat pricing, no member cap, and no limit on moderators or administrators. The only constraint is what your server can handle, and Flarum is light enough that a community of tens of thousands runs comfortably on modest hosting.

Do I get a custom domain and how white label is it?

Completely. Flarum runs on your own domain with your own CSS and theme, and there is no vendor branding anywhere unless you add it. The MIT licence imposes no attribution requirement in the interface. This is the most white label option in this category and it is free.

Is Flarum content indexed by search engines?

Yes, and this is the main reason to choose it over Discord, Slack, Circle, or any gated platform. Every public discussion is a normal web page with its own URL on your domain, so an accumulating archive of good answers becomes an organic acquisition channel that brings in people who have never heard of your community. Gated platforms cannot do this at all, and Discord is so far from doing it that a whole category of third party tools exists to mirror its threads onto the web.

How good are the moderation and spam tools?

The moderation fundamentals are solid in the core: flagging with a moderation queue, group based permissions on every capability, post editing with history, locking, deletion, and suspension. Spam is the gap. The core ships no automated classifier, so you install extensions for Akismet, Stop Forum Spam, captcha, or an approval queue. They work well, but choosing and maintaining them is your job, where Discourse handles spam out of the box and is genuinely better at it.

Are courses and events available?

No. Flarum is a forum. There is no course builder, no lessons, no progress tracking, no certificates, no scheduled events, no RSVPs, and no live streaming. If you need those, run them on a separate platform and link from the forum, or choose Circle, Thinkific, or Kajabi instead.

Can I get my data out?

Better than anywhere else on this page. Your data is in your own MySQL database on your own server, so exporting, transforming, analysing, or migrating it requires nobody's permission and loses nothing. Importers exist from phpBB, vBulletin, and XenForo for moving in. Every hosted platform in this category treats the community archive as effectively non portable; Flarum simply hands it to you.

Should I just run a free Discord or Slack instead?

It depends entirely on whether you want to be found. Discord is free, better at real time conversation, has voice and events, and takes minutes to set up, but nothing in it is indexed and you cannot export the archive. Slack is worse still, hiding everything past 90 days on the free plan. Flarum keeps every discussion forever as an indexed page on your own domain, at the cost of running a server. Many communities honestly need both: Discord for talking and Flarum for the answers that should still be findable in three years. If you have no technical capacity at all, run the Discord and revisit this when the lost search traffic starts to bother you.

Editorial verdict

Flarum is the right answer for a technically capable operator running a free, public, discussion first community, and the wrong answer for almost anyone selling something. What it offers is unmatched at the price: unlimited members, permanent history, complete data ownership, your own domain with no vendor branding, source access under the MIT licence, and every public discussion indexed by Google as a page you own, all for the cost of a small server. At $50,000 a month in member revenue it costs you nothing where Circle would take about $1,600 and Patreon more than $6,750. The costs are operational and scoped. You are the sysadmin, the patcher, and the person who fixes the extension that broke on upgrade, and you get a forum and nothing else: no checkout, no courses, no events, no chat, no app, and no automated spam filter without an extension. If you want the strongest forum with a vendor behind it, Discourse is better and worth paying for. If you want the lightest one you can host anywhere for five dollars and modify however you like, Flarum is excellent and has been quietly underrated for a decade.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.