Discourse

Advanced forum / community solution based on Ruby and JS.

Thriving · 91
91/100
Thriving

High commit volume, frequent releases and growing activity.

Maintenance 39/40
Releases 21/25
Community 19/20
Momentum 12/15

Commit activity more than 98% of tracked projects; popularity more than 97%. How this is calculated.

Commits, last 11 months

2025-10: 556 commits 2025-11: 501 commits 2025-12: 524 commits 2026-01: 403 commits 2026-02: 636 commits 2026-03: 784 commits 2026-04: 555 commits 2026-05: 623 commits 2026-06: 677 commits 2026-07: 680 commits 2026-08: 583 commits
2025-10 6522 total 2026-08
Stars48k
Latest release_gh-attach-assets · 15 Jul 2026
Repo updated25 Sept 2026
LicenceGPL-2.0
Built withDocker

Is Discourse actively maintained?

Discourse is under active development: 6522 commits landed over the last 11 months, averaging roughly 647 commits a month in the most recent quarter.

The most recent tagged release, _gh-attach-assets, is about 3 months old.

Of the 40 projects we track in Communication - Social Networks and Forums, Discourse ranks #3 by health score — in the top quarter of its category.

What Discourse actually does

Discourse is an advanced web-based platform designed for building online communities, discussion boards, and social forums. It is constructed using Ruby and JavaScript, providing structured environments for multi-user conversation and knowledge sharing. The project is open source under the GPL-2.0 licence and relies heavily on containerisation for deployment.

Best fit: It is well-suited for organisations or administrators who need a heavily maintained, structured forum solution for large communities. It works best when you want a dedicated space for long-form discussions rather than quick chat streams.

Worth knowing: The stack has significant resource requirements and an operational footprint that can be heavy for small hobbyist servers. Running it demands careful management of its containerised dependencies and background worker processes.

Deployment notes

Because the runtime is packaged via Docker, you will typically need to configure persistent storage volumes for database and asset data. You should also place the container behind a reverse proxy to handle TLS termination and incoming HTTP traffic.


Discourse as a replacement for


Alternatives to Discourse

Projects in the same categories, ordered by health score.