Vault
Published Updated
What is Vault?
The Vault is Orbit’s local, encrypted store for API keys and secrets. Keys are encrypted with AES-256-GCM, never sent to Sivants, and can be scoped globally or to one project.
Encrypted local storage for API keys and secrets. Keys are AES-256-GCM encrypted, never sent to Sivants servers, and available across all your projects.
The Vault is project-agnostic — keys added once are available everywhere in Orbit. Each key has a name (what Orbit calls it internally) and a value (the actual secret). Keys are encrypted on write and never leave your machine. BYOK keys bypass the Sivants Credits system entirely for that provider — Orbit calls the provider directly using your key.
How it relates to Orbit
Orbit stores provider secrets in its encrypted Vault and supplies them to connected services when needed. See Vault & Secrets for details.
When you would use it
You set up the Vault during initial Orbit configuration, then add keys as needed for new services.
Common operations
- Adding API keys for providers (Anthropic, Google, fal.ai, etc.)
- Storing service tokens (Vercel, Railway, Stripe)
- Reviewing what's stored
Frequently asked questions
Can coding agents read my Vault?
Agents routed through Orbit’s API executor are blocked from vault tools, and secrets are supplied to connected services only where they are needed. See The Vault.
How do I add a key to the Vault?
Add it from the Vault panel, choose its scope, and reveal or back it up later when needed. See Store Secrets in the Vault.