Skip to main content
We believe financial infrastructure should be inspectable, extensible, and owned by those who operate it. Open by design is not a positioning strategy for us. It is an architectural principle. Midaz, our core ledger, is source-available under Elastic License 2.0 because financial systems require transparency, control, and long-term sustainability. Fetcher, our data ingestion service, is source-available too. The rest of the Lerian portfolio — Reporter, Matcher, Flowker, Tracer, Lender, Streaming Hub, and our plugins — is available to licensed customers, with repositories maintained internally, while preserving the same principles of transparency, auditability, and customer ownership of data and operations.

Why Source-available at the core?


A source-available core creates structural advantages — not just community engagement. By keeping Midaz source-available, we enable:
  • Transparency: Every line of the core ledger is visible and auditable. No hidden logic. No opaque behavior.
  • Independence: Institutions control their stack and retain access to the source code of the ledger that holds their money.
  • Extensibility: Teams can adapt the ledger to their regulatory, operational, and product requirements.
  • Trust by design: Visibility reduces systemic risk. You understand how your core infrastructure behaves — because you can inspect it.

What this means for your business


For decision makers evaluating Lerian, an open-by-design platform translates into concrete business benefits:
  • Source-code access: Midaz is source-available under Elastic License 2.0, so your team retains access to the ledger source code.
  • Third-party auditability: Your security team, auditors, or regulators can inspect the Midaz code directly.
  • Extensibility: Your engineers can inspect and extend Midaz to meet operational requirements.

Join the community


Building an open core only works when it is collaborative. Whether you are a developer, architect, or financial operator, you can:
  • Contribute code
  • Propose architectural improvements
  • Report issues
  • Build extensions and integrations
  • Share implementation patterns
We welcome practical contributions — not just discussions. Join our Discord community →