GitDoctorruntime, not static

Integrations / Fly.io

Fly.io

Scheduled machines across your apps.

Why connect it

Fly runs scheduled work as machines with a schedule (hourly, daily, weekly, monthly). The Machines API lists them with their last state.

What you'll see

  • Every app's scheduled machines with schedule and state
  • Failed machines flagged
  • No run ledger: the page says so

What the credential can and cannot do

Where to get it: fly.io → Account → Access Tokens (a read-only org token if available). `fly tokens create readonly` works too.

It grants: Read on apps and machines.

It cannot: GitDoctor never starts, stops, or destroys machines.

Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.

Connect