Discourse Hosting
Run a modern discussion forum with trust levels, moderation tools, and email replies.
- One click deploy
- 4 GB RAM Memory needed
- 50 GB Disk Space Needed
- From 10 € Price
Official links
Discourse’s official links and original website
Discourse Website
More
Tech
- Docker image
- discourse/discourse:latest
- Default port
- 80
- Database
- postgres
How Discourse works
Discourse organises conversation into topics and replies that remain searchable over time. Categories and tags separate subjects, while notifications, bookmarks, summaries, profiles, and moderation tools help members follow and manage participation. The interface updates dynamically without turning every discussion into a chat room that disappears from view.
Trust levels grant capabilities progressively as members participate, reducing the need for administrators to approve every ordinary action manually. Moderators can review flags, manage users and content, close or split topics, and apply site rules. The catalogue stack packages PostgreSQL and Redis with a preconfigured administrator account.
Key Discourse features
Topics can include rich text, links, media, polls, and threaded context through quoted replies. Search, tags, categories, and summaries make older knowledge usable, while badges and trust levels encourage constructive participation. Moderation queues and community flagging distribute some governance work beyond a small administrator group.
Themes, plugins, APIs, single sign-on, and integrations can extend a site, but compatibility must be checked against the deployed release. Email is also central to many normal Discourse workflows. Because application email is disabled in the supplied configuration, verification, invitations, notifications, digests, and password-recovery messages do not operate.
Discourse vs Circle
Discourse is a forum-oriented community platform designed for structured public or private discussion, searchable archives, trust levels, and moderation. Circle is a managed community business platform combining discussions, chat, events, courses, memberships, payments, websites, email marketing, and creator-oriented administration.
Circle may suit organisations that want a provider-run service for monetised programmes, events, courses, and community operations in one subscription. Discourse is a better match when durable topic-based conversation, public knowledge, and self-hosted governance are more important than a bundled creator-commerce platform.
Who uses Discourse
Open-source projects use Discourse for support and development discussion. Companies operate customer communities and knowledge-rich forums, while associations and professional groups create private member spaces with categories and moderation rules.
A healthy community needs more than software. Administrators must define acceptable behaviour, moderator authority, category structure, onboarding, privacy, and escalation. With application email disabled, they must also design account access and engagement without relying on the notification and recovery patterns used by standard Discourse installations.
Self-hosting Discourse: requirements and cost
Capacity depends on members, concurrent visitors, topics, replies, searches, uploads, notifications, background jobs, plugins, moderation, and retained history. PostgreSQL stores forum content and Redis supports the application. AvaHost includes PostgreSQL but leaves it unmanaged, and the database footprint sits outside the listed application minimum.
The adjusted mapping reaches Plan 4 at €20. Discourse hosting combines one-click provisioning, community-domain HTTPS, automatic application updates, and scheduled backups. Application email is disabled, so account verification, invitations, notification messages, digests, reply-by-email, and email-based password recovery are unavailable. The initial administrator credentials therefore require careful custody and a documented non-email support process.
F.A.Q
Discourse starts at €20 on Plan 4 after accounting for PostgreSQL beyond the 4096 MB application minimum. Members, concurrent visitors, topics, replies, searches, uploads, plugins, background jobs, moderation, and retained history drive demand. A real community should be observed under representative traffic before deciding how much operating margin it needs.
The catalogue creates PostgreSQL and Redis and connects them to the Discourse application. Topics, replies, accounts, permissions, trust data, settings, and other forum records depend on the stack. PostgreSQL is included but unmanaged, so database data, uploads, plugins, secrets, and configuration should be considered one recovery and migration unit.
A community hostname can serve Discourse with automated HTTPS after DNS points to AvaHost. Establish the final address before publishing links or configuring integrations. If it changes, verify administrator access, topic links, uploads, API clients, single sign-on callbacks, webhooks, browser bookmarks, and external references that may retain the earlier hostname.
The installation cannot send account-verification messages, invitations, notification emails, digests, or password-recovery links. Browser discussion and moderation remain available, but standard Discourse onboarding and engagement are materially reduced. Administrators should retain the initial owner account securely and confirm a non-email user-creation and recovery process before opening the community to members.