Checking Link live demo · Optional extension for Johka Control

Connect AI context without breaking customer boundaries.

Across support conversations, CRM records and order systems, Johka Link correlates approved context only after Johka Control authorizes the purpose, fields and reuse. Control decides. Link connects—under explicit authority.

Open Link live demo See the authorization story

Requires Johka Control
Control-first
Private service
Metadata-only evidence

CONTROL-FIRST CORRELATION PRIVATE RUNTIME

SOURCE 01ConversationTechnically reachable

SOURCE 02OrderTechnically reachable

AUTHORITY CHECKJOHKA CONTROL

ALLOW

APPROVED EXECUTIONJOHKA LINK

3 fields released · 3 fields withheld

customer_questionorder_statusdelivery_date

SUPPORT + CRM + ORDER

The systems are connected. The context still needs authorization.

An agent may reach the conversation, account and order separately. Link makes the approved combination useful without turning availability into unrestricted authority.

Authorize before reading

A missing or invalid grant stops execution before the first source fetch.

BLOCK = ZERO SOURCE READS

Release approved fields only

Adapters receive only the fields Control allows. Link filters the result again defensively.

ALLOW ≠ UNRESTRICTED ACCESS

Recheck every reuse

Context approved for support cannot silently become input for sales profiling.

NEW PURPOSE = NEW DECISION

ONE FOUNDATION · ONE OPTIONAL EXTENSION

Control protects the boundary. Link executes the approved connection.

INDEPENDENT FOUNDATION

Johka Control

Evaluates identity, purpose, grants, policy and lineage. Returns the enforceable runtime decision.

Explore Control

OPTIONAL EXTENSION

Johka Link

Uses the Control decision to execute an approved, purpose-bound correlation across sources.

NOT AVAILABLE WITHOUT CONTROL

THE LINK AUTHORIZATION STORY

Same sources. Different authority. Different outcome.

A concrete support-and-order flow shows what changes when authority is absent, granted or reused for another purpose.

01 · SOURCESREACHABLE
Conversation and order data can both be reached.
Reachability alone releases nothing and creates no correlation authority.
SOURCE READS0
02 · NO GRANTBLOCK
Connect without authorization.
Control refuses the purpose-bound correlation. Link stops before touching either source.
SOURCE READS0
03 · SUPPORT PURPOSEALLOW
Authorize only what support needs.
Three approved fields flow. Customer email and internal notes remain outside the result.
customer_questionorder_statusdelivery_datecustomer_emailinternal_notewarehouse_note
04 · NEW PURPOSEBLOCK
Reuse for sales profiling.
The original support authority does not carry over. A different purpose requires a fresh Control decision.
REASONPURPOSE MISMATCH

METADATA-ONLY AUDIT EVIDENCE

DECISIONALLOW

PURPOSEsupport_followup

FIELDS3 approved

CONTENT STOREDnone

PRIVATE BY DESIGN

Link stays behind the customer boundary.

The pilot service is deployed privately alongside Control. Tokens and administrative functions never belong in the browser, and public Link API exposure is not part of the offer.

APPLICATIONApproved workflowRequests a correlation

PRIVATE SERVICEJohka LinkRequests authority first

SOLE AUTHORITYJohka ControlALLOW or BLOCK

No public Link API required
No service tokens in the browser
No raw context in audit evidence
Fail-closed on timeout or invalid scope

CONTROL FIRST · LINK WHEN NEEDED

Choose the route that matches your first protected flow.

Control remains available by itself. Link is added only when the pilot also needs approved context correlation across sources.

EXISTING CONTROL CUSTOMER

Johka Link Pilot Extension

FROM €3,000 extra

Fixed-scope pilot extension, excl. VAT.

Discuss the Link pilot

CONTROL + LINK PILOT

Control + Link Pilot

FROM €6,000 excl. VAT

One approved cross-system AI workflow. Customer-hosted. Final fixed scope agreed upfront.

Discuss Control + Link

Typical timing: 5–10 working days of implementation, typically completed within 2–4 calendar weeks.

You leave with: a working protected cross-system workflow, deployed enforcement and technical evidence of what was allowed, restricted and blocked.

Need Control only? The Founding Design Partner Pilot is €3,500 fixed scope for the first 5 design partners. View Control pilot scope →

Pilot pricing covers a fixed-scope validation engagement. Production licensing, additional workflows, deployments, implementation and ongoing support are agreed separately after the pilot.

AFTER THE PILOT

Prove one controlled connection. Expand from evidence.

01Fixed-scope pilot
Prove one approved Control + Link workflow in your environment.
02Production deployment
Agree the production scope, licensing, implementation and support.
03More protected workflows
Add sources and workflows only under explicit Control authority.

Production licensing and ongoing support are agreed after a successful pilot.