Wahid — by Keystone Labs

One platform for every banking operation.

Wahid unifies case management, workflow and integrations in a single, auditable back office - configurable per bank, with a governed AI copilot that builds new modules from plain language.

ON-PREMISETAMPER-EVIDENTCONFIGURABLEGOVERNED AI
Wahid platform home with module tiles and live operational stats
Open cases
1,248
SLA on track
How it works

A case type is four things, composed.

Draw the process. Define the data. Declare the rules. Set the clock. Wahid composes them into a case type - and every case runs it.

Workflow
The state machine - stages, gates, timers and integration.
Form schema
The data the case carries.
Decision table
The rules that route it.
SLA policy
The clock it answers to.
Result
One case type

Configured, versioned, ready to run.

Fraud reviewKYC reviewDisputesOnboarding
Follow a case
01 / 04

Intake to sealed, in one flow.

  1. 01
  2. 02
  3. 03
  4. 04
A case arrivesIntake from any channel lands in the right team's queue, SLA armed.
CASE-2026-00100012
INTAKE
Wahid case management dashboard
Visual workflow builder canvas with states and transitions
Case detail with a unified activity timeline
Tamper-evident audit log with integrity verification
Scroll to advance the case ↓
The platform

Everything a back office needs, in one place.

Operate

Case management, end to end

Queues and team routing, SLA timers on business calendars, row-level visibility - and one timeline that records everything.

Case detail with a unified activity timeline
Configure

A workflow engine you can see

Design on a canvas: stages, transitions, role gates, approval gates, decision gateways and integration API calls. Versioned, with history and restore.

Visual workflow builder canvas with states and transitions
Control

Access to the widget

Default-deny RBAC gates modules, tabs and widgets. One matrix of who sees what.

Role-based access control matrix
See

Customer 360

Profile, accounts, cards and loans bound to your core over mTLS - no data duplication.

Customer 360 profile bound to core-banking data
Extend

Modules, two ways

Extend the platfrom for your specific usecase using UI based module builder or full React modules on the SDK.

Module and page builder for per-bank extensions
Describe

Describe it. Watch it build.

Tell Wahid what a module should do, in plain language. The copilot designs it, builds every screen, and hands you a draft - it authors configuration, never decisions, and nothing goes live without your review.

On your model

Your in-house LLM, your cloud, or an API - a config choice, so data can stay inside your perimeter.

Inside the guardrails

The copilot builds only what the platform can validate. Everything lands as a draft behind the same activation checklist as human work.

On the record

Every generation is recorded verbatim - prompt, output, acceptance, token spend - and audited like any other admin action.

Describe it instead

A loan-restructuring module: officers see a queue of restructure requests, open one to review the customer’s loans, fill a restructure form, and submit - which files a RESTRUCTURE case.

Design ready - 3 pages, 2 permissions declared
Page ready · restructure-queue
Page ready · restructure-review
Page ready · restructure-form
Done - everything is DRAFT. Review, then activate.
Loan restructuring
3 pages · 2 permissions · DRAFT

Illustration of the real flow - module generation in Wahid’s admin builder.

Prove

A record you can hand a regulator.

Every action chains to the last with sealed hashes. Verify integrity on demand and hand regulators evidence, not exports.

  • Hash-chained, concurrency-safe sealing
  • On-demand chain verification
  • Customer-access auditing
5h ago
Owning-team orphan scan
seal a1f3…9e2c ← 7b04…11af
✓ sealed
11h ago
Customer data viewed
seal 7b04…11af ← c2d8…5a90
✓ sealed
11h ago
Role perms updated
seal c2d8…5a90 ← f591…03bd
✓ sealed
1d ago
Case transitioned → SEALED
seal f591…03bd ← 44d0…7a8b
✓ sealed
1d ago
Decision table evaluated
seal 44d0…7a8b ← genesis
✓ sealed
Connect

One integration layer. Every system, every module.

Wahid Core sits between your bank's systems and the modules your teams work in — orchestrating REST/SOAP over mTLS, an outbox with retries and circuit breakers, with every call permission-gated.

Bank systems
Core banking
REST · mTLS
Payment hub
ISO 20022
Card management
SOAP · mTLS
Wahid Core
Integration layer
Routing & orchestration
mTLS + HMAC verified
Outbox · retries · dead-letter
Circuit breakers
Permission-gated calls
Wahid modules
Customer 360
360° profileFile dispute
Lending
ExposureOriginate
Case management
TimelineOpen case
View Action

Default-deny RBAC

Permissions gate every module, tab and widget - with segregation of duties.

Tamper-evident audit

A hash-chained system of record, verifiable from day one.

On Premise

Runs on your infrastructure - your data never leaves your estate.

OIDC-native identity

Keycloak out of the box - JIT provisioning, role sync, teams from IdP groups.

The outcome

Months, not years without losing control.

Configuration over code where it's safe. Modules over forks where it's not.

Time to market

  • Workflows, forms, rules and SLAs are configuration
  • New use cases without a release
  • Per-bank modules ship without forking the platform

Control

  • On-Premise, on your infrastructure
  • Tamper-evident audit from day one
  • Default-deny RBAC to the widget level

See Wahid in action.

A guided walkthrough with your use case in mind.