Discourse

Self-hosted community software, honestly reviewed. No marketing copy, just what you actually get when you run it yourself.

TL;DR

• What it is: Open-source (GPL-2.0) community platform — think modern forums plus real-time chat, built for teams that want to own their community infrastructure [1].
• Who it’s for: Tech companies, open-source projects, SaaS builders, and product teams that need a structured discussion space without paying $100–$500/month to Circle, Khoros, or Gainsight [2].
• Cost savings: Discourse managed hosting starts at $20/month; Circle starts at $89/month. Self-hosted on a $10 VPS costs effectively zero beyond hardware.
• Key strength: 10+ years of battle-testing, 46,578 GitHub stars, powering 22,000+ communities including some of the internet’s busiest. Real-time chat, trust level systems, email integration, and a plugin ecosystem built on a stable, auditable GPL codebase [1][2].
• Key weakness: Heavy server requirements for a forum platform (Ruby on Rails + PostgreSQL + Redis means you need a real server, not a $3 VPS). The hosted plan’s pricing tiers gate things you’d expect free — like custom domains, API access, and even themes — behind the $100/month Pro tier [1].

---

What is Discourse

Discourse is a community discussion platform. You get threaded topics, real-time chat channels, private messages, user profiles, moderation tools, and a plugin system — all running on your own server or Discourse’s managed hosting.

The project started in 2013 with a specific thesis: forum software had been stuck in the phpBB era for a decade, and the internet deserved something that worked like a modern web app. That bet paid off. The codebase is now over a decade old, and the platform runs communities for Rust, Ubuntu, Mozilla, Twitch, and thousands of smaller tech projects.

What makes Discourse different from modern SaaS alternatives like Circle or Slack is the combination of GPL-2.0 licensing (full source access, no vendor lock-in, fork it if you need to), a genuinely complete feature set (topics, chat, DMs, email-in/email-out, AI moderation, gamification, voting, docs — all in one install), and a community management model that assumes public, searchable, persistent conversations rather than ephemeral Slack threads [2].

The GitHub repository sits at 46,578 stars. The platform is built on Ruby on Rails (API), Ember.js (frontend), PostgreSQL (primary data store), and Redis (cache). Those aren’t trendy choices in 2026, but they’re stable, well-understood, and the reason Discourse instances can run for years without incident [1].

---

Why People Choose It

The case for Discourse usually starts with one of two pain points: you’re paying for Circle or Slack and the bill keeps climbing, or you’re running a community that actually needs structure — categories, threaded replies, accepted answers, moderation queues — and Slack’s flat channel model is failing you.

Versus Slack / Discord. These tools are great for team chat and real-time coordination. They’re genuinely bad at producing a searchable knowledge base. When your 200th customer asks a question that’s been answered 40 times in Slack, the conversation is effectively lost. Discourse’s model — topics are first-class, searchable, linkable, closeable — means answers accumulate rather than disappear. The enterprise page makes this distinction explicit: “Replace Slack overload with organized, searchable async communication. Give teams a place where conversations don’t disappear and decisions get documented.” [2]

Versus Circle / Mighty Networks. These are the modern SaaS community platforms. Circle starts at $89/month, Mighty Networks at $33/month. Both are closed-source SaaS with the usual risks: pricing changes, data lock-in, and no ability to audit what’s running. Discourse’s self-hosted option eliminates the monthly fee and gives you full data ownership — the README is explicit: “You can self-host Discourse on your own infrastructure.” For communities that are growing but cost-sensitive, self-hosted Discourse makes the math look very different [1][2].

Versus Khoros / Gainsight (enterprise community platforms). These are the enterprise incumbents. Discourse’s enterprise page specifically lists them as migration sources [2]. The pitch against them is cost (both are six-figure contracts) and flexibility (Discourse’s codebase is open, auditable, and extensible via plugins). Discourse Enterprise includes dedicated infrastructure, 99.9% SLA, ISO27001/SOC 2 Type II compliance, custom SSO, and professional migration services — at a significantly lower price point than the Khoros tier [2].

On data sovereignty. A recurring theme in community discussions is data ownership. The Communiteq/DiscourseHosting thread [5] shows that even paying for third-party Discourse hosting is considered acceptable — users cite the ability to download full database backups anytime, move between hosts freely, and access their data without negotiating a contract. The enterprise page reinforces this: “Full export capability anytime. No vendor lock-in. Zero data sold to third parties.” [2]

---

Features

Core discussion:

• Threaded topic-reply model with categories and tags
• Real-time chat (channels, direct messages, group messaging)
• Email-in / email-out — users can reply to topics by replying to emails
• Trust level system — users earn capabilities (posting links, flagging, becoming moderators) based on participation
• Accepted answer marking (via Solved plugin)
• Topic voting for product feedback flows [1]
• Full-text search across all content

Moderation and management:

• Built-in AI spam detection [1]
• Moderation queue, flagging system, auto-close rules
• Admin dashboard with community health metrics
• Automation plugin for workflow rules (auto-tag, auto-close, auto-moderate) [1]
• User notes, warnings, suspensions

Customization:

• Themes and theme components (CSS/HTML/JS)
• Plugin system — official plugins include Discourse AI, Data Explorer (SQL queries against your own community data), Calendar, Gamification, Policy, Topic Voting, and more [1]
• DiscourseConnect (SSO) for integrating with your existing auth system
• Support for SAML, OAuth2, OpenID Connect, Google, GitHub, Discord, and 10+ other auth providers [1]

AI features (newer, Discourse AI plugin):

• AI-assisted moderation
• Content translation (2–10 languages depending on plan) [1]
• AI daily credits system for hosted plans (100k–3M credits/day depending on tier) [1]
• Chatbot integration via Discourse AI plugin

Enterprise:

• Dedicated AWS infrastructure, staging environments [2]
• Custom SSO, SAML, SCIM provisioning
• Role-based permissions, custom reporting, analytics dashboards
• Professional Services: custom themes, plugins, migrations, onboarding [2]
• ISO27001, SOC 2 Type II, GDPR/CCPA compliant hosting [2]
• 99.9% uptime SLA, support spanning 14 time zones [2]

---

Pricing: SaaS vs Self-Hosted Math

Discourse’s managed hosting tiers [1]:

Plan	Price	Key limits
Free	$0	2 staff seats, 500k page views/mo, 5GB storage, 10 categories
Starter	$20/mo	Unlimited categories, tags, groups, email support
Pro	$100/mo	Custom domain, API/webhooks, custom themes, 15+ plugins, 5 staff seats
Business	$500/mo	Advanced analytics, priority support, migrations, 20+ plugins, 15 staff seats
Enterprise	Custom	Dedicated infra, SLA, unlimited staff, 50+ plugins

The biggest gotcha in the pricing table: custom domain and API access require the $100/month Pro tier [1]. If you’re planning to integrate Discourse with anything — your CRM, your product, your support workflow — or put it on your own domain, the Free and Starter tiers aren’t viable. That’s a meaningful price jump.

Self-hosted:

• Software: $0 (GPL-2.0)
• Server: Discourse officially recommends a minimum of 1GB RAM for very small communities, but 2–4GB is realistic for anything with active users. A Hetzner CX21 (2 vCPU, 4GB RAM) runs about $6–9/month.
• Email delivery: You need an SMTP provider for notifications, invites, and email-in. Mailgun, SendGrid, or AWS SES — budget $5–20/month for small communities, free tiers available.
• Your time for setup and ongoing maintenance.

Comparison to Circle:

• Circle Starter: $89/month (includes custom domain, basic community features)
• Circle Professional: $199/month
• Discourse Pro: $100/month for equivalent feature access
• Discourse self-hosted: ~$10–30/month all-in

Concrete math for a product community with ~500 active members and moderate traffic:

• Circle Professional (necessary for API and integrations): $199/month = $2,388/year
• Discourse Pro hosted: $100/month = $1,200/year
• Discourse self-hosted on Hetzner + email: ~$180–300/year

The self-hosted gap is $1,700–2,200/year saved versus Circle. That’s real money for a bootstrapped team. The caveat is meaningful: someone has to manage the server.

---

Deployment Reality Check

Discourse is not a simple deploy. That’s not a knock — it’s just true, and anyone telling you otherwise is selling something.

The official path is Docker-based. The install guide uses a custom discourse-setup script that walks you through DNS configuration, SMTP setup, and SSL certificates. This is more guided than a raw docker-compose file, but it still assumes you’re comfortable with a Linux terminal and DNS records [1].

What you actually need:

• A Linux VPS — Ubuntu is the blessed path. Minimum 2GB RAM; 4GB recommended for any real traffic. An ARM VPS like Hetzner’s Ampere instances work but have occasional plugin compatibility surprises.
• A domain name pointed at the server
• An SMTP provider (Gmail SMTP works but will hit limits; Mailgun or SendGrid is the right call)
• Docker (the installer handles this if you start from a fresh Ubuntu image)

The Scaleway thread [4] — dated but instructive — is a good example of what “deployment reality” looks like in practice. Users in 2016 were testing Scaleway VPS instances and found that Discourse’s performance was sensitive to single-core CPU speed, not just RAM. The consensus: Discourse is not a lightweight application. It runs a full Rails app, Sidekiq workers, PostgreSQL, and Redis simultaneously. A $3 VPS will struggle. A $6–10 VPS with real CPU will run well for small-to-medium communities.

Third-party managed hosting (not Discourse.org): For teams that want someone else to handle the server but don’t want to pay Discourse’s full managed rates, third-party hosts like Communiteq (formerly DiscourseHosting) have been in the market since at least 2014. The Communiteq review thread [5] from that period — still referenced in Discourse Meta — shows a pattern of responsive technical support, full database backup access, and fast setup. That option sits between “run it yourself” and “pay $100/month to Discourse.”

Plugin compatibility: The plugin ecosystem is large and mostly well-maintained, but community plugins occasionally break on major Discourse version upgrades. If you install 15 plugins and one core update breaks two of them, you’re debugging Ruby. Official Discourse plugins (maintained by the core team) are much safer.

Realistic time estimates:

• Technical user following the official guide: 45–90 minutes to a running instance with SSL
• Non-technical founder: a full day, including DNS propagation waits and SMTP debugging
• Migrating from Khoros/Slack with Discourse’s professional services team: weeks, but they handle it [2]

---

Pros and Cons

Pros

• GPL-2.0 license. True open source. Fork it, audit it, run it forever, build a product on top of it. No “Fair-code” or “Business Source” license restrictions [1].
• 10+ years of production hardening. This platform has been running real communities with millions of posts for over a decade. The edge cases are known. The security track record is strong.
• Complete feature set. Topics, chat, DMs, email in/out, gamification, voting, SSO, AI moderation, API, webhooks, plugins — in a single install. You’re not stitching together five SaaS tools.
• 46,578 GitHub stars. This isn’t a niche project that might disappear. The community is large, the plugin ecosystem is real, and the docs are extensive [1].
• Powering serious communities. The “you’re in good company” section isn’t marketing fiction — Discourse runs the official community forums for major open-source projects, tech companies, and game studios [1][2].
• Data ownership. Full export anytime. No negotiation required [2][5].
• Enterprise-grade features exist. SSO, SAML, SOC 2, GDPR compliance, staged rollouts, custom development services — this is not a startup side project [2].
• Email-first design. Email-in and email-out actually work, which matters for communities where many users prefer email digests over web-based reading.

Cons

• Pro tier hides basics. Custom domain and API access require $100/month. If you’re building on Discourse, the Free tier is a demo, not a real starting point [1].
• Server requirements are real. You need 2–4GB RAM minimum for a functioning instance. A shared $3 VPS won’t cut it. [4]
• Ruby on Rails in 2026. This is not a flaw per se, but it’s a consideration. Finding Rails developers who know the codebase is harder than finding Node.js or Go devs. If you need to hire someone to extend or maintain your Discourse instance, the talent pool is smaller.
• Plugin breakage on upgrades. Discourse updates frequently and community plugins occasionally lag behind core changes. If you rely on non-official plugins, test updates in staging first.
• Not a chat-first tool. The chat feature exists and works, but it’s not Slack or Discord. Teams that want real-time collaboration as the primary mode should use a dedicated tool.
• Setup is genuinely involved. The installation guide is good. SMTP configuration, SSL, reverse proxy, email deliverability — these are all solvable, but they’re real steps that take time and knowledge. Non-technical founders will need help [4][5].
• AI features are add-on, not core. The Discourse AI plugin is real and actively developed, but it’s a bolt-on to a discussion platform, not a native AI product. Don’t evaluate Discourse as an AI tool.

---

Who Should Use This / Who Shouldn’t

Use Discourse if:

• You’re building a product community, support forum, or developer community and you want a permanent, searchable home for those conversations instead of a Slack archive that nobody reads.
• You’re paying $100–$500/month for Circle, Mighty Networks, or a similar SaaS community platform and you or your team has the technical capacity to manage a server.
• You’re an open-source project that needs a self-hosted community forum under a license that matches your values.
• You need SSO integration with your existing product (DiscourseConnect is mature and well-documented).
• You want to run SQL queries against your own community data via the Data Explorer plugin. This is genuinely useful for understanding what your community is talking about.

Skip it (stay on Circle / Slack) if:

• Your team is fully non-technical and nobody wants to touch a Linux server.
• Your community use case is primarily real-time chat, not persistent threaded discussion. Discourse chat is fine; Discord and Slack are better for chat-first communities.
• You need a community platform live this week without allocating engineering time. Discourse setup is measured in hours for technical users; longer for everyone else.

Skip it (use Slack/Discord) if:

• Internal team collaboration is your primary use case. Discourse is optimized for community-facing discussion. For internal company communication, the overhead isn’t justified.

Skip it (use a managed host or Discourse’s own hosting) if:

• You need a community running with an SLA and support contract, and server management is not in your wheelhouse. Discourse’s Business tier ($500/month) or Enterprise is expensive but comes with 99.9% uptime guarantees and professional services [2].

---

Alternatives Worth Considering

• Flarum — lighter weight, PHP-based open-source forum. Much lower server requirements than Discourse. Less mature plugin ecosystem. Right choice if Discourse’s resource requirements are the blocker.
• NodeBB — Node.js-based, also modern. Has real-time features and a plugin system. Smaller community than Discourse.
• Circle — the polished SaaS alternative. No server management. Starts at $89/month. Closed source, no data export control. Right choice if you want something live this week and your budget supports it.
• Slack / Discord — right for real-time team chat. Wrong for building a searchable knowledge base. Many teams run both: Slack for internal team, Discourse for public community.
• Ghost — if you primarily want a newsletter/content platform with some community elements (comments, member tiers), Ghost is worth considering. Different product category.
• Khoros / Gainsight — enterprise incumbents Discourse explicitly positions against. Significantly more expensive, closed source, but with enterprise sales support and SLA guarantees that some large companies require [2].

For a non-technical founder evaluating community platforms, the realistic shortlist is Discourse vs Circle. Pick Circle if time-to-launch and zero server management are the priorities. Pick Discourse if data ownership, cost, and long-term extensibility matter more.

---

Bottom Line

Discourse is the closest thing the community platform space has to a boring, reliable default. It’s not exciting — it’s a forum — but it’s a forum that’s been running production communities for over a decade, powers 22,000+ communities ranging from open-source projects to enterprise support hubs, and is available under a genuine open-source license with no commercial use restrictions. The pricing reality check matters: self-hosted is effectively free, managed hosting is competitive with Circle and cheaper than the enterprise alternatives it replaces, and the feature set at every tier is legitimately complete. The costs are the setup complexity (real but manageable), server resource requirements (you need a real VPS, not a $3 shared host), and the occasional friction of maintaining a Rails application with plugins. For a technical founder building a product community, or any team currently paying $200+/month to Circle or a similar closed-source platform, the math for self-hosted Discourse is hard to argue with.

If the server setup is the blocker, that’s exactly what unsubbed.co’s parent studio upready.dev deploys for clients — one-time, you own the infrastructure, no recurring SaaS tax.

---

Sources

1. Discourse Pricing Page — “Change plans anytime. All prices in USD.” discourse.org. https://www.discourse.org/pricing
2. Discourse Enterprise — “Security and compliance that meet your standards.” discourse.org. https://www.discourse.org/enterprise
3. Discourse Pricing (alternate URL) — same content as [1]. https://www.discourse.org/pricing.html
4. “ScaleWay review?” — Discourse Meta community thread — Self-hosting performance discussion, VPS requirements. meta.discourse.org. https://meta.discourse.org/t/scaleway-review/40916
5. “A quick review of Communiteq” — Discourse Meta community thread — Third-party managed Discourse hosting review, 2014. meta.discourse.org. https://meta.discourse.org/t/a-quick-review-of-communiteq/13113

Primary sources:

• GitHub repository: https://github.com/discourse/discourse (46,578 stars, GPL-2.0)
• Official website: https://www.discourse.org
• Pricing page: https://www.discourse.org/pricing
• Enterprise page: https://www.discourse.org/enterprise