Loomio vs Discourse: Decision-Making vs Discussion
Unlike Most “Forum vs Forum” Comparisons, This One Compares Fundamentally Different Tools
Loomio and Discourse are both community platforms with threaded discussions, but they solve different problems. Discourse is a discussion forum — it’s where conversations happen. Loomio is a decision-making platform — it’s where conversations produce outcomes. Choosing between them is less about which is “better” and more about which problem you’re actually solving.
Overview
Discourse is the modern forum platform. Built in 2013 by Jeff Atwood (co-founder of Stack Overflow), it’s become the default self-hosted forum for open-source projects, gaming communities, and companies. It handles long-form threaded discussions, categories, tagging, moderation, trust levels, and plugins. It’s the gold standard for community discussion software.
Loomio is a collaborative decision-making tool. Born from the Occupy movement in New Zealand, it’s designed for groups that need to go beyond discussion and actually reach decisions. Proposals, polls, ranked choice voting, score voting, dot voting, and time polls are all built in. The discussion features exist to support decision-making, not as an end in themselves.
Feature Comparison
| Feature | Loomio | Discourse |
|---|---|---|
| Primary purpose | Group decision-making | Community discussion |
| Discussion threads | Yes (supporting decisions) | Yes (primary function) |
| Structured voting | 7 types (proposal, poll, ranked choice, score, dot, time, check) | Basic polls via plugin |
| Decision outcomes | Tracked with deadlines and results | No formal decision tracking |
| Categories/Tags | Groups + subgroups | Categories + tags + subcategories |
| User trust levels | Admin/Member/Guest | 5-level trust system |
| Moderation tools | Basic | Extensive (flags, silence, suspend, review queue) |
| Plugin ecosystem | Minimal (webhooks) | 100+ official and community plugins |
| Real-time editing | Hocuspocus collaborative editor | Composer (single-user) |
| Email participation | Vote and reply via email | Reply via email |
| SSO/SAML | Yes | Yes (DiscourseConnect + SAML) |
| API | REST | Full REST API |
| Mobile app | Responsive web only | Progressive Web App + mobile-friendly |
| Language | Ruby on Rails | Ruby on Rails + Ember.js |
| Docker support | Official Compose | Official Docker install |
| License | AGPL-3.0 | GPL-2.0 |
Installation Complexity
Discourse ships with a custom Docker-based installer (discourse-setup) that handles most of the setup. It requires 2 GB RAM, a domain, and SMTP. The install is opinionated — Discourse expects to own the entire server and uses its own nginx internally. Running it behind another reverse proxy requires extra configuration. The biggest complexity is email: Discourse relies heavily on transactional email for everything from signups to notifications.
Loomio uses a standard Docker Compose stack (5 containers: app, worker, Hocuspocus, PostgreSQL, Redis). It’s a more conventional deployment. SMTP is also mandatory — Loomio’s email-based voting and notification system is a core feature, not optional. Memory requirements are lower than Discourse.
| Complexity Factor | Loomio | Discourse |
|---|---|---|
| Container count | 5 | 2 (app + PostgreSQL, all-in-one) |
| Minimum RAM | 2 GB | 2 GB (4 GB recommended) |
| SMTP | Required | Required |
| Install method | Docker Compose | discourse-setup script |
| Reverse proxy | Standard (any proxy works) | Built-in nginx (extra config for external proxy) |
| Setup time | 20-30 min | 30-45 min |
| Plugins | Few | Extensive ecosystem |
Performance and Resource Usage
Discourse is the heavier platform. The Ember.js frontend is feature-rich but demands more browser resources. The backend uses a PostgreSQL + Redis stack with background Sidekiq workers. A small Discourse instance idles at ~1 GB RAM. Active communities with 100+ concurrent users should plan for 4 GB+.
Loomio is lighter. The Rails backend is simpler (fewer features = less code), and the frontend is less demanding. Five containers idle around 700 MB total. Decision-heavy periods (when many polls are active and email notifications are flying) cause temporary spikes but nothing extreme.
| Resource | Loomio | Discourse |
|---|---|---|
| Idle RAM | ~700 MB | ~1 GB |
| Active RAM | ~1.4 GB | ~2-4 GB |
| CPU (idle) | Low | Low-Medium |
| Disk growth | Slow (text-heavy content) | Moderate (uploads, avatars, images) |
Community and Support
Discourse has one of the largest open-source communities in the forum space. Thousands of active installations, a vibrant meta-forum (meta.discourse.org), hundreds of plugins, extensive documentation, and professional support options. Finding help for any Discourse issue is straightforward.
Loomio’s community is smaller and more focused on cooperative governance and social enterprise. The project is maintained by a worker-owned cooperative in New Zealand (Loomio Cooperative). Documentation is adequate but not as comprehensive as Discourse’s. Community support happens primarily through the Loomio community instance and GitHub issues.
| Community Metric | Loomio | Discourse |
|---|---|---|
| GitHub stars | ~2,400 | ~43,000+ |
| Active installations | Hundreds | Thousands |
| Plugin ecosystem | Minimal | 100+ plugins |
| Documentation | Good | Excellent |
| Commercial support | Yes (SaaS + enterprise) | Yes (hosting + enterprise) |
Use Cases
Choose Loomio If…
- Your group needs to make formal decisions with documented outcomes
- You want structured voting tools beyond simple polls (ranked choice, dot voting, consent-based proposals)
- You run a cooperative, board, or governance body with decision accountability requirements
- Email-based participation is important — members who won’t check a forum will vote via email
- You need clear records of who voted what and when
Choose Discourse If…
- You need a general-purpose community forum for ongoing discussion
- Content moderation and trust levels matter (community self-policing)
- You want a rich plugin ecosystem (chat, events, voting, gamification, AI)
- SEO for public discussions matters to you
- Your community is larger than ~50 active members
- You want a progressive web app that works well on mobile
Use Both Together
Some organizations run Discourse for general community discussion and Loomio for formal decisions. This is common in cooperatives and distributed organizations — Discourse handles the “what do people think?” conversations, Loomio handles the “let’s vote on it” moments. The two platforms can be linked via Loomio’s webhook integration to post decision outcomes to Discourse.
Final Verdict
These tools solve different problems, so the winner depends on your problem. If you need a community forum — discussions, Q&A, knowledge sharing, community building — Discourse is the undisputed choice. If you need structured decision-making — proposals, voting, governance, documented outcomes — Loomio is purpose-built for exactly that.
The mistake is using one tool for both. Discourse’s poll plugin is a poor substitute for Loomio’s seven voting types, consent-based proposals, and email voting. And Loomio’s discussion threads are a poor substitute for Discourse’s categories, trust levels, moderation tools, and plugin ecosystem.
For most self-hosters: if you’re building a community, pick Discourse. If you’re running a cooperative or governance body, pick Loomio. If you need both community and governance, run both.
FAQ
Can Discourse’s poll plugin replace Loomio?
For simple yes/no or multiple-choice polls, Discourse’s built-in poll plugin works fine. But it lacks ranked choice, score voting, dot voting, consent-based proposals, email voting, decision deadlines, and outcome tracking. If you need structured governance, Discourse polls are insufficient.
Can Loomio work as a general forum?
Technically yes — it has threaded discussions. But it lacks categories, trust levels, advanced moderation, SEO optimization, a plugin ecosystem, and the performance characteristics needed for large communities. Loomio discussions are designed to support decisions, not be a standalone forum.
Which is easier to self-host?
Loomio is marginally simpler — standard Docker Compose with 5 containers. Discourse uses a custom installer that expects to own the server. Both require SMTP email and a domain.
Can members of both platforms interact?
Not natively. They’re separate platforms with no built-in integration. You can bridge them with webhooks (Loomio posts decision outcomes to Discourse) or link between them manually.
Which handles larger communities better?
Discourse, by a wide margin. It’s designed for communities of thousands with sophisticated caching, CDN support, trust levels for self-moderation, and extensive performance tuning. Loomio works best for groups of 5-200 members making decisions together.
Related
Get self-hosting tips in your inbox
Get the Docker Compose configs, hardware picks, and setup shortcuts we don't put in articles. Weekly. No spam.
Comments