Platform, Console
Compliance officers configure journeys, work alert queues, and pull evidence themselves. Engineering is needed for the integration, not for every policy change.
The workspace
The same workspace your compliance lead uses day to day — journey versions on the left, live sessions and decisions on the right.
What is in it
Each one writes to the same audit trail, so a change made in the console is as evidenced as a call made through the API.
01
Compose a journey from modules as nodes: capture, checks, branches on risk score, and terminal decisions. Every change is versioned, and sessions record the version they ran under.
02
Generate a single-use or reusable link for any journey and send it by email or messaging. No integration required, and the result lands in the same queue as API sessions.
03
Alerts and referred sessions arrive with severity, owner, and SLA. Reviewers see every signal that fired, add notes and attachments, and escalate under four-eyes control.
04
Maintain lists of rejected applicants, banned devices, and internal exceptions. Lists are enforced inside the journey, not bolted on afterwards, and every entry records who added it and why.
05
Completion and drop-off by step, decision mix, referral rates, reviewer throughput, and rule hit rates over time, filterable by journey and period.
06
Separate operator, reviewer, approver, admin, and read-only auditor roles. Reviewers cannot approve their own escalations, and permissions are enforced server-side.
07
Every configuration change, data access, decision, and export is written to an append-only log with actor, timestamp, and before-and-after values.
08
Export a single case as an evidence bundle, or a period as CSV and PDF for internal audit and regulator requests.
09
Set retention periods per data class, delete a session on request, and record the legal basis for anything held longer.
10
Your logo, colors, copy, and language defaults on the hosted flow, so the customer never sees a vendor handoff mid-onboarding.
Getting started
A policy change should take an afternoon, not a release cycle.
01
1
Start from a preset built around a UAE or GCC regulator expectation rather than an empty canvas.
02
2
Add or remove checks, set risk bands, and decide what refers to a human instead of auto-declining.
03
3
Define who works which queue, who can approve, and who only reads. Auditor access is read-only by design.
04
4
Publish the version, run it through a verification link in sandbox, then point production traffic at it.
Seat counts, role granularity, and retention limits vary by plan, seats and retention are set in your plan.
We will configure a preset for your license type and let your compliance lead drive it.