ROADMAP
The FinLabCore roadmap: what is next on a live platform
The platform you would launch on today is complete and in production, accounts, payments, FX, crypto, cards, compliance, back office, ledger. A roadmap here is not a promise to finish the product; it is where a finished product goes next, and what gets built with the partners who need it first.
How this platform grows
Two mechanisms, both structural:
- One core, continuously engineered. There are no forks, so every improvement, capability, capacity, operational tooling, lands for every tenant at once. Capacity and performance are worked as an ongoing programme, not saved for a version number. Why no forks matters →
- Scoped delivery with partners. Extensions beyond the core are built on live foundations for the partner or market that needs them, early partners shape what ships first, and the result joins the one core everyone runs.
Coming to the platform
- FX margin trading, trading on margin atop the live FX book: position keeping, collateral management, exposure limits. Registering interest shapes the first delivery.
- Per-tenant crypto books, extending tenant isolation into crypto accounting, so each brand’s crypto positions live in books as separate as the rest of its world.
Built with you: the on-request catalogue
Delivered per engagement, on foundations that already run in production:
| Deposit & savings products | Term and savings structures on the platform’s account and ledger foundation. |
| Lending & credit | Credit products with the books, controls and reporting the ledger already provides. |
| End-to-end automated regulatory filing | The platform produces regulator-ready data today; full automated submission is delivered per jurisdiction. |
| Additional rails, geographies & card programmes | New corridors and issuers onboarded through the integration layer, configuration on a defined path. |
If it is on this table and on your roadmap, the conversation is a scoping call, not a wish.
Roadmap FAQ
Does anything on this page block a launch today?
No, everything a brand launches with is live: the capability set across the site runs in production. This page is direction, not missing pieces.
How does “on request” actually work?
As scoped delivery on live foundations: your need defines the scope, the build lands on the one shared core, and the platform gains the capability permanently, early partners shape it.
How do we influence what ships first?
By showing up with the need: register interest for the coming-soon items, or bring the on-request scope to a demo, priority follows real partners.
Will our tenant get improvements automatically?
Yes, one core, no forks: platform improvements land for every tenant, and new capabilities switch on per tenant when you want them.
Bring the roadmap you wish we had
The fastest way onto this page is to need something on it.