Your directory decides who gets in.
Sign in with SAML or OpenID Connect through Microsoft Entra ID, Okta, Google Workspace or any standard identity provider, and keep members in step with your directory over SCIM.
SSO and SCIM
Sign in with SAML or OpenID Connect through Microsoft Entra ID, Okta, Google Workspace or any standard identity provider, and keep members in step with your directory over SCIM.
MemberRoleSign-inProvisioned
maya@acme.devAdminOktaSCIM
lee@acme.devApproverOktaSCIM
jo@acme.devMemberOktaRemoved 09:14
- Providers
- Entra ID, Okta, Google Workspace, any SAML or OIDC provider
- Also
- Passkeys and multi-factor sign-in on every plan
- Removing someone
- Their sessions end when the directory removes them
- Agents
- Act with the signed-in person’s rights
- Audit
- Sign-ins and directory changes recorded
How it works
What happens, in order.
01Connect
Point Sandscale at your identity provider over SAML or OIDC.
02Provision
SCIM adds and removes members as your directory changes.
03Sign agents in
Agents like Claude Code sign in through the same SSO, as the person running them.
Which plans
SSO comes with Team. SCIM, verified domains and custom roles come with Enterprise.
See pricing →Give every agent
a box of its own
Start free with 100 vCPU-hours a month. Upgrade when your agents need more.
A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI