Public
Approved external enterprise models
Control where data is processed — and by whom
Data sovereignty is not an add-on. It is enforced for every request through data classes, regions, model approvals and deployment rules.
Data sovereignty is not an add-on. It is enforced for every request through data classes, regions, model approvals and deployment rules.
The same organisation can use different infrastructures without losing control over sensitive data.
Approved external enterprise models
Approved models only
Defined EU processing
Private or on-premise only
Define the required sovereignty mode by organisation, domain or use case.
Flexible use of approved global and European models.
European processing and governed model approvals.
Strict European infrastructure and model requirements.
Private cloud, customer VPC or on-premise.
Architecture and operating model are defined by security, privacy, integration and operational responsibility.
Managed European processing regions.
EU residencyDedicated infrastructure with controlled access.
DedicatedDeployment inside your governed cloud perimeter.
Your perimeterMaximum infrastructure control for critical data.
Maximum controlYour processes belong to your company. Your governance remains intact.
Models can be added, replaced or blocked without rebuilding the entire architecture.
Keep your existing models, data and systems. CODE S adds the control layer between them.
Prices are starting prices. Implementation, integrations and usage-based AI costs are calculated separately.