Misago

Last reviewed Sep 13, 2026 · 800 words

Pick Misago if you want a forum whose code you can read and modify in Python, and pick Discourse if you want the forum with the largest community, the most plugins and the safest long-term bet. That is the whole decision for most people, and I would rather state it up front than pretend Misago (GPL-2.0, Python, 2,777 stars) competes on breadth. What it offers is a clean, modern, threaded discussion board with sensible moderation built in, running on a stack a Django developer already understands, at about 1 GB of RAM instead of the 2 GB or more Discourse expects.

The shape of the software

Misago is a classic forum in the phpBB tradition, rebuilt on Django with a React front end: categories, threads, posts, private threads, user profiles, ranks, and a moderation toolset covering warnings, bans, post approval queues and IP tracking. It has been developed by essentially one maintainer since 2016, which is both the reason the codebase is coherent and the reason the release cadence is slower than the big projects. There is a REST API, which matters if you plan to integrate signups with an existing app. Extensions exist but the ecosystem is small; if your forum plan depends on a specific plugin, check that Misago has it before you commit, because it probably does not and you will be writing it.

Where it genuinely shines is readability. A Discourse deployment is a Ruby application inside a bespoke container build system, and customising it beyond themes means learning that system. Misago is pip install-shaped Django. If your team writes Python, that difference dominates.

Deploy with the companion Docker repo, not the main one

The main repository is the application source. For a production install, the maintainer publishes a separate deployment repository, misago-docker, whose setup script asks a dozen questions and produces a stack with PostgreSQL, Redis, the Django app, a Celery worker, nginx and Let's Encrypt handling. That is the path to use:

git clone https://github.com/rafalp/misago-docker.git
cd misago-docker
./appctl setup

Have your domain's DNS pointing at the box before you run it, because the certificate step happens during setup. The same appctl script handles upgrades, backups (./appctl backup dumps the database and media into a tarball) and restores, and it is one of the better operational wrappers I have seen on a small project. If you already run Caddy or another proxy, you can skip the bundled nginx and TLS, but expect to read the compose file rather than follow a tutorial.

Resource-wise, the catalogue's 1,024 MB floor is right for a forum with a few hundred members. Email is the classic missing step: without working SMTP there are no activation mails and no notifications, and a forum without notifications dies quietly.

What you give up versus the giants

Three things. Discourse's trust-level system, which automatically grants moderation-lite powers to established members, has no equivalent; Misago's ranks are manual. Discourse and NodeBB both have real-time features (live updates, chat) that Misago does not attempt. And the plugin market that makes Discourse a platform, with SSO connectors for everything, event calendars and paid subscriptions, is simply absent. Flarum sits between them: lighter than Discourse, bigger extension catalogue than Misago, PHP rather than Python. If none of the three languages matters to you, the social category is where I would compare on community size alone, and Discourse wins that comparison.

Migrating from phpBB is possible but not turnkey; the catalogue's phpBB alternatives page is honest that every forum migration involves scripting user, category and post imports yourself.

Who actually runs Misago

Python shops that want their community forum in a language they can maintain, small and mid-sized hobby communities that want a classic threaded board without Discourse's weight, and projects that need to embed forum accounts in a wider Django application. It is also the forum I see chosen by people who tried Discourse on a 2 GB VPS, watched it swap, and wanted something that stays under 1 GB with room for a second service.

What I'd do

If I were launching a community with unknown growth and no language preference, I would run Discourse and accept its appetite; it is the safer pick and the one whose future is least in question. If I were a Python developer building a forum for a few hundred people, or bolting a board onto an existing Django product, I would run Misago via misago-docker on a 2 GB VPS, wire SMTP on day one, schedule ./appctl backup nightly, and enjoy being able to read the code when something needs changing.