Flarum
Platform · this deep dive is built from the official pages of the platform itself and of the tools that support it.
Overview
Flarum is not a platform where you can open an account — it is forum software you install on your own server. The difference is fundamental: there is no one else's audience here, no one else's moderation and no one else's rules about advertising. You write the rules, because the forum is yours.
The developers describe the product this way: "Beautiful, fast, and free — Flarum is the open-source forum software your community has been waiting for", with three badges alongside it: "Free Forever", "MIT Licensed", "Open Source". The licence is confirmed in the repository: MIT License, described as "Simple forum software for building great communities".
For a community professional, Flarum is interesting in exactly one scenario: when you need your own brand or product forum rather than a presence on someone else's. Everything this guide normally calls "growth on a platform" turns here into administering your own.
Who's here
Flarum has no audience — it has users of the software. The developers give no public numbers on installations: the home page carries the general phrase "Trusted by communities around the world" with no measurement, and the features section promises "Hundreds of community-built extensions" — again with no exact figure.
The only verifiable number about the project's size is the repository counters: 6.7K stars and 882 forks on flarum/framework. That is a GitHub measurement, not a Flarum claim, and it speaks to developer attention, not to the number of working forums.
The project's language is English. The developers' own forum requires writing in English unless a special multilingual tag is used. The documentation on the pages we checked promises no Russian interface; localisations exist as extensions.
Getting started
What the server needs
The developers list the requirements outright: Apache with mod_rewrite enabled or Nginx; PHP 7.3+ with the curl, dom, fileinfo, gd, json, mbstring, openssl, pdo_mysql, tokenizer and zip extensions; MySQL 5.6+/8.0.23+ or MariaDB 10.0.5+; SSH access and Composer if you plan to install extensions from the command line.
Two ways to install
The first is a Composer command: composer create-project flarum/flarum:^1.8.0.. The second is unpacking an archive, if you have no SSH. On the date we checked, the archive table listed version 1.8.17 for PHP 8.1 through 8.5, in variants with and without a public directory.
Note a discrepancy that is visible at a glance: the home page announces release candidate 2.0.0-rc.3 and calls it "production-ready for early adopters", while the installation guide installs the 1.8 branch and notes that "Only the latest Flarum 1.x version is detailed here". In other words, by default you get a different version from the one the home page writes about.
If you have no server of your own
The documentation mentions a third-party free host and immediately disclaims responsibility: Free Flarum — "a free community service not affiliated with the Flarum team". The service itself promises forum creation "in under 5 minutes", SSL, daily backups, automatic updates and a set of extensions out of the box and explains its model: "This service is paid for by donations". There are no limits on volume or user count on the page we checked.
What you can publish
Content restrictions are set by the forum owner, not by the software. In the base package the developers name groups and permissions, built-in moderation and reports, tags and custom CSS, an editor in two modes — Markdown and WYSIWYG — plus browser notifications and email digests.
Limits on file size, message length and number of attachments depend on PHP settings and the extensions installed: specific ceilings are determined by your own server configuration.
The only place where the project itself sets content rules is the developers' forum. There, the following are prohibited: insults and incitement to hatred; messages whose purpose is harassment, impersonation or defamation; spam, phishing and vandalism of the site; discussion of piracy; attempts to expose someone else's personal data; obscene content. The code of conduct we checked has no separate clause on advertising and self-promotion — the spam ban is worded in general terms.
How to grow
By the nature of the product, Flarum has no algorithmic feed to bring you an audience: this is your site, and you drive traffic to it yourself. Among built-in retention mechanisms the developers name browser notifications, email digests and real-time extensions over WebSockets.
There are no built-in traffic statistics in the description of core features. Nor does the software have an ad account — you place advertising on your own forum yourself.
Path to monetization
Flarum pays forum owners nothing: this is software, not a platform with shared revenue. The product is free — the home page states outright "Free Forever" and "MIT Licensed", and the MIT licence is confirmed in the flarum/framework repository.
Money enters the ecosystem from the other side: some extensions are paid. The documentation mentions the option of adding extra Composer repositories, including "Extiverse's premium offerings", that is, a paid extension catalogue.
You can earn from a forum the ordinary ways a site owner does: subscriptions, advertising, paid sections. The software describes none of them as a built-in feature, so no specific thresholds or commissions exist here.
Tools and automation
Extensions
They install in two ways: through the built-in extension manager in the admin panel, where you enter a Composer package name, or with the command composer require COMPOSER_PACKAGE_NAME:* over SSH. After that, the admin panel offers enabling and disabling, settings, version information and removal.
The documentation gives an important security warning right there: "The extension manager allows an admin user to install any composer package. Only install the extension manager if you trust all of your forum admins with such permissions". The practical conclusion: admin rights on your forum are equivalent to the right to execute arbitrary code on the server.
To find extensions, you are pointed to the Extensions tag on the community forum and to the third-party Extiverse catalogue, which the documentation calls "unofficial".
REST API
Programmatic access exists and is documented. Authentication comes in two forms: API keys — "the primary way for scripts, tools and integrations to interact with Flarum" — created manually in the database, with a recommended token length of 40 alphanumeric characters, passed in the Authorization: Token YOUR_API_KEY_VALUE; userId=1 header; and short-lived access tokens for a specific user, issued by the /api/token endpoint against a login and password.
What you can do: GET /api/discussions — a paginated list of discussions, POST /api/discussions — creating a discussion with a title, body and tags, POST /api/users — creating a user. GET endpoints work without authentication for anything a guest can see; POST, PUT and DELETE require a key because of CSRF protection. The documentation warns honestly that "endpoint documentation is still in progress", so as of the date we checked there is no complete method reference.
No known scheduling service claims Flarum support — which is to be expected: every installation has its own address and its own key, so an integration is usually written for a specific forum through that same REST API.
Limits and rules
- Server. PHP 7.3+ with ten extensions, MySQL 5.6+/8.0.23+ or MariaDB 10.0.5+, Apache with mod_rewrite or Nginx.
- Versions. The default installation installs the 1.8 branch, while the home page announces 2.0.0-rc.3; archives are offered for version 1.8.17 and PHP 8.1–8.5.
- Administration security. The extension manager lets an administrator install any Composer package.
- API. Modifying requests require a key; the method documentation is unfinished.
- Developer community rules. Insults, spam, phishing, discussion of piracy and exposing other people's data are prohibited; a violation leads to content removal or account suspension, and you should complain through the Report function rather than argue.
- Law. The MIT licence — you are entitled to change the code and use it commercially; responsibility for the content of your forum is yours, and the licence gives no warranties.
Who it's for
It suits you if you need your own forum under company control: your domain, your data, your rules about advertising and self-promotion. It suits teams that have someone who can handle a server — installation, updates and backups are entirely on you.
It suits projects that value extensibility: there is a REST API, an extension manager, and open source under MIT.
It does not suit you if you are looking for a ready-made audience — there is none here at all. It does not suit you if you have no resource for administration: free software does not mean free operation. And it does not suit you if you need a predictable version roadmap: as of the date we checked, the home page and the installation guide point to different branches of the product.
Verified data
The checked data this deep dive rests on.
About the platform
the platform describes itself this way: «Free, open-source forum software built by the community. Beautiful, fast, and extensible — made for communities of all sizes.»
Self-description: this is the platform's claim about itself, not an independent assessment
source, checked 2026-07-28
Languages
the interface language of the home page: en
The language is taken from the markup attribute, the versions from hreflang
source, checked 2026-07-28
Catalogue section: all similar See also: catalogue index · scheduler comparison · find by situation · platform restrictions