About
About Malai.
Malai is a reference UK retail banking platform — built end-to-end on synthetic data, so prospective operators can read the architecture, walk the customer journey, and evaluate the commercial path before commissioning it.
If your team is weighing whether to commission a retail bank stack, and who to build it with, this page covers why Malai exists and how it's built.
Why it exists
There was no honest reference.
A prospective operator evaluating a platform vendor has two usual options: a slide deck that claims production-grade architecture, or a demo behind a vendor's NDA. Neither lets the operator's engineers see how it's built. Neither shows the customer journey end-to-end. Neither names the commercial path before the contract.
Malai exists to be that reference. It's a UK retail bank assembled honestly — a banking core with enforced module boundaries, a double-entry ledger with a sum-to-zero invariant, a hash-chained audit trail, a typed customer portal running the journey end-to-end, and infrastructure-as-code that stands the whole thing up on a cloud-native footprint. Same shape a real bank's platform team would inherit. Different data.
It is not a bank. It holds no customer money, processes no real payments, and connects to no payment rails. The point isn't to be a bank — the point is to be the reference an operator can read, walk through, take apart, and then commission the people who built it to adapt or recreate for their own bank.
How we work
Three working principles.
Malai is built by platform engineers who would rather be judged on the work than on the pitch. These are the three commitments behind every page on this site.
-
Read the build, not the deck.
Every claim on this site is either backed by something you can open — the running demo, the executed end-to-end flows — or marked as pending. Build-time fences keep module boundaries honest, and the typed API contract generates the customer portal's client code so the wire format and the UI cannot drift. There is no demonstration-purposes magic between what the site says and what the demo does.
-
Synthetic data, by design.
Every customer, account holder, transaction, ledger entry, and audit event in Malai is generated. Sort codes sit in a Malai-reserved range; account numbers validate through the standard UK modulus check; payment rails are not wired in. The data shape matches a real UK retail bank. The data itself is reference fiction.
-
Public, on principle.
The architecture, the security posture, and the lines Malai doesn't cross live on this site — before the walkthrough call. A prospective operator should be able to disqualify Malai (or shortlist it) without scheduling time with us first.
Malai is a reference platform built on synthetic data. Its job is to be evaluated — read, walked through, taken apart, and either dismissed or taken further. Not to hold customer money.
Next steps
Use the demo first. Then talk to us.
Everything this site claims is checkable in the running demo, so the demo is the right first step. A conversation is the second.
-
Step 1
Register and explore
Self-register in the demo and you're granted every role, so you can walk the Banking, Ops and Exec surfaces behind one sign-in, on synthetic data.
-
Step 2
Then talk to us
Once you've formed a view, email the team. We'll answer the questions the demo can't, or set up a thirty-minute walkthrough over video call.