How to Host a Flarum Forum
Flarum is one of the lightest modern forum platforms you can run — but "light" doesn't mean "zero effort." This guide covers what a Flarum forum actually needs, how to set one up yourself, and what each route really costs in money and time. We host Flarum forums for a living, and we'll be upfront about when you don't need us.
What Flarum needs to run
Flarum is a PHP application backed by a MySQL-compatible database. The baseline:
- A current PHP 8 release with the usual extensions (mbstring, pdo_mysql, gd, and friends) — check the Flarum docs for the exact minimum your target release wants
- MySQL or MariaDB
- A web server — nginx or Apache, with URL rewriting configured
- Composer — Flarum and all its extensions install through it
- 512 MB–1 GB RAM is enough for a small community; active forums want more headroom, mostly for PHP workers and the database
That's a modest footprint — a $5–10/month VPS runs a small Flarum forum fine. Compare that to platforms that need multiple gigabytes just to boot (see our Flarum vs Discourse comparison).
The parts nobody mentions
Installing Flarum takes an afternoon. Operating it is the actual job, and it's where most self-hosted forums quietly degrade:
- Updates. Flarum core and every extension update through Composer. Extensions can conflict with each other or lag behind core releases — you'll learn to read dependency errors.
- Backups. A forum is its database plus uploaded files. If you don't have automatic, off-site, tested backups, you don't have backups — you have hope.
- Email deliverability. Forum signups and notifications live or die on email. Sending from your own VPS lands you in spam folders; you'll want a transactional email service and correctly configured SPF/DKIM.
- Performance under load. A traffic spike from one viral thread can take down a default PHP-FPM config. Queue workers, Redis caching, and realtime WebSockets each add another service to install and monitor.
- Security. PHP, your web server, your OS, and your database all need patching on their own schedules. Forums are a constant target for spam bots and credential-stuffing.
None of this is hard once. All of it is recurring.
Option 1: Self-host on a VPS
The right choice if you enjoy server administration, want full control, or are running a hobby forum where downtime costs nothing but pride.
The short version of the checklist:
- Provision a VPS (1 GB+ RAM), point your domain at it
- Install nginx, PHP-FPM, MariaDB, Composer
composer create-project flarum/flarum .in your web root- Walk through the web installer, configure HTTPS (Let's Encrypt)
- Set up cron for scheduled tasks, a queue worker if you add realtime
- Configure transactional email (SMTP service, SPF/DKIM records)
- Script daily database + uploads backups to somewhere off the server
- Subscribe to update notifications for Flarum core and your extensions
Real cost: $5–20/month in hosting, plus the honest number — a few hours a month of maintenance, and the on-call burden when it breaks at 2am. The forum doesn't care that you're on vacation.
Option 2: Managed Flarum hosting
The right choice if you want to run a community, not a server.
With our managed hosting, every plan gets the same stack we'd build for ourselves: automated daily off-site backups, managed email sending, Redis + WebSockets for realtime, the Extension Manager for one-click installs, uptime monitoring with incident reports, and a self-service panel with live resource usage. Setup is automated — a new forum is live in minutes, and migrations from existing forums are free.
Real cost: more per month than a bare VPS — that's the honest trade. What you're buying is the operations work above, done continuously, by people who only do Flarum.
Which should you pick?
| Self-host | Managed | |
|---|---|---|
| Monthly cost | Lower | Higher |
| Setup time | An afternoon (first time: longer) | Minutes |
| Ongoing time | Hours/month, spiky | ~Zero |
| Control | Total | High (panel + Extension Manager) |
| When it breaks | You, at 2am | Us, that's the job |
If you're technical and the forum is a hobby: self-host, genuinely. You'll learn a lot and Flarum is a pleasant app to run. If the forum matters — it's your product's community, your revenue depends on it, or your members expect it to just work — pay someone to carry the pager.
Either way: monitor it
Whichever route you choose, put uptime monitoring on your forum — ours is free for everyone, no hosting plan required, and includes the Flarum community rankings so you can see how your forum's activity stacks up.