Documentation Index
Fetch the complete documentation index at: https://docs.expanse.sh/llms.txt
Use this file to discover all available pages before exploring further.
Expanse authenticates users with a personal API key, issued through your organisation’s SSO. There is one credential you ever hold; everything else is minted automatically during compute registration.
Sign in
The CLI walks you through your organisation’s SSO flow and stores the resulting key locally. Confirm it worked:
Personal API key
Your personal exp_user_ key is scoped to the teams and computes you can access. It is what signs every CLI command and every Console session.
If you suspect a key is compromised, revoke it from console.expanse.sh/settings and sign in again.
Compute credentials
When a compute is registered, the daemon receives its own credential automatically. You never handle it directly. If you need to rotate a compute credential, do it from the per-compute page in the Console.
Privacy-aware deployments
Expanse is deployed exclusively as a privacy-aware enterprise install: the data plane and intelligence plane run inside your own infrastructure, so workload telemetry, source bundles, and intelligence reasoning stay on your network. Only identity (SSO, organisation membership, licence validation) goes through the control plane.
SSO ties into your existing IdP (Okta, Entra, Google Workspace, or any OIDC-compatible provider).
Reach out for a deployment walkthrough.
