Our take
Activeregular commits and releases- Activity
- 65
- Community
- 94
- Issues
- 21
- Pull requests
- 79
+99 stars in the last 30 days
- Merges more pull requests than 86% of the projects we track
- More contributors than 78% of the projects we track
Discourse is an actively maintained, established community platform with a broad contributor base, though teams should plan for its Ruby, Node.js, PostgreSQL, and Redis stack and review the GPL license before adopting it.
Good fit if
- You need a full community discussion platform with topics, chat, themes, and plugins.
- Self-hosting control or official managed hosting suits your deployment needs.
- Your team can operate a Rails and Ember.js application backed by PostgreSQL and Redis.
Look elsewhere if
- You need a lightweight discussion component rather than a complete community platform.
- Your team cannot meet the Ruby, Node.js, PostgreSQL, and Redis requirements.
- GPL-2.0-or-later licensing does not fit your distribution or legal requirements.
All health signals
| Last commit | 2026-11-08 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 1 (latest _gh-attach-assets, 2026-07-15, pre-release) |
| Contributors | 100+ (top contributor: 11% of commits) |
| Issues closed, last 90 days | 0+ |
| Pull requests merged, last 90 days | 79 (typically merged in 0 days) |
| Project age | 13 years |
Checked on 2026-11-09 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
48,088Forks
9,063Change since Nov 16, 2026: +1 stars·+1 forks
Overview
Discourse is an online community platform for creating discussion spaces, with built-in real-time chat and extensions through themes and plugins. Its backend is a Ruby on Rails API, its frontend is an Ember.js app, and PostgreSQL is its main data store, with Redis used for caching and transient data.
It is aimed at people and organizations that want to run a community site and control how and where it operates. You can self-host it on your own infrastructure or use the official hosting service.
Key Features
- Organize community conversations as discussion topics.
- Provide real-time communication with built-in chat.
- Customize the site with official and community themes.
- Extend functionality with plugins, including Discourse AI and Data Explorer.
- Use a Rails JSON API and Ember.js browser application.
- Store primary data in PostgreSQL and use Redis for caching and transient data.
- Deploy through self-hosting or official Discourse hosting.
Use Cases
- A membership organization can host ongoing discussions in a dedicated community space.
- A product team can give users a forum for questions, feature discussions, and peer support.
- A technical community can combine longer-form topics with real-time chat and plugins such as Data Explorer.
- An organization that needs control over where its community runs can self-host Discourse; one that prefers managed infrastructure can use official hosting.
What you need
Detected in the repository
- Node.js >= 20 (from package.json)
- Ruby (from Gemfile)
- A test suite and automated checks on GitHub Actions
License in plain words
GPL-2.0strong copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, the full source of anything you distribute that includes it, under the GPL
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
For self-hosting, the README provides this installation command:
wget -qO- https://raw.githubusercontent.com/discourse/discourse_docker/main/install-discourse | sudo bash
See the installation guide for production setup details and the README for development environment guides.
Considerations
Self-hosting requires operational capacity for the application stack, including PostgreSQL and Redis, as well as the Ruby and Node.js runtimes. The README lists Ruby 4.0, PostgreSQL 18+, and Redis 7 as minimum development versions. The project is active, with regular commits and releases and contributions from many people; recent issue-closure data is capped at zero, so the supplied health measures do not establish a typical issue-resolution time. The repository is licensed under GPL-2.0-or-later, which may affect how teams distribute modified versions.
Found this useful?
Share it with someone who would like discourse.