
# Board & committee governance

Agendas, meeting papers, resolutions, minutes and governance records.

Canonical page: https://launchinyourcloud.com/categories/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.


Agendas, meeting papers, resolutions, minutes and governance records.

7 listings.


## Belenios

Self-hosted verifiable online voting with separated election administration, credential and trustee roles.

- Listing: https://launchinyourcloud.com/directory/belenios/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: cloudimg Azure VM with Belenios 3.3.0, nginx/TLS and persistent election spool.
- 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://www.belenios.net
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Azure offer and its complete first-boot guide identify the customer VM and packaged upstream release. Cryptographic verifiability does not certify an election process or replace independent trustees, secure credentials, backups and a threat-model review.

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

cloudimg Azure VM with Belenios 3.3.0, nginx/TLS and persistent election spool. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- board-committee-governance: Self-hosted verifiable online voting with separated election administration, credential and trustee roles.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/belenios-on-ubuntu-24-04-azure/ (checked 2026-11-19). 


### Cloud deployment evidence

- cloudimg Azure Guide (azure): https://www.cloudimg.co.uk/guides/belenios-on-ubuntu-24-04-azure/
  cloudimg Azure VM with Belenios 3.3.0, nginx/TLS and persistent election spool. The Azure offer and its complete first-boot guide identify the customer VM and packaged upstream release. Cryptographic verifiability does not certify an election process or replace independent trustees, secure credentials, backups and a threat-model review.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes glondu, swergas, mateusz-holysz, 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/glondu/belenios/graphs/contributors

- Upstream project: https://github.com/glondu/belenios

### Sources

- cloudimg Azure Guide: https://www.cloudimg.co.uk/guides/belenios-on-ubuntu-24-04-azure/

- Azure Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.belenios-ubuntu-24-04

- AGPL-3.0 COPYING: https://raw.githubusercontent.com/glondu/belenios/master/COPYING

- GitHub Tags: https://github.com/glondu/belenios/tags

### Licensing sources

- https://raw.githubusercontent.com/glondu/belenios/master/COPYING

### Infrastructure sources

- https://www.cloudimg.co.uk/guides/belenios-on-ubuntu-24-04-azure/


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: Belenios selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.belenios-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.belenios-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.belenios-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.belenios-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.belenios-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Documented. The upstream FAQ confirms OpenID Connect authentication and Google as a supported provider, and discusses CAS in the voter-authentication context. Configure the selected instance and election authentication deliberately; this does not prove every Azure image ships configured enterprise federation or that voter and administrator login are identical. Scope: Upstream Belenios instance/election identity options; packaged-image and role scope. Source: https://www.belenios.org/faq.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Upstream documents building/installing with OPAM bootstrap and configuring a server with dependencies and persistent election data. This is distinct from the third-party Azure VM image. Match versions, deploy behind HTTPS and plan secure updates and retained spool data. Scope: Moving upstream manual/source installation; marketplace packaging separate. Source: https://github.com/glondu/belenios/blob/master/INSTALL.md (reviewed 2026-11-21). Deployment artifact: https://github.com/glondu/belenios/blob/master/INSTALL.md. Artifact reference: Current upstream installation guide reviewed on this date.

- Minimum footprint / sizing: Documented. The upstream FAQ describes its own Debian VM with two CPUs, 4 GB RAM and 16 GB disk, and recommends an HTTPS reverse proxy for production. This is an operator reference, not a minimum or guarantee for a 100-user/1-TB HA election service; storage, cryptographic/tallying peaks and replicas need validation. Scope: Upstream Belenios reference server, not a third-party-image or HA sizing guarantee. Source: https://www.belenios.org/faq.html (reviewed 2026-11-21).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Belenios; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/glondu/belenios/master/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## BoardPAC On-Premise

Customer-hosted board meeting and governance platform with role-based meeting access.

- Listing: https://launchinyourcloud.com/directory/boardpac-on-premises/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial subscription software; obtain on-premises order terms
- Licensing model: commercial-only
- Installation: Vendor-assisted on-premises/self-hosted implementation
- Architecture: Persistent customer-hosted board platform with browser and mobile clients; detailed backend requirements must be scoped with BoardPAC.
- Operations: Customer and BoardPAC agree infrastructure ownership, backups, updates and support for the selected on-premises installation.
- Product website: https://boardpac.co/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The official features page explicitly offers on-premises or self-hosted deployment. Confirm the customer-operated topology and the feature set in the on-premises order, especially optional AI and video-conferencing integrations.

BoardPAC uses commercial end-user subscription terms with usage and redistribution restrictions. Confirm the specific on-premises order and support agreement rather than applying SaaS availability terms to customer operations.

Persistent customer-hosted board platform with browser and mobile clients; detailed backend requirements must be scoped with BoardPAC.


### Category fit

- board-committee-governance: Board-meeting collaboration and document access controls through a vendor-supported on-premises board platform.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://boardpac.co/news/boardpac-a-microsoft-azure-partner-joins-azure-marketplace/ (checked 2026-11-12). 


### Cloud deployment evidence

- BoardPAC deployment within an existing Azure environment (azure): https://boardpac.co/news/boardpac-a-microsoft-azure-partner-joins-azure-marketplace/
  The vendor explicitly states that organizations can deploy BoardPAC within their existing Azure environment. This is a vendor deployment statement rather than a public installation guide; agree the customer subscription, backend requirements, operational ownership and commercial terms before deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Board features and self-hosted option: https://boardpac.co/features/

- Commercial subscription and usage terms: https://boardpac.co/terms-of-use/

### Licensing sources

- https://boardpac.co/terms-of-use/

### Infrastructure sources

- https://boardpac.co/features/


### Buyer diligence


Research coverage: 4/12 fields (33%); 1 documented, 3 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: Sources checked — unresolved. The feature page advertises SSO and on-premises deployment, but does not identify the protocol or licensed on-premises configuration. Confirm both before treating a particular identity provider as supported. Scope: On-premises SSO protocol/entitlement unresolved. Source: https://boardpac.co/features/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. BoardPAC advertises on-premises/self-hosted deployment, but the reviewed public features and terms do not supply a backend installer or automation artifact. Mobile-app connection instructions do not establish server installation; obtain the contracted backend package and vendor implementation procedure. Scope: BoardPAC customer-managed backend artifact remains unconfirmed. Source: https://boardpac.co/features/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Sources checked — unresolved. The public self-hosting statement does not specify backend CPU/RAM/storage or HA requirements. Agree the server/database topology, concurrent board users, document processing, offline-device synchronisation and backup/recovery capacity with the vendor. Scope: BoardPAC on-premises backend sizing remains unconfirmed. Source: https://boardpac.co/features/ (reviewed 2026-11-21).

- License pricing: Documented. BoardPAC terms grant time-limited internal use of a subscription subject to the order and restrict redistribution and sublicensing. Confirm the on-premises order, user/device limits, backend entitlement, updates and support separately; general service terms do not establish the final self-hosted price. Scope: BoardPAC public subscription framework; specific on-premises order terms require review. Source: https://boardpac.co/terms-of-use/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## FormKiQ Board and Committee Governance

Manage board meeting documentation, agendas, resolutions, minutes, and committee records with controlled access, version management, and long-term retention.

- Listing: https://launchinyourcloud.com/directory/formkiq-board-committee-governance/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: solution; configured solution on formkiq
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Commercial FormKiQ Advanced or Enterprise; confirm required extensions
- Licensing model: commercial-only
- Installation: Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.
- Architecture: Application on the FormKiQ document and workflow platform
- Operations: Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.
- Product website: https://formkiq.com/solutions/board-committee-governance/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.

This listing describes the packaged Business Solution available through commercial Advanced/Enterprise deployments. The separate open-source Core platform does not by itself include this packaged solution.

Serverless baseline for this business solution; no required OpenSearch dependency is identified. Optional OpenSearch add-ons are evaluated separately and do not add a Hybrid label to this listing.


OpenSearch required for this solution: No

### Category fit

- board-committee-governance: Agendas, meeting papers, resolutions, minutes and governance records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq (checked 2026-11-12). 


### Cloud deployment evidence

- FormKiQ commercial AWS installation (aws): https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq
  The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Edition: FormKiQ platform; solution configuration and entitlement must be agreed separately.


### Sources

- Board and Committee Governance solution: https://formkiq.com/solutions/board-committee-governance/

- Business solution editions and platform relationship: https://formkiq.com/solutions/

- Commercial deployment notes: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq

- Platform infrastructure and optional components: https://docs.formkiq.com/docs/platform/overview

- Licensing and edition terms: https://formkiq.com/pricing/

### Licensing sources

- https://formkiq.com/solutions/

- https://formkiq.com/pricing/

### Infrastructure sources

- https://formkiq.com/solutions/board-committee-governance/

- https://docs.formkiq.com/docs/platform/overview


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 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.

This is a configured solution. Parent platform buyer facts: https://launchinyourcloud.com/directory/formkiq/#buyer-diligence. Parent entitlements, sizing and release versions are not automatically established for this solution.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The solution overview describes configurable access and workflows but does not establish its actual end-user SAML/OIDC integration, identity provider or account mapping. FormKiQ platform Cognito/JWT and IAM/API authentication are separate evidence; obtain the solution-specific login design and included commercial modules. Scope: FormKiQ Board and Committee Governance; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/board-committee-governance/ (reviewed 2026-11-21). Supporting source: Underlying platform architecture — https://docs.formkiq.com/docs/platform/overview.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The overview describes confidentiality controls for board materials, version management and retention policies. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Board and Committee Governance; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/board-committee-governance/ (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Commercial installations use customer-specific CloudFormation templates supplied during onboarding. Request the template for this solution, licensed modules and AWS region; the public Core template does not include the configured solution. Scope: FormKiQ Board and Committee Governance; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/board-committee-governance/ (reviewed 2026-11-16). Supporting source: Commercial deployment and customer-specific templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- Minimum footprint / sizing: Sources checked — unresolved. The configured solution uses customer-specific deployment and optional processing/search/integration modules. No quantitative solution-specific CPU/RAM/concurrency/storage baseline was established. Serverless platform architecture and a document-import benchmark do not size the complete business workflow, external services or HA/recovery requirements. Scope: FormKiQ Board and Committee Governance; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/board-committee-governance/ (reviewed 2026-11-21). Supporting source: Platform architecture and optional components — https://docs.formkiq.com/docs/platform/overview. Supporting source: Commercial deployment templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- License pricing: Documented. The solution requires agreed commercial scope. The solution page identifies Advanced or Enterprise; confirm the edition, modules, implementation and support in a solution quote. Published base-platform prices are not the total solution price; AWS usage and connected services are additional. Scope: FormKiQ Board and Committee Governance; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/board-committee-governance/ (reviewed 2026-11-16). Supporting source: Edition pricing and separately quoted modules/services — https://formkiq.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Indico (CERN)

CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.

- Listing: https://launchinyourcloud.com/directory/indico/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded files.
- 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://getindico.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Railway template is maintained by a community publisher, rather than CERN support. It pins the current reviewed 3.3.14 image. Older third-party images need separate patch verification: upstream 3.3.14 fixes the offline-copy path traversal advisory. Meetings, attachments and agendas are distinct from a full board-governance suite. Use Indico 3.3.14 or a later compatible fixed version; an older Azure image is not covered by the Railway template’s version pin.

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

Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.

- board-committee-governance: CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/indico (checked 2026-11-19). 


### Cloud deployment evidence

- Railway (railway): https://railway.com/deploy/indico
  Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded files. The Railway template is maintained by a community publisher, rather than CERN support. It pins the current reviewed 3.3.14 image. Older third-party images need separate patch verification: upstream 3.3.14 fixes the offline-copy path traversal advisory. Meetings, attachments and agendas are distinct from a full board-governance suite.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ThiefMaster, pferreir, OmeGak, 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/indico/indico/graphs/contributors

- Upstream project: https://github.com/indico/indico

### Sources

- Railway: https://railway.com/deploy/indico

- Template Repo: https://github.com/aalfath/indico-railway-template

- Dockerfile (`3.3.14`): https://raw.githubusercontent.com/aalfath/indico-railway-template/main/Dockerfile

- MIT: https://raw.githubusercontent.com/indico/indico/master/LICENSE

- Releases (`v3.3.14`): https://github.com/indico/indico/releases

- v3.3.14 Changelog: https://raw.githubusercontent.com/indico/indico/v3.3.14/CHANGES.rst

- Indico offline-copy path traversal: https://github.com/indico/indico/security/advisories/GHSA-h57f-c9j4-577x

### Licensing sources

- https://raw.githubusercontent.com/indico/indico/master/LICENSE

### Infrastructure sources

- https://railway.com/deploy/indico


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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. Indico uses Flask-Multipass authentication/identity providers, with documented SAML and Shibboleth configurations and extensible providers. Configure the actual provider and identity/group mapping; LDAP directory authentication alone is not labelled federated SSO. Scope: Indico 3.3 stable production authentication; provider-specific configuration required. Source: https://docs.getindico.io/en/stable/config/auth/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Official production guides install Indico, Celery, Redis and PostgreSQL on supported Debian/Ubuntu or Alma/Rocky systems. The nginx guide directs Shibboleth SSO deployments to Apache; configure the chosen web/authentication stack rather than treat all recipes as interchangeable. This is a single-machine installation procedure, not a cloud HA template. Scope: Indico 3.3 stable production installation; Apache is required for the documented Shibboleth integration. Source: https://docs.getindico.io/en/stable/installation/production/deb/nginx/ (reviewed 2026-11-20). Deployment artifact: https://docs.getindico.io/en/stable/installation/production/deb/nginx/. Artifact reference: Stable 3.3 guide; match supported package versions and web/authentication configuration. Supporting source: Production Apache alternative — https://docs.getindico.io/en/stable/installation/production/deb/apache/.

- Minimum footprint / sizing: Sources checked — unresolved. The full production instructions describe Indico/Celery/Redis/PostgreSQL and worker/reload settings but do not establish a complete CPU/RAM/storage floor or 100-user/1-TB HA capacity. Worker RSS thresholds are not host sizing. Confirm attachment storage, background jobs and concurrency. Scope: Production install and process settings; quantitative workload/HA sizing remains open. Source: https://docs.getindico.io/en/stable/installation/production/deb/nginx/ (reviewed 2026-11-20). Supporting source: Production Apache installation settings — https://docs.getindico.io/en/stable/installation/production/deb/apache/.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v3.3.14 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Indico (CERN) upstream application; verify compatibility with the selected package. Source: https://github.com/indico/indico/releases/tag/v3.3.14 (reviewed 2026-11-19).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Indico offline-copy path traversal (security-advisory): The upstream advisory identifies local file disclosure in offline-copy generation. Scope: Indico <3.3.14; fixed in 3.3.14 (GHSA-h57f-c9j4-577x / CVE-2026-107398). Conditions: Exposure depends on the ability to generate the affected offline copy; verify the exact upstream advisory. Action: Use Indico 3.3.14 or a later compatible fixed version; an older Azure image is not covered by the Railway template’s version pin. Source: https://github.com/indico/indico/security/advisories/GHSA-h57f-c9j4-577x; reviewed 2026-11-19.




## Minute (i.AI)

Open-source meeting transcription and minute generation developed for public-sector use.

- Listing: https://launchinyourcloud.com/directory/minute-iai/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform
- Architecture: AWS ECS application and worker services, database, SQS, storage and separately configured speech and language-model services.
- 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://github.com/i-dot-ai/minute
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The project is explicitly in incubation. Government and council reports establish pilot use; the public Terraform depends on environment, identity and shared-platform resources that an adopting organization must supply. Azure Speech and language-model calls can send recording or transcript data outside the AWS application boundary. Human review remains necessary for formal minutes.

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

AWS ECS application and worker services, database, SQS, storage and separately configured speech and language-model services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- board-committee-governance: Open-source meeting transcription and minute generation developed for public-sector use.

- ai-tools: Open-source meeting transcription and minute generation developed for public-sector use.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/i-dot-ai/minute/main/terraform/ecs.tf (checked 2026-11-19). 


### Cloud deployment evidence

- Terraform ECS (aws): https://raw.githubusercontent.com/i-dot-ai/minute/main/terraform/ecs.tf
  AWS ECS application and worker services, database, SQS, storage and separately configured speech and language-model services. The project is explicitly in incubation. Government and council reports establish pilot use; the public Terraform depends on environment, identity and shared-platform resources that an adopting organization must supply. Azure Speech and language-model calls can send recording or transcript data outside the AWS application boundary. Human review remains necessary for formal minutes.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The institutional source identifies actual use, public governance or a named community-support program. The linked application source separately establishes installation and licensing.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://knowledgehub.dev.ai.gov.uk/tools/minute

- Upstream project: https://github.com/i-dot-ai/minute

### Sources

- Terraform ECS: https://raw.githubusercontent.com/i-dot-ai/minute/main/terraform/ecs.tf

- Repo (Incubation Notice): https://github.com/i-dot-ai/minute

- MIT: https://raw.githubusercontent.com/i-dot-ai/minute/main/LICENSE

- Commits: https://github.com/i-dot-ai/minute/commits/main

### Licensing sources

- https://raw.githubusercontent.com/i-dot-ai/minute/main/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/i-dot-ai/minute/main/terraform/ecs.tf


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 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: Sources checked — unresolved. The ECS recipe injects an AUTH_API_URL from shared infrastructure. The public application and Terraform references reviewed do not establish a complete supported SAML/OIDC federation setup for an independent adopter. Obtain the authentication-service configuration, identity-provider compatibility and access lifecycle; a service URL is not proof of corporate SSO. Scope: Incubating project with separate shared authentication service; federation unresolved. Source: https://raw.githubusercontent.com/i-dot-ai/minute/main/terraform/ecs.tf (reviewed 2026-11-20). Supporting source: Project scope and external infrastructure runbooks — https://raw.githubusercontent.com/i-dot-ai/minute/main/README.md.

- 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 AWS ECS application and worker services, database, SQS, storage and separately configured speech and language-model services. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Minute (i.AI) deployment example; review the full linked installation instructions. Source: https://raw.githubusercontent.com/i-dot-ai/minute/main/terraform/ecs.tf (reviewed 2026-11-19). Deployment artifact: https://raw.githubusercontent.com/i-dot-ai/minute/main/terraform/ecs.tf. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The public ECS recipe configures its backend task at 4 vCPUs/8 GiB in the production workspace and 2 vCPUs/4 GiB elsewhere. Frontend, processing services, database, shared infrastructure and speech/model services add resources. These are project defaults for an incubating system, not tested capacity for another organization or HA design. Scope: Upstream ECS backend-task example; remaining application and model services excluded. Source: https://raw.githubusercontent.com/i-dot-ai/minute/main/terraform/ecs.tf (reviewed 2026-11-20).

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Minute (i.AI); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/i-dot-ai/minute/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## OpenSlides

Self-hosted assembly governance for agendas, motions, elections and meeting participation.

- Listing: https://launchinyourcloud.com/directory/openslides/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT open-source license
- Licensing model: open-source
- Installation: Official osmanage utility and Docker Compose
- Architecture: Customer-operated meeting, authentication and voting services
- Operations: Customer operates containers, application data, HTTPS, backups and upgrades.
- Product website: https://openslides.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The official project documents assembly management and a Docker Compose installation. This is a narrower meeting/decision workflow alternative rather than a complete board governance document system. No specific hyperscaler deployment was verified.

The listed self-hosted OpenSlides project is distributed under the MIT license. Hosting/support offerings are separate from the source-code license.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- board-committee-governance: Adjacent formal meeting and assembly governance for agendas, motions, elections and participation. Not a complete board-records retention or board-pack compliance suite. Assess the particular board process and records requirements.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/openslides (checked 2026-11-12). 


### Cloud deployment evidence

- OpenSlides 4.3 community deployment on Railway (railway): https://railway.com/deploy/openslides
  The community template documents the OpenSlides 4.3 service architecture, including proxy, client, backend roles, authentication, voting, media, realtime components, PostgreSQL and Redis. Adapters provide generated secret files for Railway. Verify every image is pinned to a mutually compatible release and review backups, public endpoints and voting/meeting requirements; this is not vendor-managed hosting.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official functions and license: https://github.com/OpenSlides/OpenSlides

- Official self-hosted installation: https://github.com/OpenSlides/OpenSlides/blob/main/INSTALL.md

### Licensing sources

- https://github.com/OpenSlides/OpenSlides

### Infrastructure sources

- https://github.com/OpenSlides/OpenSlides/blob/main/INSTALL.md


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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. OpenSlides documents SAML SSO through its authentication service, including provider metadata, certificates and user attributes. Configure the identity provider, account mapping and role/meeting assignment for a compatible service release; this is application-user login rather than only internal service tokens. Scope: OpenSlides 4 SAML authentication service; release-specific setup. Source: https://github.com/OpenSlides/OpenSlides/wiki/SSO (reviewed 2026-11-21). Supporting source: Authentication-service documentation — https://github.com/OpenSlides/openslides-auth-service/blob/main/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream installation instructions use the manage tool to generate Docker Compose deployment files. Configure hostname, secrets, persistence and the matching OpenSlides service versions; review breaking-change instructions before upgrading. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/OpenSlides/OpenSlides/blob/main/INSTALL.md (reviewed 2026-11-14). Deployment artifact: https://github.com/OpenSlides/OpenSlides. Artifact reference: main installation instructions (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The versioned installation manual explains the generated multi-service Compose stack, database, secrets and updates but does not provide numeric production host CPU/RAM/storage requirements. Size simultaneous participants, voting/projectors, database and operational replicas rather than treating a working development stack as capacity evidence. Scope: OpenSlides 4.3.7 production sizing remains unconfirmed. Source: https://github.com/OpenSlides/OpenSlides/blob/4.3.7/INSTALL.md (reviewed 2026-11-21).

- License pricing: Documented. The OpenSlides 4.3.7 repository is MIT licensed. Component/dependency licences and paid hosting, assistance and maintenance agreements remain separate; source availability does not include commercial operational services. Scope: Versioned OpenSlides repository licence. Source: https://github.com/OpenSlides/OpenSlides/blob/4.3.7/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 4.3.7, published 2026-11-03. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream OpenSlides/OpenSlides release record; commercial editions and deployment packages may differ. Source: https://github.com/OpenSlides/OpenSlides/releases/tag/4.3.7 (reviewed 2026-11-14).






