Modernise the core.
Without ripping it out.
For CEE tier-1 universal banks: ship new products in 90 days, on Coreal's new-product ledger, read-only on the legacy core. KYC orchestration, BPM workflows, AI-orchestrated risk — DORA-aligned out of the box. The core stays the book of record; new flows live in Coreal.
Core-banking-adjacent.
The same architecture, in a different vertical.
For a telco it's billing-adjacent: read-only on the BSS event bus, new products on Coreal. For a bank it's core-banking-adjacent: read-only on the legacy core (T24, Mambu, Profile, FIS, …), new products on Coreal. Same philosophy: do not touch the book of record. Build new flows alongside it.
Customer master, account state, ledger entries, branch / treasury postings — all stay on the legacy core. We subscribe read-only via a DBA-approved read-replica or vendor-supported message queue (T24 DataSource, Mambu webhook, etc.).
- ›Zero write-path from Coreal to core
- ›Reverts in a single config change
- ›DORA Art. 28 evidence prepared in week 1
New flows — KYC orchestration, card-to-card transfers, crypto-buy, FX, savings, embedded corporate finance — run on Coreal's double-entry ledger with the BPM engine, decision journal and AI orchestrator built in.
- ›Double-entry ledger with idempotency at the boundary
- ›Decision journal · 7-year retention · replayable
- ›AI orchestrator (Minctrl) with mandatory security + compliance gates
From a brief, to a live product, to a migrated stack.
In three waves.
KYC orchestration · onboarding modernisation
Read-only feed from legacy core. KYC pipeline on Coreal: document capture · sanctions screening · auto-approve. Decision journal live for AMLA review. Target: 80%+ auto-approve, 38s median, FTE −60%.
New-product launches · cards · transfers · crypto-buy
Card-to-card transfers on Coreal ledger. Virtual card issuance. Crypto-buy via licensed CASP partner. FX. Each new product ships in 30–45 days on the same Coreal stack — the bank does not staff a new fintech team.
Gradual migration · core becomes read-only book
New-product flows now dominate transaction volume. Legacy core gradually demoted to read-only book of record for long-tail existing accounts. New customer onboardings open accounts on Coreal ledger directly; legacy is only consulted for compatibility.
What the bank owns. What Coreal owns.
Two columns. Five crosspoints. No third party in the demarcation — regulator and core-vendor relationships sit on top of this split, not inside it.
Two value streams.
New revenue + saved cost.
Bank business case is split: new-product fee revenue from Coreal-ledger flows, and operational cost saved on the legacy onboarding pipeline. Indicative numbers on a 6–8M retail-customer base (CEE tier-1 universal bank cluster).
Card interchange + monthly fees · card-to-card transfer fees · FX margin · crypto-buy spread · savings-product fees. Typically +4–8% on top of the bank's baseline retail fee revenue.
Onboarding FTE −60% · sanctions false-positive review −85% · AML evidence-pack labour −90% · branch onboarding labour −40%. Cost-to-income on Coreal-handled flows lands 15–22 percentage points below baseline.
The 90-day sequence,
day by day.
How a tier-1 CEE universal bank ran Wave-1: regulatory perimeter in days 1–14, T24 integration in days 14–30, KYC pipeline build in days 30–60, soft launch days 60–85, public launch days 85–90. Where deals break — the bank-specific failure modes.