# Loomio vs Decidim vs CONSUL vs Polis vs Rolebase: choose by scale and governance style

> A practical comparison of Loomio, Decidim, CONSUL Democracy, Polis, and Rolebase: team and board decisions, civic participation, opinion clustering, and self-managed org charts.

For AI agents: curated site map at [https://www.devolute.org/llms.txt](https://www.devolute.org/llms.txt). Canonical HTML (preferred for search engines): [https://www.devolute.org/en/insights/open-source/loomio-vs-decidim-vs-consul-vs-polis-vs-rolebase](https://www.devolute.org/en/insights/open-source/loomio-vs-decidim-vs-consul-vs-polis-vs-rolebase).

- Language: en
- Published: 2026-11-11
- Markdown URL: https://www.devolute.org/en/insights/open-source/loomio-vs-decidim-vs-consul-vs-polis-vs-rolebase.md

## Choose a decision platform by scale and governance style

A board vote, a city budget, and a living org chart are different systems.

A cooperative board, a city participation team, and a flat organisation can all need a recorded decision in the same quarter. **Loomio**, **Decidim**, **CONSUL Democracy**, **Polis**, and **Rolebase** each keep proposals and outcomes in one place. The split is how many people take part, and what counts as a decision: a threaded proposal, a multi-stage civic process, a map of agreement, or a change to roles and meetings.

If identity and data control sit next to this choice, start with **[digital sovereignty](/en/insights/open-source/introduction-digital-sovereignty)** and **[Keycloak SSO](/en/agency/keycloak-sso-implementation)** for staff and member access.

## The shortest summary

- **Choose Loomio** when a cooperative, nonprofit, board, or distributed team decides asynchronously, and the unit of work is a discussion plus a structured poll.
- **Choose Decidim** when a municipality, large association, or member network runs participatory processes at civic scale: budgeting, assemblies, and verified participation.
- **Choose CONSUL Democracy** when a city or public institution needs citizen proposals, participatory budgeting, collaborative legislation, and offline as well as online verification.
- **Choose Polis** when thousands of people should react to short statements, and you need clustering that shows where groups agree.
- **Choose Rolebase** when a self-managed team needs a living org chart, structured meetings, and consent-based decisions on roles.

## Scale and governance style

| Platform | Primary focus | Best for | Key mechanism | Licence |
|---|---|---|---|---|
| **Loomio** | Asynchronous team and board proposals | Cooperatives, nonprofits, boards, distributed teams | Threaded discussions plus structured polls (agree, abstain, disagree, block, ranked choice) | AGPL-3.0 |
| **Decidim** | Civic and large-scale participatory democracy | Municipalities, large associations, member networks | Participatory budgeting, multi-stage assemblies, citizen verification, modular processes | AGPL-3.0 |
| **CONSUL Democracy** | Public-sector participation and citizen proposals | Cities, governments, institutional deployments | Citizen proposals, participatory budgeting, collaborative legislation, offline and online verification | AGPL-3.0 |
| **Polis** | Opinion clustering across a large crowd | Thousands of participants mapping consensus | Short statements with votes; clustering visualises groups that agree | AGPL-3.0 |
| **Rolebase** | Self-management for holacracy and sociocracy | Flat teams that need roles, meetings, and decisions together | Dynamic org charts, structured meeting agendas, consent-based governance | AGPL-3.0 (earlier releases MIT) |

## Start with who may decide, and what the record must prove

Before comparing screens, answer these:

- **Who is in the electorate?** A named board, every member, or any resident who passes a verification step?
- **What is the artefact?** A closed poll, a budget allocation, a legislation draft, a consensus map, or an updated org chart?
- **How often does it run?** A weekly meeting, a seasonal assembly, or a one-off city process?
- **Who operates it?** Moderation, backups, upgrades, and the audit trail have an owner, or the process stalls after launch.
- **Where may the data sit?** Member votes and citizen statements are personal data. Hosting and access logs are part of the decision, not a later hosting ticket.

The same poll widget behaves differently under a 15-person board and a city-wide budget. Scale changes verification, moderation, and what “done” means.

## Loomio: proposals a small electorate can finish

Loomio fits when the people who decide already know each other, or share a membership list, and they need time to read before they vote.

- Discussions stay attached to a proposal, so the rationale is still there when someone joins late.
- Poll types cover the styles boards actually use: agree, abstain, disagree, block, and ranked choice.
- The outcome is a closed decision your minutes can point at.

Plan the cadence before you install it. Loomio disappoints when every thread becomes a poll, or when nobody is allowed to close a proposal. It is also the wrong primary system when the process is a city budget with eligibility checks, or when the real object is the org chart rather than the vote.

## Decidim: modular processes for a large membership or a city

Decidim fits when participation is a programme, not a single meeting. Municipalities, large associations, and member networks use it for participatory budgeting, assemblies that move through stages, and consultations that have to know who was allowed to take part.

What you must design up front:

- **Process modules:** which components are live (proposals, budgets, meetings, assemblies) and which stay switched off.
- **Verification:** how a participant proves they are a resident or a member, and what happens when that check fails.
- **Moderation and phases:** who moves a process from debate to vote to accountability.

Decidim is heavy when a twelve-person board only needed a proposal and a poll. The software will happily model a city. A small team then spends its time on configuration instead of the decision.

## CONSUL Democracy: institutional proposals, budgets, and legislation

CONSUL Democracy is the public-sector path: citizen proposals, participatory budgeting, collaborative legislation, and verification that works online and offline. Cities and government deployments choose it when the process has to survive contact with an existing institution: a census check, a staffed help desk, a paper trail.

Plan verification and the handoff into the institution as the project. The voting interface is the smaller part. Offline verification (in-person or assisted) has to land in the same electorate as the online path, or you publish two incompatible results.

CONSUL Democracy is a poor fit for an internal holacracy meeting or a quick board poll. It expects a public or institutional process with a defined electorate.

## Polis: show where a large crowd already agrees

Polis fits when you have hundreds or thousands of participants and the goal is to see opinion groups, not to pass a motion. People submit short statements and vote on statements others wrote. Clustering groups participants by how they voted and makes the overlapping “agree” region visible.

Use it when a city, association, or network needs a map of consensus before it writes the formal proposal. Plan moderation: statements are the dataset, and an unmoderated stream produces a map nobody can defend. Polis does not replace a binding vote, a budget, or an org chart. Take the consensus you can stand behind into Loomio, Decidim, or CONSUL Democracy when you need a decision with an electorate and a close.

## Rolebase: roles, meetings, and consent in one chart

Rolebase fits flat teams that practise holacracy, sociocracy, or a looser self-management model. The unit of work is the role: who is accountable, which meeting template applies, and which consent decision changes the chart.

- Org charts stay current because role changes go through the governance mode you chose, from open editing to proposal-and-consent.
- Meetings follow a structured agenda, so the decision is attached to the role it affects.
- Consent, majority, and related vote types match how self-managed teams already decide.

The current application is **AGPL-3.0**. Releases published before that licence change remain **MIT**. If you self-host a modified version as a service, read the Affero terms before you assume the older MIT grant still applies.

Rolebase disappoints when the organisation wanted a city-scale citizen process, or a one-off opinion map. It also disappoints when the chart is decorative and meetings still happen in a document nobody updates.

## Licence and operations, briefly

Loomio, Decidim, CONSUL Democracy, and Polis are **AGPL-3.0**. Rolebase’s current application is **AGPL-3.0** as well. AGPL matters when you modify the software and offer that modified version over a network: you have source-publication duties. Running an unmodified upstream release for your own members is a different situation from building a hosted product on a fork. Have counsel read the licence if you intend to ship changes to people outside your organisation.

Self-hosting still means you own upgrades, backups, moderation, and the identity boundary. Staff and member login can sit on **[Keycloak](/en/agency/keycloak-sso-implementation)** (OIDC or SAML). Citizen verification for Decidim or CONSUL Democracy is a separate register, an in-person check, or an assisted channel. The staff directory proves employment or membership. Residency is a different check.

## A practical selection checklist

- **Loomio** when the electorate is a team, board, or cooperative and the decision is a proposal with a poll.
- **Decidim** when the process is modular, multi-stage, and large enough to need verification and facilitation.
- **CONSUL Democracy** when a city or institution must combine proposals, budgeting, legislation, and offline verification.
- **Polis** when you need a consensus map across thousands of statements and votes, ahead of a formal decision.
- **Rolebase** when roles, meeting agendas, and consent decisions are the operating system of the team.

In every case, name the owner of moderation and upgrades before the first public process.

## How Devolute helps

We set the platform up on infrastructure you control, in your private cloud or as a managed private cloud, and leave you with backups, upgrades, and an identity path your operators can explain.

- Staff and member access: **[Keycloak SSO](/en/agency/keycloak-sso-implementation)**
- Data control and operating boundaries: **[Digital sovereignty agency](/en/agency/digital-sovereignty-agency)**

## Related reading

- [Digital sovereignty, SSO, and a sovereign team stack](/en/insights/open-source/introduction-digital-sovereignty)
- [Keycloak vs Auth0 vs Okta](/en/insights/open-source/keycloak-vs-auth0-vs-okta)
