Connect Fly.io to Saasmetry
The machines each app runs on, their regions, and the ones that failed to start.
What Saasmetry reads
Refreshed every 15 min. Read-only throughout: Saasmetry never writes to Fly.io.
Create the credential
- Fly.io → Account → Access Tokens → create a token.
- Copy it when it is shown.
- Enter the organization slug (`fly orgs list`), then pick the app each product reads from its data sources.
Worth knowing
- Fly issues no read-only token. A personal access token carries your whole account and a deploy token carries one app; Saasmetry only ever reads with either.
- Machines report their state and region, not their load. Fly's machines list gives what a machine was allocated rather than what it is using, and an allocation shown as a utilisation would draw a full disk on an idle machine.
- A stopped or suspended machine is reported as healthy. Fly's auto-stop makes stopped the normal resting state of a scale-to-zero app, and its own definition cannot tell an intended stop from a crash-exit — point an uptime monitor at anything that must always be up.
Is it safe to paste?
A Fly.io access token can deploy, restart and destroy machines; Fly issues no read-only equivalent. Saasmetry encrypts it and only reads your app list and the state of their machines.
Fly.io issues no read-only key, so this credential is broader than Saasmetry needs. Saasmetry only ever reads — but you should know that before you paste it, rather than after.
Also worth connecting
Connect Fly.io in about a minute
Free plan, no card: one product and two integrations.
Start free