Choose the right starting configuration. Scope, deployment, integrations and AI usage are aligned transparently to your architecture.
Private and on-premise deployment, implementation and integrations are scoped individually.
For initial governed AI infrastructures.
For multiple models, data sources and agents.
For complex governance and identity requirements.
For special data sovereignty and infrastructure requirements.
Final configuration depends on your security, integration and operational requirements.
| Capability | Control | Business | Enterprise | Sovereign |
|---|---|---|---|---|
| Approved models | ✓ | ✓ | ✓ | ✓ |
| Policy Engine | Core | Advanced | Advanced | Advanced |
| Agent Governance | — | ✓ | ✓ | ✓ |
| Knowledge Gateway | — | ✓ | ✓ | ✓ |
| AI Inventory | — | Optional | ✓ | ✓ |
| Private Deployment | — | — | Optional | ✓ |
| Enterprise IAM | — | Optional | ✓ | ✓ |
The key points on scope, operations and starting.
No. Model usage is calculated separately based on provider and deployment.
Yes. The platform is designed as a control layer for existing models, data sources and applications.
Yes, within the Sovereign scope and after a technical architecture assessment.
With an architecture assessment, a prioritised use case and definition of the required policies.
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.