Optional managed deployment
A dedicated Sanctum-managed environment for organizations that want Sanctum Lex without provisioning the underlying infrastructure themselves. Sanctum Lex remains single tenant whether it runs in your environment or on Sanctum Cloud.
Deployment choice
Some firms want Sanctum Lex entirely inside infrastructure they already operate. Others want a dedicated environment without adding another infrastructure workload to their internal team. Sanctum Cloud is the optional managed path for the second case.
For firms that want the infrastructure boundary to remain entirely inside their own cloud, VPC or private environment. Sanctum Lex is deployed as a dedicated single-tenant system under the client-approved network and identity boundary.
For firms that want the same isolated Sanctum Lex deployment without taking on the underlying infrastructure work. Sanctum provisions and operates the dedicated environment under an agreed deployment, security and support model.
The console exposes the deployment boundary as an operating environment rather than hiding it behind a generic SaaS account.
Tenant architecture
Dedicated single tenant
Infrastructure operator
Sanctum managed
Deployment region
Agreed with the client
Identity
Client enterprise identity
Data boundary
Dedicated environment
Model routes
Client-approved policy
Audit
Environment-level controls
Support
Managed deployment lifecycle
The signed deployment record remains the source of truth for the exact infrastructure, region, model routes, encryption, access and support controls active for a client environment.
What Sanctum Cloud means
The legal workspace, governance model and matter controls remain Sanctum Lex. Sanctum Cloud simply gives firms another way to operate the underlying environment.
Sanctum Cloud does not create a second legal AI product. It is an optional infrastructure path for running Sanctum Lex.
Choosing Sanctum Cloud changes who provisions and operates the infrastructure, not the isolation model of Sanctum Lex Enterprise.
Firms that prefer their own infrastructure can continue to deploy Sanctum Lex inside their existing environment and security boundary.
Region, model access, key management, egress and operational controls are documented for the environment actually approved by the client.
Sanctum Lex can be reviewed for deployment inside client-controlled infrastructure. Sanctum Cloud is available as an optional managed deployment path where appropriate.