One command
Add Modal 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 modal
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: Create a token in the Modal dashboard and paste it.
Secret slots
stack add modal writes these 1 secret
slot into your Phantom vault:
MODAL_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
- Vercel — Frontend platform. Stores a scoped access token for deploys + env sync.
- Railway — Infra from a repo. Project-level token stored in Phantom.
- Fly.io — VMs at the edge. Machines API 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 Modal account to use it with Stack?
Yes — Stack provisions Modal 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://modal.com and paste it once.
Where does Stack store my Modal credentials?
In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (MODAL_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 modal` to pull the Modal service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Modal credentials in their dashboard — https://modal.com — and Stack's next `doctor --fix` will pick up the new values.