Secrets in memory, never in prompts.
Keys and tokens live in Vault and reach a sandbox, workspace or build host in memory, for as long as the run lasts.
Vault
Keys and tokens live in Vault and reach a sandbox, workspace or build host in memory, for as long as the run lasts.
SecretIssued toEndsNow
STRIPE_TEST_KEYsbx_9a14end of runIn memory
DB_TEST_URLlease_7f2cend of leaseRevoked 10:32
NPM_TOKENacme-apiend of sessionIn memory
- Where it lives
- In memory inside the run
- Lifetime
- Ends with the run, session or lease
- Prompts
- Kept out of what agents send to models
- Audit
- Every injection recorded
How it works
What happens, in order.
01Store
Put a secret in Vault once, not in repos, prompts or environment files.
02Inject
It reaches the run in memory, never written to disk.
03End
It stops working when the run, session or lease ends.
Which plans
Vault comes with Pro and up.
See pricing →Give every agent
a box of its own
Start free with 100 vCPU-hours a month. Upgrade when your agents need more.
A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI