JOHKALINK
Johka homeWhy JohkaEnforcement storyArchitectureJohka Control
EN⌄
NLNederlandsFRFrançaisENEnglishDEDeutsch
Discuss a pilot
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.

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 withheld

SUPPORT + CRM + ORDER

The systems are connected. The context still needs authorization.

An agent may reach conversation, account and order separately. Link makes only the approved combination useful.

01

Authorize before reading

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

BLOCK = ZERO SOURCE READS
02

Release approved fields only

Adapters receive only the fields Control allows.

ALLOW ≠ UNRESTRICTED ACCESS
03

Recheck every reuse

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

NEW PURPOSE = NEW DECISION

CONTROL + OPTIONAL LINK

Control protects the boundary. Link executes the approved connection.

INDEPENDENT FOUNDATION

Johka Control

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

Johka Control
OPTIONAL EXTENSION

Johka Link

Executes the approved, purpose-bound correlation across sources.

REQUIRES CONTROL

THE LINK AUTHORIZATION STORY

Same sources. Different authority. Different outcome.

  1. 01REACHABLE

    Conversation and order data can both be reached.

    Reachability alone creates no correlation authority.

  2. 02BLOCK

    Connect without authorization.

    Control refuses; Link stops before touching either source.

  3. 03ALLOW

    Authorize only what support needs.

    Three fields flow. Customer email and notes remain outside the result.

    customer_questionorder_statusdelivery_datecustomer_email
  4. 04BLOCK

    Reuse for sales profiling.

    A different purpose requires a fresh Control decision.

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.

APPLICATIONApproved workflow
→
PRIVATE SERVICEJohka Link
→
SOLE AUTHORITYJohka Control

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 needs approved context correlation across sources.

EXISTING CONTROL CUSTOMER

Johka Link Pilot Extension

FROM €3,000 EXTRA

Fixed-scope pilot extension.

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 a pilot

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

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

JOHKA LINKControlled context correlation.

Optional correlation extension for Johka Control.

Johka ControlWebsitesinfo@johka.be