One ledger, four apps: inside the CorebankOS core
Why retail, business, web and backoffice all post to one double-entry ledger - and what that removes.
On this page
Every CorebankOS launch runs on the same six-week clock. Not because we rush - because the product arrives finished: four apps, one core and a design system your brand team can own. What changes from bank to bank is the brand, the rails and the rules. Here is exactly how those six weeks go.
Week 1 - Brand in, tokens out
Day one is a workshop, not a kickoff call. Your brand team brings the logo, the palette and the voice; we bring 240+ production screens in light and dark. By Friday every screen has been recolored, retyped and renamed from a single token file - and your team has the Figma library to keep going without us.
- One token file drives colour, type, radius and spacing across all four apps.
- Light and dark ship together - there is no second design pass.
- Copy and product names are tokens too, in every language you serve.
Weeks 2–3 - Wire the core
Retail mobile, business mobile, web banking and the backoffice all post to one double-entry ledger. So “integration” mostly means configuration: products, fees, limits and rails. Card issuing, SEPA Instant and SWIFT are switched on per product, not built per app.
“We didn’t integrate four apps. We configured one core - and all four lit up.”
Weeks 4–5 - Compliance runs in parallel
Risk scoring, step-up authentication and the audit trail are part of the core, not a vendor bolted on in week five. Your compliance team reviews live flows in the sandbox while engineering finishes the rails - so the pen test and the DORA evidence pack land before launch, not after.
Week 6 - Store review and go-live
The last week is deliberately boring. App Store and Google Play reviews, a staged rollout to staff accounts, then friends-and-family, then everyone. Status is public from day one - 99.99% uptime is a number we publish, not a promise we make.
The six-week plan
| Week | Milestone | Owner |
|---|---|---|
| 1 | Brand workshop, tokens applied to 240+ screens | Design |
| 2 | Products, fees and limits configured | Product |
| 3 | Rails live in sandbox: SEPA, SWIFT, cards | Engineering |
| 4 | Compliance review of live flows | Risk |
| 5 | Pen test and DORA evidence pack | Security |
| 6 | Store review, staged rollout, go-live | Everyone |
What happens next
Six weeks is not a stunt. It’s what happens when the product is already built and the only open questions are yours. If you want to see the plan mapped onto your bank, we’ll walk you through it on a call.
Light, dark and your brand: theming a bank in an afternoon
How 240+ screens recolor, retype and rename from a single token file - without forking the app.
Risk scoring before settlement, without the friction
Step-up auth only when it matters: how ops flags a first-time counterparty in under half a second.
Product notes
Get the product notes.
One email a month: releases, deep-dives and the changelog - written by the people who build the core.
Monthly. Product releases and changelog only - no spam, unsubscribe anytime.
Written by Nino, Daniel & Sophie