Concepts

Vault

Vault keeps your secrets out of prompts, repositories and logs. A run references a secret, and Vault injects it at run time.

How secrets reach a run

You store a secret once. A sandbox, workspace or build host lease references it, and Vault injects the value when the run starts. Values are never placed in prompts or logs, and sandscale mcp never offers a Vault value to a model.

From the CLI

sandscale vault kv put app/db password=-
sandscale vault kv get app/db --field password --reveal
sandscale vault mounts

put with - reads the value without echoing it. Values are printed only with --reveal, and only to a terminal.

Vault also has policies, leases and encryption with transit. See sandscale vault in the CLI reference.

Build host leases

Secrets issued for a build host lease end with the lease.