# Pagerless for Fly.io

> Woken only when it matters, and one tap undoes a bad deploy: Pagerless moves Machines back to the previous image.

URL: https://pagerless.dev/integrations/fly-io
Updated: 2026-10-22

## Set up

Node, Go or Python SDK. `FLY_APP_NAME` and `FLY_IMAGE_REF` are read automatically.

Store the key with `fly secrets set PAGERLESS_KEY=pl_live_...`. Or run `npx pagerless connect` and it finds your services and places the key for you.

## Fixes on Fly.io

| Fix | On Fly.io |
| --- | --- |
| Undo the update | Moves Machines back to the previous image |
| Restart | Restarts Machines |
| Add capacity | Clones or stops Machines |
| Deploy events | From the SDK's deploy marker |
| Access it needs | a Fly deploy token |

## Questions

### Can Pagerless roll back Fly.io automatically?

Yes, if your rules set undo to alone. By default it asks first, and approving an undo needs your passkey (Face ID or Touch ID). It then moves Machines back to the previous image.

### Does Pagerless need admin access to Fly.io?

It needs a Fly deploy token. It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.