Fly.io integration: connect apps, machines and volumes to Polylane
Connect Fly.io apps, machines and volumes to Polylane with an API token. Investigate release failures using machine logs and infrastructure context.
Get started for freeHow to set up Fly.io
Token validation precedes registration. A measured setup duration is not available.
- Create a read-only API token in Fly.io Dashboard → Tokens, as recommended by the product connection guide.
- Choose Fly.io in Polylane and paste the token. The form validates it before enabling Connect.
- Open the connected account to inspect apps, machines and volumes. Request a manual Sync if a recent change is missing.
Permissions and access
The recommended token type is Read-only. Deploy tokens grant deployment access and personal tokens grant full account access; neither is needed for inventory discovery. The console accepts a token without a separate access-mode selector. The exact minimum per-endpoint Fly capability set is not declared in the connection form, so use the provider’s read-only token rather than a broad personal token.
Discovery, refresh and the connected view
A scheduled inventory pass runs every 15 minutes. The graph contains Fly apps, machines, volumes, certificates and secret metadata. Investigations can read releases, machine metrics and logs, then relate a failed release to the machines and attached volumes involved. Secret values are not needed for the map.
Disconnect and revoke access
Disconnect the account in Polylane to cancel its scheduled syncing. Revoke the API token in Fly.io Dashboard → Tokens to remove provider access as well.
Provider credentials and Polylane’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
In the graph.
Every Fly.io resource Polylane picks up sits in the graph with its connections, config and history.
Fly App Machine Volume Certificate Secret Tools for the investigation.
What Polylane can do with Fly.io while it investigates. Every call is recorded in the transcript.
Fly.io Polylane MCP -
flyApiCall any Fly.io Machines REST endpoint that lacks a dedicated tool -
flyListReleasesList release history for a Fly.io app -
flyQueryMetricsQuery Fly.io Prometheus metrics for an app -
flyGetLogsGet logs for a Fly.io app via Prometheus metrics
Fly.io setup and troubleshooting
EBUSY: volume unmount failures
Docker context deadline exceeded
Common questions.
How does Polylane connect to my Fly.io account?
Create a read-only API token in Fly.io Dashboard → Tokens, as recommended by the product connection guide. Choose Fly.io in Polylane and paste the token. The form validates it before enabling Connect. Open the connected account to inspect apps, machines and volumes. Request a manual Sync if a recent change is missing.
What Fly.io resources does Polylane sync?
A scheduled inventory pass runs every 15 minutes. The graph contains Fly apps, machines, volumes, certificates and secret metadata. Investigations can read releases, machine metrics and logs, then relate a failed release to the machines and attached volumes involved. Secret values are not needed for the map.