Back to Discover
Discourse logo

Discourse

StartupLaunched September 2026

Screenshots

The Story

Discourse is forum software designed for threaded, long-form discussion. Unlike a chat product, a topic is a first-class object with a title, a category, and replies that can be read in order, which makes a community's history searchable and referenceable.

The platform adds the mechanics a community needs to stay healthy: trust levels that grant permissions as a member participates, flagging and moderation queues, and automated summaries. Topics can be categorised and tagged, and a topic can be marked as solved so the answer is visible without reading the thread.

Discourse is open source and can be self-hosted, with a hosted plan as the alternative. It is a good fit for a product community, a support forum, or a standards discussion where answers should be findable later. It is a poor fit for real-time conversation, which is what a chat product is for.

Overview

Discourse's design assumption is that a community's value is its accumulated answers, so topics are structured to be found rather than only read live.

A topic has a title, a category, and an ordered set of replies. That structure is what makes a forum different from a chat channel: a question asked a year ago is still addressable, and the accepted answer can be marked so a reader does not have to reconstruct it from the thread.

Community health is handled with mechanics rather than only moderation. Trust levels grant permissions as a member participates, which distributes some moderation work to people who have demonstrated they will use it well. Flagging opens a moderation queue, and automated summaries surface long threads.

The platform is open source and can be self-hosted, with a hosted plan as the alternative. It suits a product community, a support forum, or a standards discussion where answers should remain findable. Real-time conversation is a different problem and a chat product serves it better.

Key Features

  • Topics and categories

    Discussion is organised into titled topics within categories and tags, so history stays addressable.

  • Trust levels

    Permissions are granted as a member participates, which distributes some moderation work across the community.

  • Solved topics

    An answer can be marked as the solution, so a reader finds it without reconstructing the thread.

  • Self-hostable

    The platform is open source and can run on your own infrastructure, keeping the community's data under your control.

Where Discourse is a strong choice, and where it is not

Choose Discourse when a community needs long-form discussion whose answers remain findable, and moderation should scale with participation.

Look elsewhere if the need is real-time conversation or a simple comment section. A forum is a different shape from a chat product and a heavier one than embedded comments.

Getting started

The hosted version is live in minutes; self-hosting takes an afternoon.

  • ~30 min
    Time to first topic

    On the hosted plan, create a community and post. Categories work without configuration.

  • Free
    Cost to start

    Self-hosted is free. Hosted plans are priced by community size.

  • Docker for self-host
    Prerequisites

    Nothing for hosted. Self-hosting needs Docker, Postgres, and Redis.

Known limitations

Constraints confirmed from the project's documentation.

  • Self-hosting is a real commitment. The database, mail configuration, and upgrades are yours.
  • Email deliverability matters. A self-hosted forum needs a sending setup that inboxes accept, or notifications fail.
  • Not for real-time chat. It is a forum; live conversation is a different product.
  • Requires seeding. A new forum with no topics stays empty; communities need an initial push.
OUR VERDICT

Pick Discourse when answers should stay findable

Topics have titles and ordered replies, so a question asked a year ago is still addressable.

Trust levels distribute some moderation work as members participate, which is how a community scales without a large moderation team.

If the need is real-time conversation or a simple comment section, a forum is a heavier shape than required.

FAQ

What is Discourse?

Discourse is open-source forum software for long-form, threaded community discussion with moderation and trust-level mechanics.

Is Discourse free?

The software is open source and free to self-host. Hosted plans are priced by community size.

How is it different from chat?

Topics have titles and ordered replies, so discussion remains searchable and referenceable rather than scrolling away.

What are trust levels?

Permissions granted as a member participates, which lets experienced members take on some moderation work.

What stack is Discourse built with?

CompassPad records Discourse as a Ruby on Rails backend with PostgreSQL and an Ember frontend, based on its public repository.

What we checked

  • LIVE
    Site and primary link

    The marketing site resolved and the primary product link reached the application.

  • PRICING
    Pricing page

    The pricing page resolved and lists a free self-hosted option alongside paid hosted plans.

  • DOCS
    Documentation

    Documentation is public and covers installation, moderation, and administration.

  • FRESHNESS
    Changelog

    Dated releases are published on a public forum category and are reachable without an account.

Discussion

No comments yet. Be the first.

Join the conversation. Sign up to comment.

Sign up free

Similar But Scrappier

Notion

FeaturedTrending

Documents, databases, and wikis in one workspace with a shared editor.

Communication & CommunityCCompassPad editorial

Notion is a workspace where documents and databases are the same primitive. A page contains blocks, and a database is a collection of pages with typed properties, which means a task list, a content calendar, and a project tracker are all views over pages rather than separate applications. The product grew by replacing several tools at once: notes, a lightweight wiki, a task board, and a simple database. Because everything shares one editor and one permission model, a team can link a project page to a task database and see the same records from both. Templates and a public gallery spread reusable structures. The tradeoff is depth. A Notion database is not a relational database, so reporting is limited compared with a real BI tool, and large datasets slow down. Teams that push it into that role tend to add a proper database and analytics stack alongside it.

Discord

FeaturedTrending

Voice, video, and text channels organised into servers.

Communication & CommunityCCompassPad editorial

Discord is a communication platform organised around servers, each containing channels. A channel is text, voice, or a forum, and permissions are set per role, so a server can be private to a team or open to a large community with the same primitives. The product began in gaming and spread because the combination of always-available voice and persistent text suited any group that spends time together online. Voice channels are joinable without a call being placed, which removes the scheduling step that a meeting tool requires. Screen sharing and video are available in the same channel. For communities, the platform provides moderation tooling, role-based access, and bots that extend a server with automation. The tradeoff is that history and membership live in a vendor's account rather than on infrastructure the community controls, and the interface is optimised for live presence rather than for durable documentation.

Slack

Channel-based messaging with an app platform for workplace workflows.

Communication & CommunityCCompassPad editorial

Slack is a messaging platform for organisations, organised around channels. A channel is a named conversation that can be public, private, or shared with an external organisation, and membership is a deliberate act rather than an accident of a contact list. The structure is what distinguishes it from a group chat. Threads keep a reply attached to its parent, so a channel is not consumed by a side conversation. Search covers message history and files, and a shared channel lets two organisations work in the same space without exchanging accounts. The platform's second half is the app directory and workflow builder. Incoming webhooks, slash commands, and bots let an external system post into a channel or accept a command from one, which is how alerts and approvals end up where a team already is. The cost is per-seat pricing and the fact that an organisation's conversation history lives in a vendor account.