Deploy anywhere, with keys the agent keeps for you
Paste a deploy token in the prompt bar and the agent keeps it private; deploys to Vercel, Cloudflare, AWS, Kubernetes and 24 more use it unseen.
Versions, Checks, Deployments now offers 28 ready platforms, the ones that fit your folder first: Vercel, Netlify, Cloudflare, Fly, Render, Railway, AWS (CDK, SAM, Serverless, S3), Google Cloud Run, App Engine, Firebase, Azure, DigitalOcean, Docker, Apple container, Compose, Kubernetes, Helm, your own server, Deno, Supabase, Expo, and package registries. Add one and it joins your checks file beside what is there.
Each deployment lists the keys it needs and whether each is saved. Paste a line like VERCEL_TOKEN=… in the prompt bar and ask the agent to keep it: the token is swapped out before the model sees it and saved in your keychain under that name. You can also add, replace or forget a key from the window, for this project or for every project.
When a deployment runs, its keys reach the command only as settings, and a file key such as a cluster config arrives as a private copy that is deleted afterwards. Anything the command prints that looks like a key is masked in the log.
A deployment stops before sending anything when a key is missing or a program it needs is not installed, and says which. With a page to check, Bandicot asks it for up to a minute after the command finishes and marks the deployment failed if it never answers.
Agents can list platforms, keep keys, deploy a green commit and read past deployments with the same Versions tool.