Finamaze · shipped
Finamaze: from B2C to multi-tenant B2B
Migrating Finamaze from a B2C robo-advisor app to a multi-tenant B2B platform for financial institutions, with the infrastructure adapted to match.

Problem
Finamaze started as a B2C robo-advisor: one app, one set of investors, one configuration. The business moved to B2B, selling the platform to financial institutions such as Saudi National Bank, and every institution needed its own investors, data, branding and rules on the same product. That is a multi-tenant B2B platform, and the B2C backend and infrastructure were not built for it.
Constraints
- Live investors: the B2C product kept running while the platform changed underneath it.
- Isolation between institutions: one institution’s investors and data must never be visible to another.
- Regulated clients: each institution brings its own security and deployment requirements, so infrastructure had to adapt per tenant.
Architecture
Key decisions
- The institution is the tenant. Every investor, portfolio and configuration belongs to one institution, so isolation is a property of the data model, not a filter added in each query.
- Users per institution. Each institution has its own users and roles, and no account can see across institutions.
- Infrastructure follows the tenant model. Deployments, configuration and secrets were adapted so a new institution is onboarded by configuration rather than code.
Investor onboarding and KYC moved with the platform: see investor onboarding, KYC and reconciliation.
Results
Numbers to come.
Stack and links
Deep dives
- Finamaze: investor onboarding, KYC and reconciliation: The investor onboarding flow with document and visual identity checks, and reconciliation that keeps the platform's ledger in step with the bank.