Discourse vs Flarum vs NodeBB: Forum Software Compared

Discourse, Flarum and NodeBB are free, open source forum programs you can install on your own server, and each has a plugin or extension system. Discourse is the most complete out of the box and is also sold as a managed service. Flarum is the lightest to run on ordinary PHP hosting. NodeBB is the one built around real-time discussion on Node.js. The right pick depends on who will maintain it, how big the community will get and what you want to earn from it.

This comparison uses each project's own repository, documentation and pricing page, checked in October 2026. It ends with where forum software stops, because a community that wants votes ranking posts across many topic areas, a coin wallet, paid tiers and a branded app is usually asking for a different kind of product, such as a white-label community forum platform with those pieces built in.

What forum software is for

Forum software gives a community a place to hold long-running threaded discussion that people can find again. A question asked in March should still be answerable in October. That is the feature chat apps and social feeds do not give you, and it is why a forum still beats a group chat for support, hobby knowledge and product feedback.

Every forum program covers the same core:

• Categories or boards that organize topics.
• Topics with threaded or linear replies, and notifications when someone answers you.
• User accounts, groups and permissions per category.
• Moderation actions: edit, move, lock, delete, suspend.
• Search, so the archive is useful.
• An extension point for everything else.

The differences are in the stack you must run, how much moderation help comes built in, how the project makes money, and who maintains the plugins you will inevitably add. Those are the axes used below. For the moderation side of running any of them, see our guide to how to moderate an online community at scale.

The contenders at a glance

The table below uses statements from each project's own pages. Where a page did not state something, the cell says so instead of guessing.

A fourth name often appears in lists like this one: Vanilla. It is now Higher Logic Vanilla, a proprietary hosted product aimed at customer communities, with no public price on its page. It sits in a different category from the three above, which are free to self-host, so it is covered briefly after them.

Discourse

Discourse is the reference point for modern forum software. Its repository describes it as licensed under GPL-2.0, built on Ruby on Rails with an Ember front end, and requiring PostgreSQL and Redis. The project provides a Docker-based installer, and the repository lists current minimum versions of Ruby, PostgreSQL and Redis that you must keep up with when you self-host.

Its strongest point is moderation. The project's moderation guide describes a flag system that feeds a review queue, where staff approve, reject or ignore each item. It also describes trust levels, which promote active members automatically and unlock abilities such as editing, with staff able to promote people by hand. Whispers let moderators talk privately inside a public topic, and a staff-only category keeps team discussion out of sight. That is a worked-out answer to a problem every growing community meets: how do you give trusted members power without hand-granting it every time?

The project also lists real-time chat, themes and a plugin ecosystem that includes a data explorer for SQL queries. The plugin list on the hosted plans is a good sign of what is maintained, because the vendor keeps those working with each release.

The cost of Discourse is in the requirements. It is a Rails application with several services, designed to run in containers. A person who has never run Docker on a server will learn quickly or pay for hosting. That is a fair trade for the tooling you receive, and it is the reason the managed plans exist.

Flarum

Flarum describes itself as free, fast and beautiful forum software under the MIT license, written in PHP on a Laravel-based architecture with a Mithril front end. MIT is the most permissive of the three licenses: you can run it, change it and ship a modified version in a commercial product while keeping the notice.

The install guide for the 2.0 line asks for Apache or Nginx, PHP 8.3 or later with a listed set of extensions, and MySQL, MariaDB, SQLite or PostgreSQL. It also asks for SSH access for Composer and maintenance. There is a packaged archive for people who prefer not to use the command line for the first install. That makes Flarum the closest of the three to the classic "upload to a PHP host" experience, though the SSH requirement means cheap shared plans without a shell are not enough.

Flarum keeps its core small and puts features in extensions: the project site speaks of hundreds of community-built ones. That gives a clean base and puts the burden of choice on you. Every extension is a dependency you must check at each upgrade. The site also states that the 2.0 line is at release-candidate stage and that the community was voting on a stable release, so a new install today means choosing a version line with that in mind. The documentation notes that there are no official importers yet, only unofficial community ones for several older forum programs.

Flarum does not offer hosting. Its site presents the software as self-hosted with support through the documentation and a community forum. If you want a vendor to run it for you, you will need a third-party host or your own system administrator.

NodeBB

NodeBB is a Node.js forum built on WebSockets, so replies and notifications arrive live without a page refresh. Its repository lists the GPLv3 license, with commercial sublicenses available for environments the GPL does not suit. It runs on one of three databases: MongoDB, Redis or PostgreSQL, with Redis required if you cluster it. The repository lists Node.js 22 or later, and Nginx and Docker as optional.

The documentation lists a plugin framework, a full REST API, moderation tools with privileges, reputation and upvotes, and support for mobile and progressive web apps. The reputation and upvote system is the closest any of the three comes to the voting behavior of larger discussion sites, though it works inside forum categories instead of replacing them.

NodeBB Inc. sells hosting in four tiers, priced by page views and storage, and the NodeBB pricing page says every plan includes unlimited staff users, daily backups, SSL, custom plugins, custom domains and priority support. That custom plugin line matters if your community needs a feature that does not exist yet and you have a developer. If your team already writes JavaScript, NodeBB is the forum you can read and change without learning a new language.

Vanilla and the hosted-only route

Higher Logic Vanilla began as Vanilla Forums and was acquired by Higher Logic in 2021. Its page describes a cloud product for B2B and B2C customer communities: support, engagement and product feedback. It is proprietary, delivered as software as a service, and priced through a sales conversation. Choose it when the community is a company function with a budget and a vendor relationship. Do not choose it if you want to own the code or see a price before talking to anyone.

Hosting and upkeep

Software is free; running it is not. The costs show up as a server bill, a person to update it, a backup you have tested and time spent when a plugin breaks after an upgrade. Managed hosting turns those costs into a monthly fee. The two projects that sell hosting publish prices, listed here as seen on their own pricing pages as of October 2026. Check the pages before you decide, because plans change.

Flarum and Higher Logic Vanilla do not appear in the table because Flarum offers no hosting on its own site and Vanilla publishes no price.

Self-hosting upkeep deserves a plain list, because it is the cost people underestimate:

1. Updates. Core releases, security fixes, and the language runtime or database underneath. Discourse and NodeBB list minimum versions that move forward over time; Flarum 2.0 lists PHP 8.3 as a floor.
2. Plugin compatibility. Each plugin or extension is someone else's code. Before upgrading, check that every one you use supports the new version.
3. Backups. A backup you have never restored is a hope. Restore to a test server once a quarter.
4. Email. Notification and digest mail needs a sending service with a good reputation, or members never see replies.
5. Spam and abuse. A public forum is a target. Plan the moderation layer before launch.

Which one fits which situation

No one of these is best for every community. The table maps common situations to the option whose own documentation fits them best. Treat it as a first filter, then test the shortlist with a real installation and a copy of your own categories.

One licensing note, which is general information and not legal advice: GPL licenses ask you to offer source for versions you distribute, and the rules around modified versions you only run on a server differ by license. If you plan to modify and resell, read the license text with your lawyer. Our post on open-source clones and licenses walks through the same checks for a different product type.

Where forum software stops

Forum software is built for discussion and archive. Several things a community operator often wants are not part of that core, and none of the three projects describes them on their own pages as built-in features.

• A coin economy. A wallet, an append-only ledger of top-ups and spending, and awards that members give each other are payments features. In a forum they would be a plugin, a custom build or a separate service.
• Creator payouts. Paying members out of what the community earns needs identity checks, balances, payout rules and tax handling. Forums do not model that.
• Branded native apps. Responsive sites and progressive web apps are available. A native app under your name in the app stores, with push notifications, is a separate project, and it brings the store's user-generated-content rules with it. Apple's guideline 1.2 asks for content filtering, a report mechanism, user blocking and published contact details, and Google Play's user-generated content policy asks for terms acceptance plus in-app reporting and blocking.
• Many communities under one roof. Categories inside one forum are not the same as many independent communities, each with its own rules, roles and moderators. A forum can approximate it with category permissions, but the model of a member creating a new community is a different design.
• Ranking by votes across the whole site. NodeBB lists reputation and upvotes, and Discourse has trust levels, but a front page that ranks posts from many communities by member votes is a product decision, not a forum setting.

None of this is a criticism. A support forum should not carry a wallet. The point is to name the gap before you spend a month customizing software toward a shape it was not designed for. For the money side, our guide to how to monetize an online community compares ads and memberships.

When to look past forums

Look past forum software when three or more of these are true:

• Members should be able to start their own communities with their own rules and moderators.
• Posts should be ranked by member votes, with comment threads that nest deeply.
• You want to earn from members directly: subscriptions, a coin wallet, awards.
• You need a branded Android app, and probably iOS later.
• You want the full source code, with no per-seat fee and no revenue share.

Our community platform covers that shape: six post types, threaded comments with votes, communities with public, restricted or private visibility, a four-tier role model inside each community, a moderation queue with removal reasons, bans with expiry and appeals, premium subscriptions, a coin wallet and awards on one ledger, and a branded Android app. The full list is on the Reddit clone features page. We also set up a native iOS app for your build, and items such as paying members out of award income are tailored work we deliver alongside the platform. If you are weighing a forum against a ready-made community platform with source code, the same framework applies as in our post on Facebook Groups versus your own community platform: ownership, effort and what you earn.

A fair caution runs the other way. A ready-made platform is more than you need if your community is a few hundred people who ask and answer questions. In that case Discourse, Flarum or NodeBB will serve you well, and you should not buy more product than the problem requires.

A checklist for choosing

1. Write down who will maintain the server in month twelve. If the answer is nobody, shortlist only hosted plans.
2. Estimate page views and storage for year one and compare them with the plan limits on the pricing pages.
3. List the five plugins or extensions you cannot live without. Check when each was last updated and which software version it supports.
4. Decide what moderation you need on launch day: report button, review queue, new-member limits, bans, appeals. Check each against the project's moderation documentation.
5. Decide whether members will pay. If yes, find out how the project handles it, and whether it meets your payment provider's rules.
6. Read the license once, with the question "what happens if I change the code and run it for the public?"
7. Install the top two on a test server with a copy of your category structure and ask five real members to use it for a week.
8. Check the exit: can you export your content and your members if you leave?

If the checklist points to a forum, start with one of the three and keep the scope small. If it points past forums, read the Reddit clone development cost page for the published price and what it includes, and compare it with the engineering time the forum route would need. When you are ready to talk, the pricing page has the detail.