Own Your Agents · 02.07
Ambients: Local, Dev, Staging, Prod, and Fleet
How one Agentis install runs multiple environments, each with its own separate secrets vault.
One workspace, several environments
An ambient scopes a slice of a workspace to a specific environment — local, dev, staging, prod, fleet, or a custom name you choose. Agents, gateways, and credentials can all be bound to a particular ambient, so the same workspace can hold a "staging" version of an automation and a "prod" version side by side without them sharing secrets or colliding on state.
Why this matters in practice
Without ambients, testing a change to a production automation means either risking the real credentials and real channels, or standing up an entirely separate Agentis install just to get isolation. With ambients, an agent commissioned against the staging ambient uses staging credentials and staging channel connections by construction — there's no shared vault to accidentally leak a prod secret into a test run.
GET /v1/ambients
Authorization: Bearer $AGENTIS_API_KEYContinue
Encrypted, portable exports of an entire workspace — share it, sell it, or back it up. The profile is the secrets boundary.
SQLite online backup with manifest-versioned snapshots — how Agentis protects durable state against loss.