Self-hosted forum: own your community with Discourse

Every community needs a home, and most of them are renting. Maybe it's a Facebook Group whose reach gets throttled the moment you post a link, a Slack that swallows its own history behind a message cap, or a Discord where years of conversation are really just someone else's search index. These places feel free because the community *is* the product — the members, the threads, the attention. And when you decide to leave, the door is narrow and the export is thin. A forum you run is the opposite: your domain, your rules, your data, ready to pick up and carry. Discourse is how you build one.

What Discourse is

Discourse is open-source forum software — the full, professional thing, not a stripped-down message board. It's what a lot of the internet's largest communities actually run: product companies fielding thousands of support threads, open-source projects coordinating in public, hobbyist communities that outgrew a subreddit. Categories, threaded discussion, real-time updates, moderation, email, search, and a plugin ecosystem all ship out of the box. It's licensed under the GPL — the detail that makes "run your own" more than a slogan, since the right to read the code, change it, and keep running it can't be revoked. It also installs as a web app on phones, with real push notifications, so owning your community never means settling for desktop-only.

Discourse the company also sells hosting, and that's where the meter starts. The paid tiers gate the things you actually want — custom themes, single sign-on, more staff seats, and custom plugins only on the enterprise plan — behind steps that climb into hundreds of dollars a month. The software itself is free and complete. Every feature below ships in the version you can run yourself, with nothing held back for a higher plan.

The features that actually matter

• Trust levels. Members earn their way from new visitor to trusted regular automatically, based on how much they read and how well they participate. It's the mechanism that lets a big forum partly moderate itself, and it's on from day one.
• Moderation tools. Community flagging auto-hides a bad post once enough people flag it, a review queue puts everything questionable in one place, and staff can silence, suspend, or anonymize accounts with a full action log behind it. Real tools for real problems.
• Reply by email. Members can answer a thread straight from their inbox and have it post back to the forum, start topics by emailing a category, or follow whole categories in mailing-list mode. The forum meets people where they already are.
• Real-time discussion and chat. Topics update live as replies land, notifications arrive instantly, and the built-in Chat gives you Slack-style channels alongside the long-form threads — without a second app or a second bill.
• Categories, tags, and search. Nest categories, apply tags, set per-category permissions, and lean on genuinely fast full-text search so a five-year-old answer is still findable.
• Themes and full branding. A deep theming system means your logo, your colors, your fonts, your domain — not a subdomain wearing someone else's chrome. Install theme components from Git or write your own CSS.
• Plugins and single sign-on. Official plugins add solved-answer marking, feature voting, an SQL data explorer, AI, spam filtering, and more, and DiscourseConnect lets your forum share logins with your main site. On hosted Discourse, plugins and SSO are exactly what the upper tiers charge for.

Why self-host it instead of the hosted version

Your data stays yours. Every post, member profile, and private message lives in a database you control, on a server you can back up, export, and move. There's no platform quietly mining the conversation or deciding your community violated a policy nobody read to you. Discourse's own admin panel hands you a complete backup as a single archive, so "move it somewhere else" isn't a support ticket — it's a download.

The cost doesn't scale per seat. Hosted community platforms charge by members, staff, or plan tier, so success gets expensive fast: the more your forum grows, the more you pay just to keep it running. Self-hosted, your bill tracks the server, not the headcount. A thriving 50,000-member community costs the same to host as a quiet one.

You control the whole thing. Custom themes, any plugin you want, your own domain, your own moderation policy, your own SSO — none of it gated behind an enterprise upsell. The forum looks like you, behaves the way you decided, and integrates with the rest of your stack because you hold the keys.

Who it's for

• Product and SaaS companies that want a real support-and-community forum on their own domain, with SSO into their app, instead of a rented help center.
• Open-source projects and creators with an audience — a place to coordinate, answer questions, and keep an archive that belongs to the project, not to a chat platform.
• Niche and hobbyist communities leaving a Facebook Group, subreddit, or overgrown Discord for somewhere the history is searchable, the moderation is yours, and nobody throttles your posts.

The honest setup notes

Rolling your own Discourse is a real commitment. A few things are genuinely on you:

• Email is not optional. Discourse won't even finish setup without working outbound SMTP — signups, notifications, digests, and reply-by-email all depend on it, and getting mail to actually land in inboxes is its own deliverability rabbit hole.
• It's a real application stack. Discourse runs on Postgres and Redis behind a Rails app, wants around 2 GB of RAM to be comfortable, and updates often — you'll be rebuilding the container to stay current and patched.
• Backups are yours to keep. Discourse has an excellent built-in backup system, but *storing* those backups somewhere safe, and testing that they actually restore, is a job that doesn't do itself.

None of that is hard, exactly — it's just steady, ongoing care. Or let us run it. On Caliber Node the SMTP relay, the database, Redis, the resources, and the backups are wired up and watched for you, so you get the forum without the sysadmin second job.

Deploy it in one click

Doing this by hand means provisioning a server, installing Docker, cloning the Discourse setup, editing config files, wiring up SMTP, pointing DNS, and then owning every update and backup from there on. It's well-documented and thousands of people have done it — but it's an afternoon that turns into a standing chore.

On Caliber Node it's a menu choice. You deploy Discourse in one click, we hand you a running forum on your domain with mail already flowing through our managed relay, and you spend your time building the community instead of the infrastructure. Updates, backups, and the moving parts underneath are handled, and you still get real logs, SFTP, and a full export whenever you want one.

First run

1. Deploy Discourse from the Caliber Node app catalog and point your domain at it.
2. Open the site, create the first admin account, and walk through the setup wizard — name, logo, colors.
3. Add a few categories that match how your community actually thinks (Support, Announcements, General).
4. Set your trust-level and moderation defaults, and invite your first members or staff.
5. Start the first topic. That opening thread is your community's front door — the rest grows from there.

The bigger picture

A community is one of the most valuable things you can build online, and it's worth owning outright. When your forum lives on your own server, on your own domain, with your own data, nobody can rate-limit it, mine it, wall it off, or shut it down because a policy changed. You're not a tenant on a platform that monetizes your members — you're the landlord. Discourse is mature, capable, and genuinely yours, and that's the whole point.

Deploy Discourse in a few minutes →

Or browse the full app catalog.

One-click self-hosted apps, managed for you — real logs, SFTP, and your data always exportable. Never a black box.