
# Software on Fly.io

Explore software with documented Fly.io deployment, customer-account guidance, licensing qualifications and source evidence.

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

4 listings.


## Ever Gauzy

Open-source business operations platform for people, projects, time and financial records.

- Listing: https://launchinyourcloud.com/directory/ever-gauzy/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku, fly, railway, render
- 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: Application platform deployment
- Architecture: Ever Gauzy application/API, database and required workers using provider-specific deployment recipes.
- 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://gauzy.co
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.

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

Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Open-source business operations platform for people, projects, time and financial records.

- hr-employee-records-management: Open-source business operations platform for people, projects, time and financial records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/azure-deployment/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/gcp-deployment/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/ (checked 2026-11-19). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/heroku-deployment/ (checked 2026-11-19). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/flyio-deployment/ (checked 2026-11-19). 

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

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/render-deployment/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Guide (aws): https://docs.gauzy.co/deployment/cloud/aws-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.gauzy.co/deployment/cloud/azure-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Guide (gcp): https://docs.gauzy.co/deployment/cloud/gcp-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Guide (digitalocean): https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Heroku Guide (heroku): https://docs.gauzy.co/deployment/cloud/heroku-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Fly.io Guide (fly): https://docs.gauzy.co/deployment/cloud/flyio-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/ever-gauzy
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.

- Render Guide (render): https://docs.gauzy.co/deployment/cloud/render-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes evereq, rahul-rocket, adkif, 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/ever-co/ever-gauzy/graphs/contributors

- Upstream project: https://github.com/ever-co/ever-gauzy

### Sources

- AWS Guide: https://docs.gauzy.co/deployment/cloud/aws-deployment/

- Azure Guide: https://docs.gauzy.co/deployment/cloud/azure-deployment/

- GCP Guide: https://docs.gauzy.co/deployment/cloud/gcp-deployment/

- DO Guide: https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/

- Heroku Guide: https://docs.gauzy.co/deployment/cloud/heroku-deployment/

- Fly.io Guide: https://docs.gauzy.co/deployment/cloud/flyio-deployment/

- Railway: https://railway.com/deploy/ever-gauzy

- Render Guide: https://docs.gauzy.co/deployment/cloud/render-deployment/

- AGPL-3.0 LICENSE: https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE

- Releases v111.250.0: https://github.com/ever-co/ever-gauzy/releases

### Licensing sources

- https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE

### Infrastructure sources

- https://docs.gauzy.co/deployment/cloud/aws-deployment/

- https://docs.gauzy.co/deployment/cloud/azure-deployment/

- https://docs.gauzy.co/deployment/cloud/gcp-deployment/

- https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/

- https://docs.gauzy.co/deployment/cloud/heroku-deployment/

- https://docs.gauzy.co/deployment/cloud/flyio-deployment/

- https://railway.com/deploy/ever-gauzy

- https://docs.gauzy.co/deployment/cloud/render-deployment/


### 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 vendor documents application-user OAuth login with Google, GitHub, Facebook, Twitter, LinkedIn and Microsoft, including registered clients and instance callback settings. Provider login and the application JWT session/API mechanism are distinct configuration layers. Scope: Upstream application-user social OAuth configuration; not proof of arbitrary enterprise SAML or SCIM support. Source: https://docs.gauzy.co/authentication/social-auth/ (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. The official AWS guide provides service architecture, CLI provisioning and ECS task configuration for the application, PostgreSQL, Redis and S3. Configure images, task resources, secrets, networking and persistence for production; the illustrative commands are not a supplied complete CloudFormation stack. Scope: Vendor-documented customer AWS deployment recipe; complete production configuration and version alignment require review. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The AWS guide illustrates two Fargate tasks at 1 vCPU/2 GB each, a db.t3.medium database with a 50-GB provisioning example and cache.t3.micro Redis. These are example service sizes from the guide, with file storage and load balancing additional; its advertised cost table is not a reference-workload quote. Scope: Published AWS example allocations, not a 100-user/1-TB HA minimum or current operating-cost estimate. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (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: Ever Gauzy; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE (reviewed 2026-11-19).

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







## Umami

Self-hosted website and event analytics application with dashboards and PostgreSQL storage.

- Listing: https://launchinyourcloud.com/directory/umami/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean, fly, heroku, northflank, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for upstream Umami.
- Licensing model: open-source
- Installation: Build from source, run the official prebuilt container or use its Docker Compose application/PostgreSQL setup.
- Architecture: Customer-operated web analytics service and PostgreSQL database
- Operations: Customer manages tracking endpoints, database, admin credentials, retention, TLS, backups and upgrades.
- Product website: https://umami.is/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Change the documented initial administrator password and configure production secrets. Third-party integrations, tracking destinations and external databases require separate configuration; Umami Cloud is a distinct offering.

MIT License for upstream Umami. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated web analytics service and PostgreSQL database. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- web-analytics: Website and event analytics through a deployed tracking endpoint and analytics application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-digitalocean (checked 2026-11-12). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-fly-io (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-heroku (checked 2026-11-12). 

- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-northflank (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-railway (checked 2026-11-12). 


### Cloud deployment evidence

- Umami self-hosting on a DigitalOcean Droplet (digitalocean): https://docs.umami.is/docs/guides/running-on-digitalocean
  The project documents running the Umami application and PostgreSQL on a customer Droplet with PM2 and Nginx. The guide links older Ubuntu setup examples; use currently supported OS and Node.js versions, configure HTTPS and maintain backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Fly.io (fly): https://docs.umami.is/docs/guides/running-on-fly-io
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Heroku (heroku): https://docs.umami.is/docs/guides/running-on-heroku
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Northflank (northflank): https://docs.umami.is/docs/guides/running-on-northflank
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Railway (railway): https://docs.umami.is/docs/guides/running-on-railway
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Upstream release notes document current runtime/security work and credit multiple named contributors across successive releases.

Reviewed 2026-11-10.

- Maintenance and named release contributors: https://github.com/umami-software/umami/releases

- Public upstream project: https://github.com/umami-software/umami

### Sources

- Official installation and runtime: https://docs.umami.is/docs/install

- Upstream project and capabilities: https://github.com/umami-software/umami

- Current upstream license: https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

- Umami self-hosted deployment on Fly.io: https://docs.umami.is/docs/guides/running-on-fly-io

- Umami self-hosted deployment on Heroku: https://docs.umami.is/docs/guides/running-on-heroku

- Umami self-hosted deployment on Northflank: https://docs.umami.is/docs/guides/running-on-northflank

- Umami self-hosted deployment on Railway: https://docs.umami.is/docs/guides/running-on-railway

### Licensing sources

- https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

### Infrastructure sources

- https://docs.umami.is/docs/install


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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The API documents an SSO token endpoint requiring existing authentication and Redis. This does not establish a generic SAML/OIDC enterprise identity-provider integration or its edition entitlement. Scope: Authenticated token exchange checked; enterprise federation remains unresolved. Source: https://docs.umami.is/docs/api-reference/sso (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official guide documents source builds, application containers and Compose. It explicitly identifies the HelmForge Kubernetes chart as third-party; change the default administrator password and configure the database and secrets. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.umami.is/docs/install (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide requires the application runtime and a PostgreSQL database, but does not give a numeric whole-stack production CPU/RAM/storage minimum. Event volume, retention, query concurrency and HA determine capacity; provider demo allocations are not a 100-user, 1 TB HA sizing guarantee. Scope: Current upstream self-hosted topology; whole-system sizing remains unconfirmed. Source: https://docs.umami.is/docs/install (reviewed 2026-11-20).

- License pricing: Documented. The reviewed v3.5.0 application is MIT-licensed and can be self-hosted without a core software subscription. Retain the required copyright/licence notices; hosting, database, operations and Umami Cloud services are separate costs. Scope: Published self-hosted application terms; not a Cloud plan quote. Source: https://github.com/umami-software/umami/blob/v3.5.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## Windmill Self-Hosted

Run scripts and workflows with customer-operated execution workers and an app builder.

- Listing: https://launchinyourcloud.com/directory/windmill/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, render, hetzner, fly, ubicloud
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits
- Licensing model: open-source
- Installation: Docker Compose or Kubernetes/Helm with PostgreSQL and worker replicas
- Architecture: Customer-operated server, worker processes and PostgreSQL job/state storage
- Operations: Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.
- Product website: https://www.windmill.dev/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry excludes hosted Windmill Cloud. Review current community limits and Enterprise features rather than assuming all features are included. Workflow code can reach external services; worker sandboxing and credentials need explicit configuration. Official self-hosting documentation gives AWS/Azure/GCP guidance. Windmill v1.877.0 prevents workspace members from bypassing the configured AI-model allowlist through direct proxy or completion API calls. Direct configured-key POSTs must now contain JSON with a string model, and existing GitHub App repository resources remain admin-only until an administrator saves them once. Retest API callers and repository-resource access. v1.878.0 is the reviewed current follow-up release.

Official repository licensing combines AGPLv3/Apache-2.0 components with proprietary Enterprise feature code. The broad listing includes both community and commercial editions; current plan limits must be checked separately.

Classified servers for the documented long-lived server/worker containers and PostgreSQL queue/state. Fargate compatibility is managed-container hosting, not a function-only software stack.


Cloud evidence scope: Documented customer-operated deployment guides for AWS, Azure and Google Cloud

### Category fit

- workflow-automation: Code-first scripts, flows, schedules and internal apps with worker execution; enterprise controls and quotas vary.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). 

- ubicloud: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/windmill-labs/windmill (checked 2026-11-12). Source: https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial (checked 2026-11-12). 


### Cloud deployment evidence

- Windmill upstream self-hosting provider compatibility (aws, azure, gcp, digitalocean, render, hetzner, fly, ubicloud): https://github.com/windmill-labs/windmill
  The upstream self-hosting section explicitly names AWS EKS/ECS, Google Cloud, Azure, Ubicloud, Fly.io, Render, Hetzner and DigitalOcean, paired with Docker Compose and Helm installation commands. This is an upstream application-hosting compatibility statement; image licensing and enterprise features are separate. Operate the application in a customer cloud account or managed-platform project as appropriate to the selected provider.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Windmill production deployment on Ubicloud Kubernetes (ubicloud): https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial
  Ubicloud documents customer account setup, PostgreSQL and Kubernetes provisioning, Windmill Helm deployment, application access and TLS configuration. This is a full customer application deployment, not a PostgreSQL connector or GitHub Actions runner integration.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-host architecture, Docker and provider guidance: https://www.windmill.dev/docs/advanced/self_host

- Project capabilities and license files: https://github.com/windmill-labs/windmill

- Self-hosted edition limits: https://www.windmill.dev/pricing

- Licensing and edition terms: https://github.com/windmill-labs/windmill/blob/main/LICENSE

- Windmill production deployment on Ubicloud Kubernetes: https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial

- Windmill v1.878.0 release: https://github.com/windmill-labs/windmill/releases/tag/v1.878.0

- Windmill v1.877.0 policy hardening: https://github.com/windmill-labs/windmill/releases/tag/v1.877.0

- Configured AI-key model enforcement: https://github.com/windmill-labs/windmill/pull/12527

- GitHub App repository approval persistence: https://github.com/windmill-labs/windmill/pull/12524

### Licensing sources

- https://github.com/windmill-labs/windmill/blob/main/LICENSE

- https://www.windmill.dev/pricing

### Infrastructure sources

- https://www.windmill.dev/docs/advanced/self_host


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The self-hosted OAuth/SSO guide documents user login through Google, Microsoft, GitHub and other configured providers, separately from OAuth resource connections. SAML and SCIM are explicitly Enterprise features; identity-group synchronization and custom claim settings also have edition limits. Scope: Instance user login; built-in SSO and Enterprise SAML have different entitlements. Source: https://www.windmill.dev/docs/advanced/setup_oauth (reviewed 2026-11-20). Supporting source: Enterprise SAML and SCIM — https://www.windmill.dev/docs/advanced/saml_and_scim.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. v1.877.0 blocks workspace members from spending configured workspace or instance AI keys on models outside the admin-enabled list. Direct configured-key calls now require JSON with a string model; retest clients. Existing GitHub App repository resources require one administrator save before non-admin access. Scope: Windmill configured AI-key proxy and GitHub App repository-resource authorization. Source: https://github.com/windmill-labs/windmill/pull/12527 (reviewed 2026-11-19). Supporting source: v1.877.0 release — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: Repository approval behavior — https://github.com/windmill-labs/windmill/pull/12524.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose stack includes PostgreSQL and application/worker services. Follow its database-major-version migration notes and choose matching application and dependency releases. Scope: Upstream self-hosted stack; database upgrades require explicit migration planning. Source: https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The self-hosting guide suggests roughly one worker per vCPU with 1–2 GB RAM per worker. PostgreSQL, server, proxy and optional editor services require additional capacity; worker concurrency and job isolation change sizing. Scope: Worker rule of thumb, not a complete host minimum or a 100-user/1-TB HA design. Source: https://www.windmill.dev/docs/advanced/self_host (reviewed 2026-11-20).

- License pricing: Documented. At v1.878.0, compilable non-enterprise source is AGPLv3, with Apache-licensed clients/specifications. Published Community binaries also contain proprietary features with free internal-use rights and restrictions on redistribution, resale and embedding. Enterprise rights require a commercial licence. Scope: Versioned source and distributed-binary terms differ; cloud infrastructure and support are separate. Source: https://github.com/windmill-labs/windmill/blob/v1.878.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Windmill v1.878.0 was published November 19, 2026. The preceding v1.877.0 release tightened configured AI-key model authorization and changed direct API validation, while also requiring administrators to resave existing GitHub App repository resources before non-admin use. Scope: Upstream Windmill self-hosted release. Source: https://github.com/windmill-labs/windmill/releases/tag/v1.878.0 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/windmill-labs/windmill/releases/tag/v1.875.0. Supporting source: v1.877.0 policy changes — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: AI model allowlist enforcement — https://github.com/windmill-labs/windmill/pull/12527. Supporting source: GitHub App repository approvals — https://github.com/windmill-labs/windmill/pull/12524.




### Security and lifecycle reviews

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

- Windmill v1.877.0 configured-AI-key policy hardening (security-advisory): Windmill now rejects direct configured-key calls to provider models outside the administrator-enabled list. Scope: Workspace or instance AI keys and GitHub App repository resources in self-hosted Windmill. Conditions: Workspace members with direct API access could previously spend the configured key on other provider models; direct callers now need JSON with a string model. Action: Upgrade to v1.877.0 or later, retest API clients and have an administrator resave existing GitHub App repository resources. Source: https://github.com/windmill-labs/windmill/pull/12527; reviewed 2026-11-19. Supporting source: v1.877.0 release — https://github.com/windmill-labs/windmill/releases/tag/v1.877.0. Supporting source: Repository approval persistence — https://github.com/windmill-labs/windmill/pull/12524.



