CapabilitiesKeys and secrets
Stored secrets
Save API keys with the provider and have them appear in the machine as environment variables.
Who offers it
Part of Keys and secrets, which explains why it matters.
Fully: Agent 37, Blaxel, Boat, boxd, Daytona, E2B, InstaBox, Lizard, Modal, Morph, Runtime and Sandboxer. With a catch: Cloudflare Sandbox and Vercel Sandbox. Not at all: Tensorlake.
Values are saved with the machine and appear in its environment, where the agent can read them.
docs-confirmed “Anything in an instance's environment, the agent can read and repeat back.” Source
Values are saved in the workspace and injected when a machine starts.
docs-confirmed “Configure environment variables and secrets in Blaxel sandboxes” Source
Secrets are saved per environment and injected at start as variables or files.
docs-confirmed “boat injects two types of secret when a sandbox starts.” Source
A value is saved once for the organisation and injected into every machine in its scope.
docs-confirmed “Set an environment variable or a secret once for your organization” Source
Values are saved with the account and substituted by the provider, so the machine holds only a stand-in.
docs-confirmed “Secrets are a secure way to store and use sensitive values such as API keys, tokens, and passwords across your Daytona sandboxes” Source
Values are saved per project and appear in the machine as environment variables.
docs-confirmed “Secrets let you store credentials such as API keys with E2B and reference them by name.” Source
Values are saved for the organisation and delivered either as a stand-in or as a real environment variable.
docs-confirmed “Inside the sandbox: any process there can read and copy it.” Source
Values are passed when the machine is created and reach every command.
docs-confirmed “Create-time `envs` reach every command.” Source
Values are saved with the app and delivered to the machine as environment variables.
docs-confirmed “You can set environment variables using inline secrets” Source
A template carries a secrets manager, and agent tokens can be limited to reading or writing them.
docs-confirmed “Every devbox is created from a template that integrates with our secrets manager” Source
A key is saved once with the hosts it may be used for, and machines never hold the value.
docs-confirmed “Store an API key once. Your sandboxes use it without holding it.” Source
An environment bundles variables and secret files that are written into the machine.
docs-confirmed “Variables — a `.env`-style list, exported to every process in the sandbox.” Source
The catch: There is no saved secret inside the machine; you keep the value in your own small program and add it on the way out.
docs-confirmed “Once a value is in the sandbox, all the code there can read it and send it anywhere the sandbox can reach.” Source
The catch: There is no saved list of secrets for a sandbox; you pass the values each time you create or run one.
docs-confirmed “Run with environment variables” Source
Note: There is no saved secret: you pass the value with each command or session.
inferred “Set per-command and per-PTY environment variables in the CLI, Python, and TypeScript.” Source
- SpritesNot published
No saved secret store for a Sprite is documented; credentials are handled through its connector catalogue.
inferred “Connectors solve this by storing the credential once, in your organization” Source
Related
Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.