Bankeiro

The context

Every MB Labs client wanted to launch their own digital bank under their own brand — without waiting a year of development. The answer was Bankeiro: a single banking product (accounts, Pix, cards, internet banking) able to become dozens of different apps. The engineering challenge was not building a bank; it was building forty without drowning.

Decisions that were mine

1. 01Theming by configuration, never by fork

   The rule I defended from day one: no client ever gets a fork. Colors, typography, feature flags and per-brand flows lived in configuration layers over the same codebase. Fixing a bug once fixed all forty apps at once.

2. 02The release pipeline as an internal product

   Publishing 40 apps by hand is where teams break. I built and maintained the CI/CD flow (Bitbucket Pipelines + AWS + Fastlane) and managed the store accounts — from signing certificates to answering Apple review.

3. 03Code review as an architecture tool

   As the person reviewing front-end and mobile pull requests, I used review to spread the standard: state conventions, module boundaries, and what counted as “core” versus brand customization. Review was where the architecture stayed alive.

Where it landed

The platform sustained brands like PaGol, Localiza and Syngenta in simultaneous production, with coordinated releases and a team able to onboard a new bank in weeks, not months.