kmplai · a product by Edarx

Compliance intelligence for regulated firms. Conversational. Human-governed.

Ask the way you'd ask a colleague. kmplai connects to your systems, runs investigations against your own procedures, and cites every answer to the rule. All in one chat.

Industry and regulatory agnosticAudit pack builds itselfHuman-governed by designOn-prem or private cloud
The idea

A co-analyst that works the way your team does.

Instead of switching between a records system, a document folder, a portal and an internal note, you talk to kmplai. It fetches the data, runs the investigation, reads your procedures and explains the rule. One chat window, everything in it.

Where kmplai fits

Where the break lands next.

kmplai is not a reconciliation tool. The tools that compare numbers and flag mismatches already exist. That problem is solved.

kmplai sits on top of the systems you already use and handles everything that happens after a flag is raised: collecting evidence, following the procedure, reasoning through the root cause, escalating when required, and building the audit trail, all through a conversation.

Because every step is logged as it happens, the audit pack assembles itself continuously. When the auditor arrives, the evidence is already there.

Capabilities

Three modules, one agentic workflow.

Three modules sit behind every chat. A Data Fetcher pulls from any system you've connected, or messages the right person when there's no API. A Break Investigator runs your procedure step by step. A Knowledge Base answers policy questions cited to the rule. Every action lands in an immutable audit trail.

Get yesterday's custodian positions
Sources called0 / 5
APIRecords system · ledgercalling
APICash & balances · currentcalling
APIPosition data · livecalling
APIReference data · eventscalling
DM@ops-desk · overnight fileDM'd
01 · Getting the data

Pulls data from APIs, or the right person.

kmplai calls every system you've connected, the moment you ask. Where there's no API it messages the right person and waits for the file.

Investigate break BRK-04182
Following Cash break · v2.4
Cash break investigationv2.4 · 5 steps
Pull custodian statement
Reconcile against ledger
Check pending corp actions
Isolate root cause
Recommend next action
02 · Break Investigator

Investigations that follow your procedure.

The agent uses your firm's own procedure as its instructions, fetches evidence in order from every connected source, and hands back a structured root cause with a recommended next action.

When must we escalate a material breach?
Checking firm policy & rulebook
Answer cited from 2 sourcesDrafting
§Sources · Breach Escalation Policy §4.2 · Rulebook §6.1
03 · Knowledge Base

Plain-English answers, cited to the rule.

Every firm procedure, policy and control lives in kmplai alongside the regulatory rulebook. Ask anything in plain English and get a precise answer, referenced to the exact policy section and rule.

Prepare the Q1 audit pack
Scope: all closed breaks, Jan to Mar, with decisions & rule refs?
Yes, and include late settlement exceptions.
On it. Compiling from the live log
Q1 audit logwriting
TimeEventByRule
09:12:04Break opened · BRK-04118agent§4.2
09:14:22Evidence gathered · 6 sourcesagent§4.3
09:18:47Root cause · Late settlementagent§4.5
09:21:11Escalated · L2 reviewerk.chen§5.1
09:24:30Closed · approvedsignedj.novak§5.4
04 · Audit preparation

The audit pack builds itself as you work.

Every step (what was checked, what was found, who decided, when) is logged against the procedure step and rule it satisfies. Ask for a Q1 report and kmplai returns a complete, structured pack. No year-end scramble.

Getting started

Three steps. No rip-and-replace.

Bring your procedures. Connect your systems. Open the chat. kmplai reads the context you've given it and starts working, the way a knowledgeable new colleague would.

  1. 01

    Context

    Provide your policies, procedures, controls and escalation thresholds. This is what tells kmplai how your firm specifically operates: what counts as a material breach, who gets escalated to, what evidence each case type requires.

  2. 02

    Connections

    Authorise API connections to the systems your team already uses. Data sources, internal records, communication tools, anything the work touches. No rip-and-replace.

  3. 03

    Ask

    Open the chat and start asking. No training programme, no onboarding workflow, no dashboard to learn. kmplai reads the context you've given it and goes.

kmplai· Case KMP-04182 · Compliance ReviewLive
Case KMP-04182 · workflow
Case-handling playbook · v2.4
● Human review
Evidence gathered
Pulling from connected sources
RecordsDocumentsCustomers
Procedure matched
Case-handling playbook · v2.4
Draft summary written
Fully cited · 4 risk flags
Analyst review
Awaiting J. Novak
Commit to ledger
Signed · immutable
LiveConnecting sources …
Who it's for

Industry and regulatory agnostic by design.

Every regulated firm has the same operational shape: receive data, reconcile it, investigate discrepancies, escalate decisions, document the trail, prove compliance to a regulator. Only the context changes from one firm to the next. kmplai reads the context you give it and works accordingly.

01

Any sector

Financial services, insurance, healthcare, regulated tech, public sector. Wherever a body of rules governs day-to-day work, the operational shape is the same.

02

Any rulebook

Drop in the regulations and standards your firm operates under. kmplai cites the specific clause it relied on, every time, in plain English.

03

Any system

Connect to whatever you already use. APIs, files, message threads, internal portals. kmplai meets your stack where it lives.

One firm brings their reconciliation playbook. Another brings a multi-step investigation procedure. A third brings their reporting controls and escalation thresholds. The agent reads the context it was given and runs accordingly. The chat experience is identical. No code changes required.

How we built it

Three non-negotiables from line one of code.

01

Human in the loop

Every final decision on a reportable breach (whether to escalate, whether to notify a regulator, whether to remediate) is made by a named human whose identity and timestamp are permanently logged. kmplai handles the 90% of work before the decision; the human owns the 10% that requires judgement.

02

Traceable by default

Every request, response, decision and escalation is logged with full source provenance. Findings cite the specific procedure step and regulatory rule that satisfied them. The audit pack assembles itself as you work.

03

Your data, your perimeter

Deploy on-prem or in a private cloud. Data stays where it lives. kmplai brings the intelligence to the data, not the other way round. No rip-and-replace of your existing systems.

Get started

See kmplai on your playbook.

Bring a real case. We'll show you how kmplai pulls the evidence, follows your procedure, cites the rule and assembles the audit pack, end to end, in under an hour.