Classify
Detect sensitive input before provider access and derive policy-relevant data facts.
Trust layer · EU / local controls
Control where sensitive AI use cases may go.
Talon’s category is the control plane for company AI use cases. For European and regulated teams, EU/local destination policy, PII handling, air-gap options and signed runtime evidence are the trust layer that makes that operating model usable.
Input: confidential
Candidate: OpenAI / US
→ REJECTED before dispatch
Candidate: Ollama / LOCAL
→ SELECTED on policy-aware runner path
Signed facts:
→ rejected candidate + reason
→ selected destination
→ session / correlation contextPII before egressEU / LOCAL policyCandidate rejectionAir-gap postureObserved destinationsSigned evidence
Why it belongs under the control plane
Regional policy should not be rebuilt in every AI application.
Once a company has several AI use cases, each one should not invent its own destination checks, PII behavior and review artifact. Talon applies these controls on governed paths and records what happened.
Constrain
Deny disallowed provider-bound traffic or reject candidates where Talon owns policy-aware selection.
Prove
Record selected and rejected destinations so operators can review observed runtime behavior.
Two control paths
Chosen destination and policy-selected destination are different problems.
Gateway proxy: the client chooses the provider route. Talon can allow or deny that provider-bound request; it does not silently convert an OpenAI proxy request into an Ollama request.
Policy-aware runner: Talon owns candidate selection and can reject a disallowed candidate before dispatch, then select an allowed EU or LOCAL alternative.
# proxy path
client chose provider
→ allow OR deny that route
# policy-aware runner path
classify request
→ evaluate candidate
→ reject by policy
→ select allowed alternativeReliability under regional policy
Fallback does not create a sovereignty exception.
On supported transient failures, explicitly configured fallback candidates are re-checked against effective policy. Under eu_strict, a non-EU/LOCAL candidate is skipped rather than dispatched. If no valid candidate succeeds, the path fails closed.
primary → transient failure
fallback candidate → policy re-check
if region/model/budget policy fails
→ candidate skipped
if no valid candidate succeeds
→ fail closed
→ signed attempt + terminal evidenceEU and local posture
Useful controls for European and regulated teams.
EU strict
Reject non-EU/LOCAL candidates where Talon controls routing and fail closed when no allowed candidate remains.
Air-gap / local-only
Use explicit local or EU providers and deny-by-default egress posture for private or disconnected deployments.
Runtime consistency
Compare declared residency posture with observed signed destinations and denials.
Honest compliance language
Supporting controls and operator proof—not a compliance certificate.
Talon can help a team show which destinations were configured, which runtime paths were observed, what was blocked and whether evidence verifies. That supports reviews and audits. It does not make a deployment compliant by itself.
talon compliance sovereignty --format html
talon audit show <evidence-id>
talon audit verify <evidence-id>
# technical evidence
# not legal determinationTest the boundary
Run one sensitive request and inspect the actual destination decision.
Reproduce a block before provider access, then reproduce a policy-aware local selection. Inspect and verify the signed runtime facts instead of relying on a marketing claim.