Discourse (Official) Alternatives

A community manager I know runs a 40,000-member product forum and describes his Discourse (Official) bill as "the cheapest expensive thing I pay for." Roughly $100 a month at time of writing for the entry hosted tier — no intro discount, no renewal jump, just a flat price that scales with traffic. He has never regretted it. But he is running a forum that funds a business; the calculus is different for a neighbourhood group or a bootstrapped SaaS with forty active users. This piece is about when the official hosted Discourse is worth its keep, when self-hosting the same open-source software makes more sense, and what else is out there.

When it makes sense to leave Discourse (Official)

The entry price dwarfs your community. The official hosting starts around $100/month at time of writing, and larger communities pay more — the business tier runs several times the entry rate, and enterprise pricing is custom. That is defensible for a forum driving product support and retention. It is not defensible for a hobby community with a few hundred posts a month. Discourse the software is free and open source; you are paying the Discourse team to run it. If your budget is the constraint and your community is small, paying for the privilege of not managing a server stops making sense once the number is bigger than your community's entire budget.

You need things the platform does not do. Official hosting is managed Discourse and nothing but Discourse. No custom server-side plugins that require unsupported modifications, no exotic infrastructure, no running companion services on the same box. Communities that want to stitch together a forum, a chat bridge, custom authentication, or a bespoke data pipeline eventually hit the edges of what managed allows. When your roadmap requires the server, you need a server.

Support is email-only. The hosted product gives you email support from people who wrote the software — arguably the deepest Discourse expertise on the planet — but no phone line and no live chat. For most community operators that is fine. If your forum is mission-critical and you need an escalation path with response-time commitments, that is not what is on offer at the standard tiers.

Traffic tiers make growth expensive. Hosted Discourse pricing scales with page views and storage, so a successful community costs more every year even though the software has not changed. That is fair — bandwidth and storage are real costs — but it means your best case (growth) is also your most expensive case. If your forum is growing fast and your revenue per member is flat, the bill grows faster than the value.

You have the skills in-house. If your team already runs Rails or Postgres infrastructure, the thing Discourse Hosting sells — "you never think about servers" — is solving a problem you do not have. A single small VPS plus a weekend of setup runs Discourse perfectly well for modest communities, and the monthly saving is real money over a few years.

There is also the licensing trap to be aware of before you leave. Discourse is open source under the GPL, so self-hosting is completely legitimate and costs nothing in licence fees — but "free software" is not "free hosting". Postgres needs tuning, Sidekiq jobs need monitoring, and when a plugin update breaks your theme the forum's owner is you. The official hosted product prices that responsibility at roughly $100 a month. Whether that is expensive depends entirely on what an hour of your time is worth and how often things break.

When you should stay

Stay if uptime and updates matter more than the last hundred dollars. Automated updates, daily backups, CDN delivery, and security patching are exactly the chores that self-hosted Discourse operators underestimate. I have maintained self-hosted forums; the software updates frequently and the community expects zero downtime. On hosted, that is someone else's night shift.

Stay if your community has outgrown "small". Once you cross into serious traffic — hundreds of thousands of page views, heavy email delivery, large storage — a hosted platform with a support team that knows the software cold becomes good value again. Self-hosting a busy Discourse instance means managing Sidekiq queues, email deliverability, and Postgres performance for real.

Stay if email is central to how your community works. Discourse's email — digests, notifications, mailing-list mode — is best-in-breed, and deliverability at scale is a genuinely hard problem. Managed hosting gets your sending infrastructure right in ways that a DIY SMTP setup fumbles.

Stay if the migration risk outweighs the savings. A forum is not a brochure site: it is thousands of threads, millions of post rows, user trust, and search rankings built over years. If the community is healthy and the bill is affordable, the risk of a botched migration is worth more than the money you would save. I will always do that maths out loud with a client before recommending a move.

Finally, ask your community what it actually needs before you shop for platforms. I have watched operators migrate a thriving forum onto the wrong abstraction — a chat tool, a comment plugin, a social feed — and lose the archive-shaped thing that made the community valuable. The platform is replaceable; the ten thousand conversations are not.

The alternatives

The honest landscape here: almost every alternative to official Discourse hosting is either "Discourse somewhere cheaper" or "a different kind of community product". Both are legitimate; they are not the same decision. Prices are entry rates at time of writing.

Render — self-hosted Discourse without being a sysadmin full-time

Render is a PaaS where you can run Discourse on a managed server plus a Postgres database, with static sites free and paid services starting at low single-digit dollars per month at time of writing. You keep the real Discourse — plugins included — while the platform handles deploys, SSL, and the underlying machine. This is the route I recommend to technical founders who want official-grade software without the official-grade bill. The trade-off: upgrades, backups, and email configuration are yours, and a 1GB instance will feel tight for a busy forum.

Railway — the fastest way to a running forum

Railway provisions apps and databases from Git with usage-based pricing and a free allowance at time of writing. For standing up a community quickly — a launch cohort, an internal community, a project forum — it is hard to beat for speed. Two cautions from my own use: usage billing on a chatty forum with busy background workers can surprise you, and the free tier is for testing, not for a community anyone depends on. Set a spend cap on day one.

Ploi — server management for people who want a real server

Ploi is a server-management platform aimed at developers and agencies: you bring a cloud server from any major provider and Ploi handles deployment, SSL, backups, and queue workers around it. If you want root-level control with the routine work automated, this is a clean middle path, and the pricing starts from a free tier at time of writing for light use. Discourse-specific tooling is less turnkey than the PaaS options, so expect to get your hands slightly dirty with the container setup.

Ghost(Pro) — if what you actually want is a publication

A surprising number of "we need a forum" conversations end with "we needed an audience, not a discussion board". Ghost(Pro) runs the Ghost publishing platform from $9/month at time of writing, with memberships, newsletters, and comments built in. For a company that wants to publish and let readers respond, it delivers community-adjacent functionality at a tenth of the cost. What it is not: a threaded discussion forum with moderation tooling. If your community's value is in the archive of conversations, stay with Discourse.

Divio — European managed hosting with data residency

Divio offers managed cloud hosting with European data residency and GDPR compliance as a headline feature, from a free tier at time of writing. For communities with European members and strict data-protection requirements — user-generated content is personal data, remember — hosting the forum inside the EU on a platform that treats compliance as core is worth a premium. It is a Docker-based platform, so bring someone comfortable with containers.

CloudAccess.net — managed app hosting for the non-Docker crowd

CloudAccess.net specialises in managed application hosting — the kind of platform where the app is provisioned and maintained for you rather than you assembling infrastructure. For community operators who want a hands-off experience on open-source software without wrestling a PaaS, it is a credible option with support attached. Do your own current-pricing homework before committing; plan structures in this corner of the market change often.

Tiiny.host — for the community that is really a static site

Some "communities" are announcement pages, FAQ hubs, or documentation with a contact form. Tiiny.host hosts static files and simple sites with minimal fuss and minimal cost. If your forum is actually a slow-moving noticeboard where the "discussion" is three posts a year, a static site is honest where a forum platform is theatre.

A checklist item people forget when leaving official hosting: export anything the platform gave you that a generic server will not. DKIM records and sending-domain configuration, Let's Encrypt history, custom email templates, and any support-team knowledge you have accumulated in tickets are not in the backup archive. Spend an hour gathering those before the migration rather than reconstructing them afterwards from memory, because reconstructing them afterwards from memory never goes as well as you think it will.

How to switch without downtime

Forum migrations are unforgiving — every broken thread URL is a lost reader and a lost search ranking — so the process needs more care than a typical site move.

1. Take an official backup first. Discourse's admin panel produces a full backup archive: database plus uploads. Do this regardless of where you are moving to; it is also your rollback plan.
2. Stand up the new Discourse and restore the backup before touching DNS. On hosted platforms or a fresh VPS, restore the archive, then check that a sample of threads, images, and user profiles loads correctly.
3. Verify email before announcing anything. Discourse lives on email — signup confirmations, notifications, digests. Configure SMTP on the new platform and send test messages to Gmail, Outlook, and a corporate mail domain. Broken email silently kills a community's engagement while the website looks perfect.
4. Check plugins and themes. Self-hosted Discourse runs plugins that hosted does not, and custom themes carry over imperfectly. Reinstall plugins one at a time and watch the logs.
5. Plan the DNS cutover for your quietest hour. Lower TTLs a day or two ahead, switch, and keep the old instance reachable (read-only if possible) until TTLs expire. Discourse URLs are clean and persistent — keep the same domain and the same slugs and the migration is invisible to search engines and users.
6. Preserve redirects if the domain or URL structure changes. Discourse's /t/slug/id pattern is stable, so keeping the same domain solves 95% of redirect pain. If you must change domains, map old thread URLs to new ones and put the redirects in at the edge.
7. Keep the old instance alive for at least two weeks and monitor 404s and search console. Forums accrue long-tail search traffic to old threads; that traffic is worth protecting.

One more thought on timing: forums are seasonal and emotional. Migrating during a moderation crisis, a launch, or your community's busiest season multiplies every small problem into a public one. Pick the quietest fortnight you can find, warn the members a week ahead, and do the DNS switch on a weekday morning when you are awake and caffeinated — not on a Friday night before a holiday weekend, which is when I have made every worst hosting decision of my career.

How we evaluate hosting providers

At HostingSpotter, the number we care about is the renewal price — what you pay for the life of the site — because that is where the hosting industry hides its margins. For managed application platforms like Discourse Hosting, the equivalent question is whether the flat monthly fee scales sanely with growth and what is genuinely included: backups, email delivery, migrations, support channels. We rely on first-hand testing and primary sources such as the vendor's own pricing page, and where pricing moves or a number cannot be pinned down, we say "at time of writing" instead of inventing precision. Nobody pays for placement, and when a flat, honest price — like Discourse Hosting's no-intro-discount model — is the exception in this industry, we say that too.