Helios Voting
Open-source verifiable election software for organizational and committee voting.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Application platform deployment
Runs in
Documented customer environment
Helios web service, PostgreSQL, election state and configured authentication using upstream Fly or Heroku artifacts.
- Fly.io: Customer platform workspace
- Heroku: Customer platform workspace
- Heroku
- Fly.io
Servers / containers
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
- Fly.io: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Fly Config ↗ · Source checked 2026-11-19
- Heroku: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Heroku Procfile ↗ · 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 method | Application platform deployment |
|---|---|
| Infrastructure | Servers / containers Helios web service, PostgreSQL, election state and configured authentication using upstream Fly or Heroku artifacts. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | Apache License 2.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.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The upstream authentication registry enables CAS and configured social-provider login. The provider implementations validate returned identity and map it into Helios users. Select the deployment configuration and provider credentials; election/voter eligibility is separately controlled and development login is not production federation.
Moving upstream Helios authentication implementations; administrator/voter policy remains deployment-specific · Source ↗ · CAS implementation ↗ · Google authentication ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The reviewed source supplies deployment configuration for Helios web service, PostgreSQL, election state and configured authentication using upstream Fly or Heroku artifacts. Set organization-specific secrets, networking, storage and compatible image versions before use.
Helios Voting deployment example; review the full linked installation instructions · Deployment artifact ↗ (master (moving branch)) · Reviewed 2026-11-19
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The upstream Fly configuration assigns separate web and worker processes one shared CPU and 1 GB memory each, with request-concurrency settings. These are example machine allocations, not a total deployment or election-capacity guarantee; database, Redis, tallying peaks, replicas and persistent data require separate sizing.
Moving upstream Fly example web/worker allocations; not a workload-tested HA minimum · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Helios Voting; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (8 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.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The upstream Fly migration guide requires an election-free window, preservation of secrets and the existing public URL, and a rollback plan. The deployment artifacts do not certify election suitability or remove the need to validate the organization's election process.
Community & maintenance
The reviewed upstream contributor history includes benadida, McCio, shirlei, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Board & committee governance
- Open-source verifiable election software for organizational and committee voting.
Compare within Board & committee governance
- BeleniosSelf-hosted verifiable online voting with separated election administration, credential and trustee roles.
- Azure
- BoardPAC On-PremiseCustomer-hosted board meeting and governance platform with role-based meeting access.
- Azure
- FormKiQ Board and Committee Governance Directory PublisherManage board meeting documentation, agendas, resolutions, minutes, and committee records with controlled access, version management, and long-term retention.
- AWS
- Indico (CERN)CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.
- Railway
- Minute (i.AI)Open-source meeting transcription and minute generation developed for public-sector use.
- AWS
- OpenSlidesSelf-hosted assembly governance for agendas, motions, elections and meeting participation.
- Railway
These products address related workflows; read their category-fit notes before comparing scope. See all of Board & committee governance →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Fly Config ↗raw.githubusercontent.com
- Heroku Procfile ↗raw.githubusercontent.com
- Fly Guide ↗raw.githubusercontent.com
- Apache-2.0 ↗raw.githubusercontent.com
- Commits ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Fly Config ↗ · Fly.io
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Helios web service, PostgreSQL, election state and configured authentication using upstream Fly or Heroku artifacts. The upstream Fly migration guide requires an election-free window, preservation of secrets and the existing public URL, and a rollback plan. The deployment artifacts do not certify election suitability or remove the need to validate the organization's election process.
- Heroku Procfile ↗ · Heroku
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Helios web service, PostgreSQL, election state and configured authentication using upstream Fly or Heroku artifacts. The upstream Fly migration guide requires an election-free window, preservation of secrets and the existing public URL, and a rollback plan. The deployment artifacts do not certify election suitability or remove the need to validate the organization's election process.
- Fly Config ↗ · Fly.io
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com