Fly.io

Connect Fly.io to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Fly.io:

   1. With flyctl signed in to the organization, run fly tokens create readonly --name "Safeguard" --expiry <duration> and copy the token it prints.
   2. Or, in the Fly.io dashboard, choose the organization from the dropdown, then click Tokens to create and manage org tokens.

   Where to find the other values:

   • Organization: The organization's name/slug as shown in the dashboard's organization dropdown.

   Fly.io's public documentation does not cover every step.

   The read-only org token comes from the flyctl command; the docs did not confirm that the dashboard Tokens page offers a read-only type, nor whether a token is shown only once. If you belong to several orgs, make sure the command targets the right one (the org flag was not covered on the fetched page).

   Source: docs.fly.io, checked 2026-10-07.

   The permissions Safeguard needs: fly tokens create readonly.

2. On Compliance › Connectors, open Fly.io, click Connect, choose API token and fill in:

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.
   Organization	Required.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Fly.io and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Cloud Infrastructure connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks