
# Board & committee governance on Fly.io

Compare documented Board & committee governance deployments on Fly.io, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/fly/board-committee-governance/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Fly.io organization and app; platform-managed Machines
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.fly.io/launch (checked 2026-11-20).
- Network: App networking and explicitly published services
- Identity and access: Organization/app access, deployment tokens and secrets
- Installation guidance: Use flyctl and fly.toml to deploy the application and database; configure regions, volumes, secrets and recovery.
- Guidance source: https://docs.fly.io/launch
- Guidance reviewed: 2026-11-12


### Organization networking

Fly apps in an organization use the private IPv6 6PN network over WireGuard. Review organization boundaries and external connectivity; the application still runs on platform-managed infrastructure.
Source: https://docs.fly.io/networking/private-networking (reviewed 2026-11-14).

The listings below have evidence for Fly.io. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


## Helios Voting

Open-source verifiable election software for organizational and committee voting.

- Listing: https://launchinyourcloud.com/directory/helios-voting/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: fly, heroku
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Helios web service, PostgreSQL, election state and configured authentication using upstream Fly or Heroku artifacts.
- Operations: 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.
- Product website: https://raw.githubusercontent.com/benadida/helios-server/master/fly.toml
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

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.


### Category fit

- board-committee-governance: Open-source verifiable election software for organizational and committee voting.

### Deployment boundaries


- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/benadida/helios-server/master/fly.toml (checked 2026-11-19). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/benadida/helios-server/master/Procfile (checked 2026-11-19). 


### Cloud deployment evidence

- Fly Config (fly): https://raw.githubusercontent.com/benadida/helios-server/master/fly.toml
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Heroku Procfile (heroku): https://raw.githubusercontent.com/benadida/helios-server/master/Procfile
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/benadida/helios-server/graphs/contributors

- Upstream project: https://github.com/benadida/helios-server

### Sources

- Fly Config: https://raw.githubusercontent.com/benadida/helios-server/master/fly.toml

- Heroku Procfile: https://raw.githubusercontent.com/benadida/helios-server/master/Procfile

- Fly Guide: https://raw.githubusercontent.com/benadida/helios-server/master/docs/migrating-heroku-to-fly.md

- Apache-2.0: https://raw.githubusercontent.com/benadida/helios-server/master/LICENSE

- Commits: https://github.com/benadida/helios-server/commits/master

### Licensing sources

- https://raw.githubusercontent.com/benadida/helios-server/master/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/benadida/helios-server/master/fly.toml

- https://raw.githubusercontent.com/benadida/helios-server/master/Procfile


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. Scope: Moving upstream Helios authentication implementations; administrator/voter policy remains deployment-specific. Source: https://github.com/benadida/helios-server/blob/master/helios_auth/auth_systems/__init__.py (reviewed 2026-11-21). Supporting source: CAS implementation — https://github.com/benadida/helios-server/blob/master/helios_auth/auth_systems/cas.py. Supporting source: Google authentication — https://github.com/benadida/helios-server/blob/master/helios_auth/auth_systems/google.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Helios Voting deployment example; review the full linked installation instructions. Source: https://raw.githubusercontent.com/benadida/helios-server/master/fly.toml (reviewed 2026-11-19). Deployment artifact: https://raw.githubusercontent.com/benadida/helios-server/master/fly.toml. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. 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. Scope: Moving upstream Fly example web/worker allocations; not a workload-tested HA minimum. Source: https://github.com/benadida/helios-server/blob/master/fly.toml (reviewed 2026-11-21).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Helios Voting; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/benadida/helios-server/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






