Governed control

One control plane for model access.

Give Octopus customers and family products the access they need, while keeping keys, budgets, audit context and operational visibility in one governed layer.

01KeysScope access to the workload

02BudgetSet accountable boundaries

03AuditPreserve decision context

Keys belong to a clear scope

Issue access for a product, environment or workload instead of sharing one credential across the organisation. Rotation and revocation remain operational actions, not application rewrites.

Workload-scoped API keysExpand details
This is part of Keys belong to a clear scope. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Separate production and development accessExpand details
This is part of Keys belong to a clear scope. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Central rotation and revocationExpand details
This is part of Keys belong to a clear scope. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Budgets become policy

Assign accountable limits to the teams and applications that consume model capacity. Budget context stays beside routing policy so cost decisions can be made before a request leaves the control plane.

Workspace and workload boundariesExpand details
This is part of Budgets become policy. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Usage-aware policy decisionsExpand details
This is part of Budgets become policy. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Clear ownership for consumptionExpand details
This is part of Budgets become policy. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Audit the route, not the conversation

Record the operational facts needed to understand a routing decision: which policy applied, which path was selected and how the request behaved. Product data can remain outside the audit trail.

Policy and route attributionExpand details
This is part of Audit the route, not the conversation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Operational event historyExpand details
This is part of Audit the route, not the conversation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Data-minimising audit contextExpand details
This is part of Audit the route, not the conversation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Observe the layer shared by every product

A shared router creates one place to inspect latency, errors, usage and route outcomes across the Octopus family. Product teams keep their own application telemetry while the platform view remains consistent.

Latency and error visibilityExpand details
This is part of Observe the layer shared by every product. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Usage and route outcome signalsExpand details
This is part of Observe the layer shared by every product. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Consistent operational vocabularyExpand details
This is part of Observe the layer shared by every product. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Workspaces preserve ownership

Organise policies, keys and budgets around the customer or product boundary that owns them. Shared infrastructure does not need to mean shared administration.

Customer and product separationExpand details
This is part of Workspaces preserve ownership. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Delegated operational ownershipExpand details
This is part of Workspaces preserve ownership. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Common controls, isolated scopeExpand details
This is part of Workspaces preserve ownership. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

OCTORYN ROUTER

Establish the control boundary first.

Define the workspace, access scope and budget posture before connecting a production workload to Octoryn.

Open the control guide