Capabilities and boundaries
Designed for decisions you can explain.
Each capability below describes its operating scope so technical and commercial teams can evaluate the same proposition.
01Govern AI access
Create organisation, department and project boundaries, then issue keys with deliberate model, supplier and region permissions.
- Separate workloads by accountable owner
- Central administrators with delegated operation
- Discuss enterprise SSO rollout and identity-provider requirements
02Make AI economics visible
Relate usage to models, keys and teams, with pricing and nominated billing available for operational review.
- Current usage and cost breakdowns
- Project and department reporting
- Hard-budget requirements assessed against each enforcement path
03Control location and infrastructure
Route through supported EU or country lanes and enforce allowed regions on credentials. Infrastructure boundaries depend on the selected model lane.
- Explicit regional policy
- Fail closed when an allowed route is unavailable
- Assisted onboarding for customer-owned GPU capacity
04Optimise without surrendering policy
Applications can name a model directly or opt in to chat autorouting. Eligibility remains bounded by configured policy and available route telemetry.
- Model-fit and cost inputs
- Availability-aware routing
- Explicit selection policies and inspectable routing metadata
05Use one governed access layer
Adopt compatible APIs where they fit and native specialist endpoints where modalities require them.
- Documented endpoint coverage
- Central key lifecycle
- Selected direct-provider BYOK lanes; custody and fallback scope are confirmed during evaluation