JOHKACONTROLRequest a pilot
Runtime authorization for AI context

AI context should not gain authority just because an agent can access it.

Johka Control enforces runtime authorization for AI context flows, correlation and derived context—before protected context reaches the AI provider.

See Johka Control in action Request a pilot
  • Customer-hosted
  • Fail-closed
  • Auditable
  • Provider-independent core
LIVE ENFORCEMENT PATH POLICY ACTIVE
01
REQUEST ORIGINApplication / Agent
CONTEXT ATTACHED
Context envelope
ENFORCEMENT POINTJOHKA CONTROL
VERIFYING
IdentityPurposeGrantLineage
ALLOWREDACTBLOCKREQUIRE_GRANT
AUTHORIZED PAYLOAD
03
UPSTREAMAI Provider
MINIMIZED
UNAUTHORIZEDNO PROVIDER CALL
Decision ID · jhk_08F21Audit: metadata only

THE AUTHORITY GAP

AI systems can reach more context than they should be allowed to use.

Retrieval controls what data can be found. Johka controls whether context may flow, correlate, be derived or be reused at runtime.

01

Access is not correlation authority

An agent may technically reach two contexts without being authorized to combine them. Johka makes that boundary explicit and enforceable.

REACHABLE ≠ AUTHORIZED
02

Derived context keeps its authority

Summaries and inferred facts do not become unrestricted because they are new. Johka carries origin, lineage and policy forward.

DERIVATION ≠ RESET
03

Unauthorized means no provider call

When Johka refuses a flow, protected context stays at the enforcement point. The upstream AI provider receives nothing.

BLOCK = ZERO EGRESS

AUTHORIZATION STORY · 6 DECISIONS

Watch authority change—not just the prompt.

One request evolves across context boundaries, explicit grants, minimization, derivation and revocation. Johka evaluates every transition.

STEP 01 / 06ALLOW

Bind authority to origin

A payroll context enters with tenant, principal and purpose already attached. Johka evaluates the flow before payload inspection begins.

REQUESTpayroll/employee-104 → benefits-agent
DECISION EVIDENCEruntime
  • tenant: acme-eu
  • principal: hr-ops
  • purpose: benefits-review
PROVIDER CALLPermitted

DEPLOYMENT & CONTROL

Built as enforcement infrastructure, not another AI data layer.

Johka sits in the execution path and returns an enforceable decision before an AI request can leave the controlled environment.

CUSTOMER ENVIRONMENT
CALLERSApps · Agents · RAGContext identity attached
→
PRIVATE CONTAINERJohka ControlPolicy · grants · lineage
→
GATEWAYProvider AdapterOpenAI proven today
AUDIT RAIL

Decision metadata · finding types · grant state · no raw protected context

Customer-hosted inside your controlled environment
Private, versioned container deployed inside your controlled environment
Scoped grants by purpose, principal, agent and context
Revocation and expiry evaluated at runtime
Context lineage retained across derived information
Privacy-preserving audit without raw protected content
CONTEXT MANAGEMENT

Organizes what AI can find.

≠
JOHKA CONTROL

Determines what AI context may do.

CONTROLLED PILOT

Prove one protected AI flow in 5–10 working days.

Start with one real application, one provider path and one authority boundary. We map the flow, deploy Johka and deliver evidence of the decisions it enforces.

Run the live authorization story
STARTING AT€3,500
  • Context-flow and boundary mapping
  • Customer-hosted Johka deployment
  • One provider integration
  • Policy, grant and audit configuration
  • Technical evidence and pilot readout
Discuss a pilot