Community & forums

Discourse

Open-source community platform — forums, built-in chat, and plugins you self-host

discourse/discourseRuby47,558 as of 2026-07-30
By Jake Luo · Published Jul 30, 2026

Discourse is an open-source community platform — discussion topics, built-in real-time chat, themes and a plugin ecosystem — that you self-host on your own infrastructure or run on the project's paid hosting. It has been in active development since 2013 and is the usual choice when a company wants to own its community's software and data outright. For a founder the honest caveat is that the software was never the hard part: a forum works when its members need each other, and until they do, an empty one advertises exactly how few people are engaged.

What Discourse is

Discourse (github.com/discourse/discourse) is a community platform its own README calls 100% open source, built for people who want complete control over how and where their site runs. It is a Ruby on Rails application exposing a JSON REST API, with an Ember.js front end, PostgreSQL as the main data store and Redis for caching, published under the GNU General Public License version 2.0 by Civilized Discourse Construction Kit, Inc. The project has been shipping since January 2013, which makes the README's claim of being battle-tested for over a decade one of the rare ones you can check against a commit history.

What the repo actually ships
  • Discussion topics — the threaded forum at the centre of it, with the reading and moderation tooling a decade of real use produced.
  • Built-in real-time chat, so a community does not have to be split between a forum in one place and a chat app in another.
  • Themes and plugins — an official and community theme selection, plus plugins including Discourse AI for chatbots and Data Explorer for running SQL against your own instance.
  • Self-hosted or hosted — run it on your own infrastructure for the cost of the servers, or pay for the project's official hosting and skip the operations.

Where a forum fits a founder's growth stack

The growth argument for a forum, as opposed to a chat community, is that it is public text with a URL. Every question a customer asks and somebody answers becomes a page — and it is exactly the shape of page that still earns something: a specific problem, in the customer's own words, answered by someone who hit it. That is the long-tail keyword pattern produced as a by-product of support rather than as a content project, and it is the same material AI answer engines retrieve when a person asks about your product. A chat server generates none of it, because the conversation goes invisible to search the moment it scrolls.

The second argument is compounding of a different kind. The answers accumulate, so a question gets answered once in public instead of five times privately, and later members find it without you. That mechanism is community-led growth — value flowing member to member rather than outward from the company. It is real, and it is also the part that cannot be installed.

The empty-room problem

A forum is two-sided, and only one side ships with the software. It needs enough people carrying the same problem to have a reason to talk to each other rather than to you — and below that threshold a public space is actively worse than no space. A visitor landing on a category with four topics and no replies has learned something concrete about how many people use your product, and it is not the impression you were going for. This is why how do I build a community around my product argues that most early products should be participating in communities that already exist instead of hosting one.

First-party note from building AgentCeres — the AI Growth Officer at agentceres.com: our earliest customers came from threads we do not own. Someone described a problem in a public forum, we answered it as a person, and that thread went on being read for months afterwards — it ranks, it gets pulled into AI answers, and it still sends people. It is also the single most valuable piece of writing about us that we cannot edit one word of. That is the honest case for eventually owning the room: the durability of public text, plus control over it. And it is the same reason we have not opened one yet, because the identical thread on our own forum, with nobody else in it, would have convinced no one. The asset was the room full of strangers, not the software running it.

The practical read: adopt Discourse once unanswered questions from real users are arriving faster than you can handle them privately, and there is a plausible reason for two of those users to want to talk to each other. Before that, the same hours spent where they already gather do more, and a customer feedback loop through support threads and reviews gets you the signal a forum would have surfaced without the empty-room cost.

What it costs to run

Self-hosting Discourse is a real service, not a static site. The repo asks for Ruby 3.4 or newer, PostgreSQL 15 and Redis 7, and its install guide is a Docker-based deployment; once it is up you own the backups, upgrades, spam handling and moderation. That is fine for a team already running infrastructure and an unwelcome second product for a solo founder mid-launch, which is why the project's own paid hosting exists and why choosing it is not a failure of nerve.

Whichever way you run it, the software is the cheap part and the moderation is not. A community needs somebody reading it every day through its first months, answering the questions nobody else will yet and setting the tone that later members copy. AgentCeres is the execution layer for the growth work around a product — a roster of specialists drafts the SEO, content, social and outreach, and a human approves anything that goes out — and the line we deliberately draw is that community replies are the motion that tolerates drafting least, because a reply reading as generated costs more trust than the answer was worth.

FAQ

Is Discourse free?
Yes if you self-host it. The code is open source under GPL-2.0, so there is no licence fee and no cap on building a commercial community around it; you pay for servers and for the time to operate and upgrade them. The project also sells official hosting, which trades that operational work for a subscription — check discourse.org for current pricing.
Discourse or Discord — which should a founder pick?
They do different jobs. Discord is real-time and social, good for a group that wants to hang out, and everything said in it is invisible to search the moment it scrolls past. Discourse is durable and indexed: slower, more deliberate, and each thread becomes a page that keeps working. If the value is people helping each other with problems, a forum compounds; if it is presence and chat, Discord fits better. Discourse now ships chat as well, which narrows the gap in one direction only.
Can I self-host Discourse on a cheap VPS?
Technically yes for a small community — it wants PostgreSQL and Redis alongside the app, and a modest instance handles low traffic. The cost that surprises people is not the machine. You are now running a database, a cache and a public-facing web application that receives spam, and you own its upgrades. Budget the attention rather than the server.
Does a forum help SEO?
Genuinely, once it has real content: user questions produce specific, naturally phrased pages that are hard to write deliberately and are exactly what search and AI answer engines both reward — see generative engine optimization. An underpopulated forum does the opposite, filling your domain with thin near-empty pages. The SEO benefit is a consequence of an active community, never a reason to start one.
When should I start a forum?
When members need each other, not when you need a support channel. Concretely: the same questions keep recurring, you are answering them privately more than a few times a week, and users are already comparing notes somewhere else. Until then support tooling and existing communities do the job — community-led growth sets out the difference between a community and a support annex.
Related projects
ChatwootOpen-source customer support platform — live chat, a shared inbox, and an omnichannel help deskFiderOpen-source feedback portal where customers post and vote on feature requests, so you can see what to build nextGhostOpen-source publishing platform — a site, a newsletter, memberships and paid subscriptions in one installDocusaurusOpen-source static-site generator for documentation websites, released by Meta

You built it. Now grow it.

AgentCeres is a managed AI marketing team — specialists draft the SEO, social, and outreach that fill your links, you approve what ships. 14-day free trial, from $39/month.

Start free trialMore projects