One command
Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results.
stack add fly
Or retrieve catalog matches for what you're building via stack recommend:
stack recommend "host a Next.js frontend"Auth flow
Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed.
How-to: Paste an API token from https://fly.io/user/personal_access_tokens.
Secret slots
stack add fly has these 1 catalog secret
slot; verify which values its adapter actually materializes through Phantom:
FLY_API_TOKEN
Use stack env export --example for an empty-key skeleton.
Stack does not automatically fill env files or resolve credential placeholders.
stack exec -- <cmd> forwards to installed Phantom exec;
configure and verify the app separately.
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?
Use an existing Fly.io account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed. If you don't have a credential yet, create one at https://fly.io/dashboard and supply the required inputs; inspect verification and persistence results.
Where does Stack store my Fly.io credentials?
Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (FLY_API_TOKEN); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.
Can I rotate or revoke this integration later?
Use `stack remove fly` for local Fly.io configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Fly.io credentials through https://fly.io/dashboard, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.