0-4 yrs
0-4 yrs
20%
20%
5
5
100+
100+
Smart Discussion Forums
Discourse work splits into two tracks: setting up something new or improving what's already running. New setups involve architecture decisions that are hard to change later (self-hosted vs. managed, plugin strategy, SSO approach). Existing forums usually need plugin fixes, version upgrades, or performance work that the original team didn't get to.
Discourse Innovations
Discourse is flexible enough to run a small team's internal forum or a public community with hundreds of thousands of members. The work we do depends on where your forum is and where it needs to go:
Custom Discourse Setup & Deployment
Ground-up Discourse installations. We handle server provisioning, Docker setup, domain configuration, SSL, email delivery (SMTP or SES), and backup automation. Your forum launches production-ready, not "we'll fix that later" ready. Includes category structure, user roles, and initial plugin set based on your community's goals.
Custom Discourse Plugin Development
Discourse's plugin system lets you add features without forking the core codebase. We build custom plugins for functionality Discourse doesn't include: custom workflows, third-party integrations, automated moderation rules, gamification systems, content gating, and reporting dashboards. Plugins survive Discourse version upgrades because they hook into the plugin API, not patch core files.
Discourse Performance & Scaling
Forums slow down as they grow. We diagnose and fix the bottlenecks: database query optimization, Redis caching configuration, Sidekiq job tuning, CDN setup for assets, and connection pooling for high-concurrency traffic. For large forums, we configure horizontal scaling with load balancers and read replicas.
Discourse Maintenance & Upgrades
Discourse updates frequently. Falling behind on versions means security risks and harder upgrades later. We handle version upgrades, plugin compatibility testing, security patching, backup verification, and monitoring. Your forum stays current without your team spending time on it.
BUILT AROUND YOUR BUSINESS
Discussion Forums with Real-Time Chat
Your community gets both long-form discussion threads and real-time chat channels in one platform. Members can quote chat messages into forum topics and vice versa. No need to run Slack for quick conversations and a separate forum for detailed discussions.
Trust-Based Moderation
Discourse automatically gives members more permissions as they participate. New users start with limited abilities (can't post links or images). Active, trusted members earn the ability to edit titles, move topics, and help moderate. This means your community partially runs itself instead of requiring a full-time moderator for everything.
Single Sign-On (SSO)
Your members log in once with their existing account. Discourse connects to your app's auth system, Google, GitHub, Facebook, Discord, or any SAML/OAuth provider. No separate forum passwords. No "forgot password" support tickets for the forum.
Custom Branding and Themes
Your forum looks like your product, not like a generic discussion board. Custom colors, fonts, layouts, and navigation that match your existing site. Your community feels like part of your product, not a separate tool.
Email Integration
Members can reply to forum posts directly from email without visiting the site. The forum can run in mailing list mode for communities that prefer email. New topics can be created by sending an email. This matters for communities where not everyone wants to check a website.
Built-In Search and SEO
Forum content is indexed by Google. Every discussion your community has becomes a searchable resource that brings new visitors from search engines. Discourse generates sitemaps, handles meta tags, and structures content for search engines automatically.
Badges and Gamification
Recognize active members with built-in and custom badges. Track contributions, milestones, and community health from the admin dashboard. Badges sound small, but they measurably increase participation in forums that use them well.
Mobile Apps
Native iOS and Android apps (Discourse Hub) so your community is accessible from phones without building your own mobile app. The web interface is also fully responsive.
BUILT AROUND YOUR BUSINESS
Ruby on Rails Backend + Ember.js Frontend
Discourse core is a Rails application with an Ember.js single-page app on the frontend. The entire frontend communicates through the same API that's available to you. Every action a user takes in the UI is an API call, which means anything the UI can do, your code can do too.
Plugin Architecture
Plugins hook into Discourse through a defined API: server-side (Ruby) and client-side (Ember.js/JavaScript). Plugins can add routes, controllers, models, serializers, and frontend components without modifying core files. Each plugin lives in its own directory with its own git repository. This separation means core upgrades don't break your custom code, as long as you use the plugin API and not monkey-patches.
Comprehensive REST AP
Full API coverage for topics, posts, categories, users, groups, badges, search, notifications, and admin operations. Token-based or API key authentication. The API is the same one the Ember.js frontend uses, so it covers every operation. Rate limiting is configurable.
PostgreSQL + Redis + Sidekiq
PostgreSQL for all persistent data (posts, users, categories, settings). Redis for caching, session storage, and message bus (real-time updates). Sidekiq for background job processing: email delivery, search indexing, badge granting, and scheduled tasks. Standard Rails stack, no exotic dependencies.
Docker-Based Deployment
Discourse ships as a Docker container managed by its own launcher script. The official deployment is Docker-only. Configuration lives in a YAML file (app.yml) that defines your database, Redis, SMTP, plugin list, and resource limits. One-command rebuilds pull the latest code, install plugins, compile assets, and migrate the database.
Multi-Site / Multi-Tenant
Run multiple independent Discourse forums from a single installation. Each forum (tenant) gets its own database, configuration, and domain. Shared codebase and shared plugins. Useful for SaaS companies offering community forums to their customers, or organizations running separate forums for different teams or products.
Webhooks and Integrations
Outgoing webhooks for topic creation, post creation, user events, and moderation actions. Connect Discourse events to your existing tools: Slack notifications, CRM updates, analytics pipelines, custom workflows. Incoming webhooks for creating content programmatically.
Theme System
Themes are CSS and JavaScript applied on top of the default UI. Each theme has its own git repository and can be updated independently. Theme components let you share reusable UI pieces across themes. No need to fork the Discourse codebase to change the look.
faqs
Frequently Asked Questions
Everything you need to know before getting started with us. Below are out most common questions we get asked.
What is Discourse, and why do companies use it for community forums?
Discourse is an open-source forum platform built on Ruby on Rails. It was created in 2013 by Jeff Atwood (co-founder of Stack Overflow) as a modern replacement for aging forum software like phpBB and vBulletin. Companies use Discourse because it combines long-form discussions with real-time chat, has a trust-based moderation system that scales without hiring a large moderation team, and is fully open-source so you own your data and your platform. It's used by GitHub, Figma, New Relic, and thousands of other organizations for customer support forums, developer communities, and internal discussions.
What does Discourse development and customization involve?
Discourse development covers everything from initial setup and deployment to custom plugin building and ongoing maintenance. Setup work includes server provisioning, Docker configuration, SSO integration, email delivery, and backup automation. Customization means building custom plugins for features Discourse doesn't include, creating branded themes, configuring moderation workflows, and integrating with your existing tools (CRMs, analytics, helpdesks). For existing forums, the work is usually version upgrades, performance optimization, and fixing or replacing broken plugins.
How much does Discourse development cost?
Cost depends on what you need. A standard Discourse setup with a custom theme, SSO integration, and a couple of custom plugins is a smaller project than a multi-tenant installation running dozens of forums with complex plugin systems. Discourse itself is free (open-source), so your costs are development time, hosting, and ongoing maintenance. Development costs scale with the complexity of your customizations and integrations.
Can you migrate our existing forum to Discourse?
Yes. Discourse has built-in import scripts for phpBB, vBulletin, Vanilla Forums, SMF, bbPress, and several other platforms. The full list lives in Discourse's script/import_scripts directory on GitHub and covers dozens of sources. Migration preserves posts, users, categories, and attachments. The tricky parts are usually custom fields, user avatars, and maintaining URL redirects so existing search engine links don't break. We run migrations on a staging instance first, verify data integrity, and only switch production once everything checks out.
What's the difference between self-hosted Discourse and Discourse's managed hosting?
Self-hosted means you run Discourse on your own server (AWS, DigitalOcean, Hetzner, etc.). You control the infrastructure, have full access to the database, can install any plugins, and handle your own backups and upgrades. Discourse's official managed hosting handles all of that for you, but limits which plugins you can install and costs more per month. Self-hosted makes sense when you need custom plugins, want full data control, or run a multi-tenant setup. Managed hosting makes sense when you don't have engineering time for server maintenance.
How do custom Discourse plugins work?
Discourse plugins are Ruby and JavaScript packages that extend the platform without modifying its core code. A plugin can add new database tables, API endpoints, admin settings, frontend components, and background jobs. Plugins hook into Discourse through a defined extension API, which means they survive version upgrades. We build plugins as standalone git repositories that are installed by adding a URL to the Discourse configuration file. The forum rebuilds with the plugin included.
How do you handle Discourse performance at scale?
Performance tuning for Discourse follows the same fundamentals as any Rails application: database query optimization, proper PostgreSQL indexing, Redis caching, and Sidekiq job management. Discourse-specific work includes tuning the message bus (which handles real-time updates), optimizing full-text search for large post databases, configuring CDN for assets and user uploads, and setting up connection pooling (PgBouncer) for high-concurrency traffic. For very large communities, we configure horizontal scaling with load balancers and PostgreSQL read replicas.
Why hire a Discourse development company instead of doing it in-house?
Discourse is a Rails and Ember.js application with its own plugin architecture, theme system, and deployment pipeline. Building a custom plugin requires understanding both the Ruby backend and the Ember.js frontend, plus Discourse's specific conventions for extending each side. Most Rails developers haven't worked with Discourse's plugin API before, and most frontend developers haven't worked with Ember.js. A team with existing Discourse plugin experience can build what you need faster and avoid the common mistakes that cause plugins to break on the next Discourse update.