The Cambrian Experience Explosion
A £2B lender (MFS) collapsed on a £930M collateral shortfall — a compliance and data integrity failure that governed infrastructure should have caught. Block halved its workforce citing AI tools, then grew revenue 24% in the same quarter. WiseTech cut 2,000 engineers, and its CEO declared the era of manually writing code over.
Three signals, collected over a single month. One conclusion.
When anyone can ship a working prototype in a weekend, software isn't the moat. The moat is the substrate the software runs on — and in regulated financial services, that's a much harder thing to build than it looks.
What a substrate actually is
The Moroku Digital Services Layer is that substrate.
It's a single GraphQL API that sits on top of any core banking system — Thought Machine, Temenos, Mambu, FiServ, Data Action — and provisions secure, APRA-aligned access to the bank's system of record. Tenant-isolated data. Event-driven messaging. MFA authentication. Immutable audit logs held in isolated accounts. CPS 230 / 234 ready from day one.
The DSL doesn't replace the core. It governs how experiences reach it — and it unleashes the Cambrian explosion of agentic AI above it, modernising cores in place so they can take advantage of the enormous potential now on the table.
Three live examples
What gets built on top of the substrate is where the story becomes real.
Moroku Money — retail digital banking
Money is the finished application layer for a bank's retail customers: internet banking, mobile, accounts, payments, the lot. The bank keeps its core. We deliver the customer experience. Every transaction, every balance lookup, every payment flows through the DSL, which hands off to whatever system of record the bank already operates.
Teller — staff operations
Teller is the staff-facing surface: same substrate, different audience. Bankers, branch staff, and operations teams get the visibility and controls they need without any change to the underlying core. One substrate, multiple surfaces, consistent data, consistent security, consistent audit.
Kanopi — AI-native, in a regulated environment
Kanopi is the interesting one. It's a document and data intelligence platform for Australian financial services professionals — built AI-native using code generation tools, and reaching a working prototype in weeks rather than months. It's also the live test case inside Moroku's AI research programme for a question the whole industry needs to answer:
Can AI-generated code be productionised for a regulated environment at scale?
The answer lives in the substrate. The generated code doesn't change. What changes is where it runs, who owns it, and how it's governed — Moroku-owned data environments in Sydney, append-only audit logging with row-level security, MFA and IP-restricted access, incident management wired into operational backbone from the first day of real client data.
AI assembles the experience. The substrate makes it operable in a bank.
Why Moroku is different
Everyone in this market has a story about modernisation. Most of them ask the bank to rip out its core, or replace one form of vendor lock-in with another. Neither is the right answer in 2026.
We sit on top of whatever core the bank already runs — core-agnostic, partnership-led — so AI-native assembly can happen safely above the line. Built by us. Built by our ecosystem. Or built by the bank itself, using tools that didn't exist eighteen months ago. The core modernises in place. The experiences evolve independently.
This is what core-agnostic, AI-native, and APRA-aligned look like when you put them together in a single platform.
The moment the substrate matters most
The Cambrian explosion in AI-assembled software is not a threat to infrastructure players. It's the moment the substrate matters most. Because once a small team with Claude, Lovable, and Cursor can replicate any customer experience you've ever launched, the question stops being "what can you build?" and starts being "what can you run, safely, for a regulated financial institution, at scale?"
That's a question about the substrate. Not the surface.
There are 100+ mutuals and non-bank lenders across Australia and New Zealand who need a modern digital banking partner. The technology is ready. The regulatory environment is aligned. The substrate is live.
The substrate wins.
Explore the Digital Services Layer Book an Architecture Review