What Is Flarum and What Should You Know Before Using It?
Flarum is a next-generation, open-source forum platform for running online discussions. It is a reasonable choice if you want a self-hosted community forum with a modern interface and an extension ecosystem, and you are comfortable installing and maintaining PHP-based software. If you need a fully managed, zero-maintenance service, or you are not prepared to track release candidates and extension compatibility, Flarum will require more hands-on work than a hosted alternative.
What Flarum actually is
Flarum is forum software: you install it on a server, and it provides the discussion structure — categories, topics, posts, users, and moderation tools. Its own community describes it as "the next-generation forum software that makes online discussion fun," which signals where it positions itself: the discussion experience and interface come first, rather than a legacy admin-and-thread model.
The practical implication is that Flarum is a platform you deploy and extend, not a service you sign up for. That shapes everything below — releases, extensions, and support all assume you are running your own instance.
How it differs from traditional forum software
The distinction that matters most when choosing is not a feature checklist but where the effort goes.
| Dimension | Flarum | Traditional forum software (e.g. phpBB-style) |
|---|---|---|
| Design priority | Modern, discussion-first interface | Long-established feature sets, often denser UI |
| Extension model | Extensions are central to adding functionality | Functionality often built in or added via mods |
| Release cadence | Active line of releases, including release candidates | Typically slower, stability-oriented releases |
| Compatibility burden | Extensions must match your Flarum version | Varies by mod and version |
The trade-off is consistent: Flarum gives you a cleaner starting point and a strong extension culture, but you take on version-compatibility management. Traditional software often asks less of you in that respect because more is bundled.
Current release status and compatibility
The official community's discussion list shows Flarum's release activity directly, and it is worth reading before you commit to a version:
- Flarum 2.0.0-rc.8 — a release candidate, with an accompanying community vote on whether it is ready to become 2.0 GA (general availability).
- Flarum 1.8.20 — a maintenance release on the 1.x line.
- "Friends of Flarum — 2.0 Compatibility Progress" — a thread tracking how extensions are keeping up with 2.0.
Two conclusions follow. First, if you need maximum stability today, the 1.x maintenance line is the safer bet, because 2.0 is still in release-candidate status. Second, before installing any extension, check whether it supports your chosen version — the existence of a dedicated compatibility-progress thread tells you this is a real, ongoing concern rather than a hypothetical one.
Getting started: installation and extensions
Flarum is self-hosted software, so getting started means deploying it on your own server rather than creating an account. The community's own framing — "get support using and extending Flarum" — confirms both activities are expected of users.
A workable sequence:
- Pick a version. Choose the 1.x maintenance line for stability, or a 2.0 release candidate if you want the newer line and accept pre-GA risk.
- Install Flarum on a server that meets its requirements. (Consult the official installation documentation for the exact environment and commands — do not rely on secondhand instructions.)
- Verify the base forum works before adding anything: create a category, post a topic, reply to it, and confirm the discussion renders as expected.
- Add extensions one at a time, checking each against your Flarum version. The community maintains an Official Extension Discovery (Beta) listing, which is the natural starting point for finding extensions.
- Re-test after each addition, so that if something breaks you know which extension caused it.
The most common sticking point is step 4: installing an extension built for a different Flarum version. The compatibility thread exists precisely because this happens often.
Where to get support
The official Flarum Community at discuss.flarum.org is the support venue, and its "All Discussions" area is where releases, extension announcements, and help threads live. It is also where you will find the extension-discovery listing and the compatibility tracking.
One practical note from the site itself: it states it is best viewed in a modern browser with JavaScript enabled, and it can show a loading error that a hard refresh may fix. If the community appears broken, try a hard refresh before assuming the site is down.
Beyond browsing, the community is where you would post your own question — but check the existing release and compatibility threads first, since version questions are recurring there.
What to decide before you start
- Choose Flarum if you want a self-hosted, extensible forum with a modern interface and you are willing to manage versions and extension compatibility yourself.
- Wait on 2.0 if you need production stability — the release-candidate status and the active compatibility-tracking thread both point to 1.x for now.
- Look elsewhere if you want a hosted service with no server maintenance, or if you would rather not track which extensions match which release.
The single most useful habit with Flarum is checking version compatibility before installing anything — releases, extensions, and support discussions all revolve around that one variable.