> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Open by design

> Understand why Lerian builds source-available financial infrastructure — transparency, independence, extensibility, and trust by design.

We believe financial infrastructure should be inspectable, extensible, and owned by those who operate it.

Source-available is not a positioning strategy for us. It is an architectural principle.

Midaz is open because financial systems require transparency, control, and long-term sustainability.

## Why Source-available?

***

Source-available creates structural advantages — not just community engagement.

By making our products open, we enable:

* **Transparency**: Every line of code is visible and auditable. No hidden logic. No opaque behavior.
* **Independence**: Institutions control their stack. No forced upgrades. No vendor lock-in.
* **Extensibility**: Teams can adapt the ledger to their regulatory, operational, and product requirements.
* **Trust by design**: Visibility reduces systemic risk. You understand how your infrastructure behaves — because you can inspect it.

## What source-available means for your business

***

For decision makers evaluating Lerian, source-available translates into concrete business benefits:

* **No vendor dependency**: If Lerian disappears tomorrow, you still have the code. Your operations continue
* **Third-party auditability**: Your security team, auditors, or regulators can inspect the code directly — no NDAs or trust-me-it-works conversations
* **Predictable costs**: No surprise license escalations. You know what you run and what you pay for
* **Talent flexibility**: Your engineers can debug, extend, and maintain the platform without waiting for vendor support tickets

## Join the community

***

Source-available 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 →](https://discord.lerian.studio/)