Core banking should be a platform you program, not a product you're stuck with.

Four pillars, six independent blocks. You adopt what you need, when you need it — and you keep control of the architecture and the roadmap.

Four pillars.

  • Ledger

    The foundation of any financial system: consistent accounts, balances and transactions, with Midaz.

  • Transactional Services

    They govern how money moves — real-time validation, reconciliation, workflow orchestration and credit.

  • Governance

    Reporting, multi-tenancy and observability as structural components, not add-ons.

  • Connectivity

    Integration with BACEN, Brazil's central bank, and with partners through native rails and plugins. No core operates in isolation.

The architecture, assembled.

The products compose on top of the ledger; the ledger connects to the central bank through the rails. One block, one service — you assemble from what you need.

Interfaces and plugins.

Plugins connect the platform to third-party messaging and services — certified adapters, not rails we own. Lerian's own rails, over the RSFN, live in the Brazil Rails.

  • Pixconnection to Pix, Brazil's central-bank instant payment system, through certified partners (JD, BTG).
  • TEDconnection to TED/STR, the same-day interbank wire, through certified partners (JD, BTG).
  • Feesconfigurable fee calculation and charging on top of operations.
  • CRMintegration with CRM systems for customer data.
  • Access Managercentralized authentication, identity and access control.
See the Brazil Rails →

Run it where you decide.

The deployment model (BYOC or Lerian Cloud) is independent from the licensing model (Community or Enterprise). You combine what makes sense for your operation.

BYOC

The platform runs in your own AWS, GCP or on-prem. Lerian ships the software, the Helm charts and the Terraform templates; you operate the infrastructure. Your data never leaves your environment.

Lerian Cloud

Lerian hosts and operates the platform (PaaS): infrastructure, upgrades, monitoring and high availability. You deploy your applications on top and focus on building financial products — while still owning the stack.

  • Community + BYOCself-managed with Midaz's source-available Helm charts; support through GitHub and Discord.
  • Enterprise + BYOCfull BYOC with Lifecycle Management, plugins, Console, dedicated support and an SLA.
  • Enterprise + Lerian CloudLerian runs everything; you get the complete platform with no infrastructure responsibilities.

Lerian Console.

The Console is the web interface for operating every product on the platform — Midaz, the plugins, Reporter and the rest — from a single panel. It is part of the Enterprise offering.

Open by design.

Openness here is an architecture principle, not a positioning strategy. Midaz is source-available under the Elastic License 2.0, with its code public on GitHub. Reporter, Matcher, Flowker, Tracer, Lender and the plugins are licensed products, with repositories kept internal.

With a source-available core, if Lerian disappears tomorrow you still have the code — and your central operations keep running.

View on GitHub →

Build your core, your way.

Talk to the people who build the platform — or go through the documentation on your own.