Loomio: A Self-Hostable Decision-Making Tool for Collaborative Groups

What Loomio Solves and Who It Serves

Loomio addresses a specific pain: making decisions as a group without endless email threads or chaotic meetings. It is built for collaborative organizations, which the README describes as groups that need a structured way to propose, discuss, and decide. The target users are cooperatives, nonprofits, community groups, and distributed teams. If your organization regularly faces questions like 'should we adopt this policy?' or 'which vendor do we pick?', Loomio gives a shared space to formalize that process. It is not a general-purpose chat app; it is a decision engine. The README points to Loomio.com for trying it, but the core value for engineers is the self-hosted option, which is the focus of this review.

The Core Mechanism: Proposals, Discussion, and Decisions

Based on the repository and the product's stated purpose, Loomio's mechanism revolves around creating a proposal within a group. Members can then discuss it, and the tool provides a clear way to signal agreement, disagreement, or abstention. The exact UI and data flow are not detailed in the README, but the concept is that decisions are made explicit rather than left implicit. The architecture is a Ruby application, which suggests a typical Rails-style stack, but the README does not confirm the framework. The key point is that Loomio replaces informal consent with a visible, auditable trail. That trail matters for organizations that need to show how a decision was reached, whether for governance or legal reasons.

Getting Started: Self-Hosting and Development Setup

The README points to two guides for running Loomio yourself. For production, you follow the self-hosting deployment guide at deploy/README.md. For development, you use DEVSETUP.md. The README does not list the exact commands, but the presence of these guides means you will need to clone the repository and follow step-by-step instructions. Expect to install Ruby, a database (likely PostgreSQL, though not stated), and configure environment variables. The deployment guide likely covers Docker or a traditional server setup, but without reading it, you must verify the specifics. The development guide probably includes bundle install and database migration steps, but again, the README is silent. Start by reading those two files; they are the authoritative source for setup.

Licensing and Community Contribution

Loomio is released under the GNU Affero General Public License (AGPL-3.0). This is a strong copyleft license. If you modify the software and offer it over a network, you must make your modified source available to users. That is a critical consideration for any organization that plans to customize Loomio internally. The README encourages contributions via GitHub issues and mentions a Loomio Co-op Handbook, indicating a cooperative governance model. The license means you can freely use and modify it for internal purposes, but if you provide Loomio as a service to others, be prepared to share your changes. This is not legal advice; consult a lawyer for your specific situation.

A Genuine Limitation: Not a Chat Replacement

Loomio is not a real-time messaging platform. If your team expects to have quick back-and-forth discussions, you will still need a separate tool like Slack or Matrix. Loomio is designed for asynchronous, structured decision-making. That means decisions may take longer because they are not immediate. Also, the README does not mention integrations with other tools, so you may need to manually transfer context from chat into Loomio. For small teams that make decisions quickly in a meeting, Loomio could feel like overhead. It is the wrong tool if your organization has no formal decision process or if members resist following a structured workflow.

Alternative Approach: Regular Issue Trackers or Polls

A simpler alternative is to use a generic issue tracker like GitHub Issues or a polling tool like Doodle. The difference is that those tools are not designed for decision-making. An issue tracker can host a discussion, but it lacks a built-in mechanism to formally close a decision with consent. A poll can collect votes, but it does not support nuanced positions like 'agree with reservations' or a discussion thread. Loomio's approach is to combine discussion and voting in one place, with a clear outcome. If your group already uses an issue tracker and you only need occasional polls, the alternative is lighter. But if you need a repeatable, auditable decision process, Loomio offers a purpose-built structure.

Maintenance and Upgrade Cost

The repository shows recent releases, with v3.4.2 pushed on 2026-08-28. That indicates active maintenance. However, the README does not provide a changelog or migration notes. Upgrading a Ruby application can involve dependency changes, database migrations, and configuration updates. The cost of maintenance depends on your familiarity with Ruby. If you are not a Ruby developer, you may struggle with customizations. The self-hosting guide is the first place to check for upgrade instructions. The AGPL license also imposes obligations if you distribute modified versions, which adds a compliance cost. Before adopting, read the deployment guide thoroughly to understand the server requirements and upgrade path.

Editorial conclusion

Adopt Loomio if you run a cooperative, nonprofit, or distributed team that needs structured, asynchronous decision-making and wants full control over data via self-hosting. Do not adopt it if you need real-time chat or if your group cannot commit to learning a dedicated decision workflow. Before adopting, verify the deployment guide's requirements, test the AGPL obligations with your legal counsel, and check the issue tracker for current bugs or missing features that affect your use case.

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes