Software on Fly.io
Software with a documented deployment path in a customer environment on Fly.io.
4 listings, including 4 from other publishers. Search and filter Fly.io listings →
Read this page as JSON or Markdown.
Each listing needs its own deployment evidence. A cloud badge identifies a documented option, not a certification or an exclusive list of compatible providers. FormKiQ listings carry a Directory Publisher disclosure.
Customer-account guidance
- Account boundary
- Fly.io organization and app; platform-managed Machines
- Network
- App networking and explicitly published services
- Identity & access
- Organization/app access, deployment tokens and secrets
- Deployment tooling
- Use flyctl and fly.toml to deploy the application and database; configure regions, volumes, secrets and recovery.
Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Provider boundary source ↗ · Checked 2026-11-20
Official provider guidance ↗ · Source reviewed 2026-11-12. Check region, service availability, backup destinations and support access for your deployment.
Deployment and procurement checks
- 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. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Browse by category
5 categories on Fly.io. Counts show matching listings; a listing can appear in more than one category.
Business operations3 categories
Data & analytics1 category
Developer platforms & operations1 category
No categories match your search.
Documented software
Deployment evidence and qualifications
Open-source business operations platform for people, projects, time and financial records.
- Fly.io Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
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.
Scope: The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Fly.io Guide ↗
Deployment evidence and qualifications
Open-source verifiable election software for organizational and committee voting.
- Fly Config ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Helios web service, PostgreSQL, election state and configured authentication using upstream Fly or Heroku artifacts. The upstream Fly migration guide requires an election-free window, preservation of secrets and the existing public URL, and a rollback plan. The deployment artifacts do not certify election suitability or remove the need to validate the organization's election process.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
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.
Scope: 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.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Fly Config ↗
Deployment evidence and qualifications
Self-hosted website and event analytics application with dashboards and PostgreSQL storage.
- Umami self-hosted deployment on Fly.io ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages tracking endpoints, database, admin credentials, retention, TLS, backups and upgrades.
Scope: 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.
License: MIT License for upstream Umami.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Umami self-hosted deployment on Fly.io ↗
Deployment evidence and qualifications
Run scripts and workflows with customer-operated execution workers and an app builder.
- Windmill upstream self-hosting provider compatibility ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.
Scope: 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.
License: AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Windmill upstream self-hosting provider compatibility ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings