Forum software is the application that runs threaded, searchable discussion for a community. The best choice depends on the team’s hosting skills and the community’s size: Discourse suits larger, moderated groups, Flarum suits lightweight PHP hosting, and classic boards suit simple needs.
This guide supports the wider topic of the self-hosted community, where owning the platform is part of the point.
What forum software actually does
A forum keeps conversations in public or semi-public threads that remain findable months later. That is the main difference from chat tools, where messages scroll away, and from feeds, where recency decides what people see. A good forum gives each topic a permanent address, a searchable archive, user accounts with permissions, and moderation tools to keep discussion healthy.
Most packages cover the same core: categories, topics and replies, notifications by email, user profiles, trust or role systems, and an admin panel. The differences lie in how they are built, how much they ask of the server, how easy they are to extend, and what the licence allows. Those differences matter more than any feature checklist.
Two modern approaches: Discourse and Flarum
Two open-source projects show the range of design choices. Discourse describes itself as a platform for community discussion, and its repository lists a GPL-2.0 licence. Its back end is a Rails application, the main data store is PostgreSQL, and Redis handles caching and transient data, according to the Discourse repository. That stack is capable but demanding: several services must run together and stay updated.
Flarum takes the opposite path. Its project page calls it simple forum software and says it is built with PHP, so it is quick and easy to deploy. It carries an MIT licence and exposes a powerful Extension API, according to the Flarum repository. The interface runs on Mithril, a small JavaScript framework, which keeps the front end light.
| Factor | Discourse | Flarum |
|---|---|---|
| Licence | GPL-2.0 | MIT |
| Language and stack | Ruby on Rails, PostgreSQL, Redis | PHP, Mithril front end |
| Typical install | Docker-based installer on a VPS | PHP hosting with a web server |
| Extension model | Plugins and themes | Extension API |
Table details come from the Discourse repository and the Flarum repository.
The licence difference is practical. GPL-2.0 is a copyleft licence, so distributed modifications must stay under the same terms. MIT is permissive and places few conditions on reuse. For a community that only runs the software, either works. For a team that plans to build and distribute custom add-ons, the choice deserves a closer read.
Hosting requirements and the cost of running it
Self-hosting a forum means taking on updates, backups, email delivery and security patches. Discourse documents its installer plainly. Its cloud install guide lists a minimum of 1 GB of RAM with swap and a recommended 2 GB or more, along with a 64-bit Linux system. The installer installs Docker and git if they are missing, then launches an interactive setup wizard.
Those figures are a floor, not a plan. A forum with an active archive, image uploads and background jobs grows past a minimal server, so budget for headroom and watch memory use during the first busy weeks. PHP-based boards such as Flarum are usually lighter, but they still need a database, a web server and regular updates, so the maintenance burden never fully disappears.
The same guide notes that the installer works on any cloud provider with Docker support and on a local server. It also points out that the project sells official hosting plans for people who would rather skip server management. Barnraiser.org has no connection to any such plan and does not recommend one; the point is simply that hosted and self-managed routes both exist for most large projects.
Reliable email is the item new administrators most often underestimate. Forums depend on notification and password-reset messages, and a poorly configured sending domain sends them to spam. Plan for that before launch, not after members complain.
Matching software to community size
Size and moderation load should drive the decision more than fashion. A few rules of thumb hold up across projects:
- Small hobby or club group: a lightweight package on ordinary PHP hosting keeps costs and maintenance low. Flarum fits here, as do older boards.
- Growing public community: built-in trust levels, spam controls and strong search matter more. Discourse is designed around these needs, at the price of a heavier server.
- Private team or customer group: look at permission models, single sign-on options and export tools before anything else.
- Technical project: code formatting, tagging and email reply support tend to matter most.
Anyone weighing a simpler, older design can read about the traditional bulletin board model, which still serves many communities well. Those who want profiles, follows and feeds rather than topic threads may be better served by a self-hosted social network instead.
Moderation, spam and community health
Software cannot replace human moderators, but it can make their work lighter. Look for tools that let trusted members flag problems, hold new users’ first posts for review, rate-limit new accounts and merge or split topics. A forum that is hard to moderate tends to drift toward either spam or silence.
Search and navigation matter just as much. If members cannot find an earlier answer, they ask the same question again, and the archive loses its value. Test search with real queries from the community’s own subject area before deciding.
Finally, consider accessibility and mobile behaviour. Most readers arrive on a phone, often from a search engine, and land on a single thread rather than the front page. Open a sample thread on a small screen and check that it loads quickly, reads cleanly and offers an obvious way to reply or join.
A practical checklist before committing
- Test a demo or a throwaway install. Post, reply, search and moderate as a member would.
- Check the upgrade path. Find out how updates are applied and how often breaking changes appear.
- Look at the extension ecosystem. Confirm that the add-ons you need exist and are still maintained.
- Verify export and import. Leaving later should not mean losing the archive.
- Plan backups. Database and uploads both need regular, tested copies.
- Read the licence. Confirm it fits how you will modify and share the code.
Migration is costly because links, accounts and years of posts are involved. A week of testing at the start is cheap by comparison.
Frequently asked questions
Is forum software free?
Many leading projects are open source, including Discourse under GPL-2.0 and Flarum under MIT. The software is free to download, but hosting, email delivery, backups and administrator time are real costs.
Which forum software is easiest to install?
Flarum is built with PHP, which suits common web hosting. Discourse offers a single-command installer for a fresh Ubuntu or Debian server, which is simple if a VPS and Docker are acceptable.
How much server power does a forum need?
For Discourse, the project’s install guide lists 1 GB of RAM with swap as a minimum and 2 GB or more as recommended. Lighter PHP-based boards usually need less.
Can a forum be moved to different software later?
Usually yes, through importers or export tools, but it takes planning. Check export options before choosing, since URLs, accounts and formatting rarely transfer perfectly.
