COMPLIANCE & TRUST ENGINE

Make compliance an execution capability.

Octoryn can evaluate trusted identity and environment signals, inspect sensitive data, enforce versioned policy and constrain provider eligibility before an AI request reaches model supply.

01Whosigned identity trust

02Whereenvironment and residency

03Whatinput and output classification

04Whycontent-free decision evidence

Trust identity without trusting a header

A short-lived, request-bound trust context carries verified enterprise identity signals into the Router. It narrows an already authenticated principal and is consumed once before provider credentials are touched.

Human, agent and service-account identityExpand details
This is part of Trust identity without trusting a header. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
SSO, MFA, device-trust and mTLS signalsExpand details
This is part of Trust identity without trusting a header. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Tenant, product and request bindingExpand details
This is part of Trust identity without trusting a header. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Cross-replica replay protectionExpand details
This is part of Trust identity without trusting a header. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Evaluate where the request is running

Region decisions use signed deployment and network evidence rather than a caller-supplied country field. Expected cloud, ASN and runtime signals can raise or lower environment trust.

Deployment and runtime regionExpand details
This is part of Evaluate where the request is running. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Source country, ASN and network classExpand details
This is part of Evaluate where the request is running. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
VPN, proxy and TOR risk signalsExpand details
This is part of Evaluate where the request is running. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Residency checked before route selectionExpand details
This is part of Evaluate where the request is running. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Classify data on both sides of the model

Input and output inspection runs in memory. Policies can allow, mask, deny or require external human approval when PII, PHI, payment data, Australian identifiers or credentials are detected.

PII, PHI, PCI, TFN and ABN detectionExpand details
This is part of Classify data on both sides of the model. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Secret and credential detectionExpand details
This is part of Classify data on both sides of the model. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Allow, mask, deny and HITL actionsExpand details
This is part of Classify data on both sides of the model. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Prompts and outputs excluded from evidenceExpand details
This is part of Classify data on both sides of the model. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Route only to eligible provider capability

Provider Trust is about handling posture, not model quality. Reviewed profiles express region, retention, ZDR, contract, reliability and dated attestation evidence. Explicit requirements always override a composite score.

Regional processing and residency modesExpand details
This is part of Route only to eligible provider capability. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Retention, training-use and ZDR postureExpand details
This is part of Route only to eligible provider capability. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Dated first-party attestation evidenceExpand details
This is part of Route only to eligible provider capability. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Minimum trust plus hard capability gatesExpand details
This is part of Route only to eligible provider capability. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Detect abnormal behaviour without storing content

A shared metadata-only authority can detect rate anomalies, rapid country changes, network changes and unexpected provider shifts across Router replicas.

Bounded per-principal request windowsExpand details
This is part of Detect abnormal behaviour without storing content. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Impossible-travel and network-change signalsExpand details
This is part of Detect abnormal behaviour without storing content. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Provider-family shift detectionExpand details
This is part of Detect abnormal behaviour without storing content. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Fail-closed authority handlingExpand details
This is part of Detect abnormal behaviour without storing content. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Version policy, approvals and rollback

Policy as code turns a control into a reviewable artifact. Approved versions are immutable; activation and rollback produce evidence and follow the same reviewed deployment path as Router configuration.

Schema-versioned YAML or JSONExpand details
This is part of Version policy, approvals and rollback. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Separation of author and approverExpand details
This is part of Version policy, approvals and rollback. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Explicit active versionsExpand details
This is part of Version policy, approvals and rollback. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Content-free activation and rollback evidenceExpand details
This is part of Version policy, approvals and rollback. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Explain every decision without copying the conversation

A decision identifies the policy, rule, action, trust and risk scores, classifications, eligible provider posture and canonical evidence hash. Governance readers can inspect why a route was allowed or denied.

Tenant-scoped compliance summaryExpand details
This is part of Explain every decision without copying the conversation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Route simulation with provider eligibilityExpand details
This is part of Explain every decision without copying the conversation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Canonical evidence hashesExpand details
This is part of Explain every decision without copying the conversation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Low-cardinality operational metricsExpand details
This is part of Explain every decision without copying the conversation. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

OCTORYN ROUTER

Define the trust boundary before enforcement.

Start disabled, validate in Shadow, then activate reviewed policy for a bounded workload. Enforcement is a deployment decision, not a marketing default.

Read governance docs