Decidim

Open-source civic participation, proposal, participatory-budgeting and accountability platform.

8 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Decidim patch-release security fixes

Decidim 0.32.2 lists five upstream security advisories and ordered upgrade steps.

Scope: Decidim 0.32.x patch sequence; consult each linked GHSA for its own affected range.

Provider templates can use a different application version; a new deployment date does not establish patch level.

Action: Check the installed Decidim version and follow the 0.32.0, 0.32.1 and 0.32.2 upgrade sequence with database, application and static-file backups.

Primary source · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Docker / Compose

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • Hostinger: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Hostinger Decidim ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodDocker / Compose
InfrastructureServers / containers
Provider-packaged Decidim application stack on a customer-controlled VPS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The v0.32.2 application registers configured OmniAuth providers such as Google and implements verified user registration/identity linking. Provider settings are organisation-specific. This confirms the configured social/OAuth path, not generic SAML/OIDC plugins or identity verification of every participant.

Upstream Decidim v0.32.2 configured provider login; package/organisation scope · Source ↗ · User creation and identity handling ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The versioned installation manual documents creating and configuring a Rails/Decidim application, database, migrations, assets and deployment prerequisites. This is an upstream manual installation path; provider one-click images, TLS, background jobs, storage and upgrades require separate release/configuration review.

Decidim v0.32.2 upstream manual installation, separate from provider packages · Deployment artifact ↗ (v0.32.2) · Reviewed 2026-11-21

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The versioned installation manual/checklist identifies software and operational prerequisites but does not establish numeric production CPU/RAM/storage sizing. Size application/database/search, background jobs, attachments, participation peaks and HA for the selected modules.

Decidim v0.32.2 complete production sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Decidim; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Reviewed upstream v0.32.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

Decidim upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

The provider page does not pin an application version. Verify the deployed image and apply current upstream security maintenance before use. Budget voting and accountability reporting are distinct from a general grant-contract management system. Check the installed Decidim version and follow the 0.32.0, 0.32.1 and 0.32.2 upgrade sequence with database, application and static-file backups.

Community & maintenance

The reviewed upstream contributor history includes andreslucena, alecslupu, mrcasals, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Public participation
Open-source civic participation, proposal, participatory-budgeting and accountability platform.

Compare within Public participation

  • Consul DemocracyOpen-source civic participation and participatory-budgeting platform.
    • DigitalOcean
    • Heroku
    Customer-operated · Open Source / Open Core
  • Pol.isOpen-source deliberation and public-consultation application with a customer-operated AWS stack.
    • AWS
    Customer-operated · Open Source / Open Core

These products address related workflows; read their category-fit notes before comparing scope. See all of Public participation →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Hostinger Decidim ↗ · Hostinger

      Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Provider-packaged Decidim application stack on a customer-controlled VPS. The provider page does not pin an application version. Verify the deployed image and apply current upstream security maintenance before use. Budget voting and accountability reporting are distinct from a general grant-contract management system.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory