CODE S applies data-classification and sovereignty policies server-side to approved workflows. Specific providers, regions and deployment models require separate review and approval.
Public, internal, confidential and restricted determine which routes, tools and external connections a workflow may use.
Separately approved external model routes may be permitted.
Only model routes and tools approved for the workspace.
External models, web access and connectors are limited by policy.
Only separately reviewed private routes and local work contexts.
The mode limits routes and capabilities. It does not replace technical, data protection or contractual provider approval.
General workspace policy for routes approved for use.
Additional limits on regions and external processing.
Strict limits on model routes, tools and data egress.
Policy mode for separately approved private routes and local workspaces.
European cloud, private cloud, customer VPC, hybrid, and on-premises deployments are potential target architectures. A deployment option is considered available only after the target architecture has been defined and the security review, operational approval, and customer acceptance are complete.
Potential target architecture with defined European regions.
After approvalPotential dedicated target architecture with controlled access.
After approvalPotential integration into a controlled customer environment.
After approvalPotential target architecture for particularly critical data.
After approvalA deployment model is described as available only after architecture, security, and operational approvals have been granted.
Policy defines the permitted boundaries. The actual infrastructure follows only after documented approval.