One command
Add Fly.io to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.
stack add fly
Or describe what you're building and let Claude pick it up via stack recommend:
stack recommend "host a Next.js frontend"Auth flow
Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.
How-to: Paste an API token from https://fly.io/user/personal_access_tokens.
Secret slots
stack add fly writes these 1 secret
slot into your Phantom vault:
FLY_API_TOKEN
The values never leave Phantom in plaintext. Your .env file references slot
names, and stack exec -- <cmd> swaps them in at process-spawn time via
Phantom's local proxy.
Related providers in Deploy
- Modal — Serverless compute for AI + data. Token stored in Phantom.
- Vercel — Frontend platform. Stores a scoped access token for deploys + env sync.
- Railway — Infra from a repo. Project-level token stored in Phantom.
- Cloudflare — Workers, R2, D1. Account id inferred from the token's scope.
- Render — Zero-config hosting. API key stored in Phantom.
FAQ
Do I need a Fly.io account to use it with Stack?
Yes — Stack provisions Fly.io on your behalf, but it authenticates as you. Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://fly.io/dashboard and paste it once.
Where does Stack store my Fly.io credentials?
In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (FLY_API_TOKEN) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.
Can I rotate or revoke this integration later?
Yes. Run `stack remove fly` to pull the Fly.io service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Fly.io credentials in their dashboard — https://fly.io/dashboard — and Stack's next `doctor --fix` will pick up the new values.