> ## 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.

# Solutions

> Problem-first entry points that name the Lerian products which solve each need.

A solution starts from the problem you must solve, not from a product name. A solution page states the need, then names the Lerian products that meet it.

Solutions group the catalog by the problem you solve: core banking, payment rails, reconciliation, loan management, and orchestration. The five solutions draw on one platform, and the pieces combine differently in each.

## The five solutions

***

<Columns cols={2}>
  <Card title="Core banking" icon="vault" href="/en/solutions/core-banking">
    Run accounts, transactions, and regulatory reporting on a ledger you own, with the controls your regulator expects.
  </Card>

  <Card title="Payment rails" icon="money-bill-transfer" href="/en/solutions/payment-rails">
    Reach Brazil's payment systems through Lerian-owned messaging to BACEN, or through a connectivity partner.
  </Card>

  <Card title="Reconciliation" icon="scale-balanced" href="/en/solutions/reconciliation">
    Match your own records against banks, PSPs, and ERPs without spreadsheets, and close the month with an audit trail.
  </Card>

  <Card title="Loan management system" icon="hand-holding-dollar" href="/en/solutions/loan-management-system">
    Run the full credit journey, from product definition through origination and servicing, with payroll-loan connectivity for Brazil.
  </Card>

  <Card title="Orchestration engine" icon="diagram-project" href="/en/solutions/orchestration-engine">
    Coordinate the checks and approvals around a transaction, with a step-level record of what ran and what it returned.
  </Card>
</Columns>

Each solution combines products that you can also adopt one at a time.

## One platform, five compositions

***

The same pieces appear in more than one solution, and each solution gives them a different job.

| Piece          | Core banking                    | Payment rails                      | Reconciliation                 | Loan management system      | Orchestration engine       |
| -------------- | ------------------------------- | ---------------------------------- | ------------------------------ | --------------------------- | -------------------------- |
| Midaz          | the ledger                      | records partner-interface postings | exported as a source           | receives loan postings      | the `ledger` provider      |
| Tracer         | decision before the ledger      | —                                  | —                              | —                           | the `tracer` provider      |
| Reporter       | reports from ledger data        | renders the CCS file               | —                              | —                           | —                          |
| Matcher        | compares the ledger to banks    | —                                  | the reconciliation engine      | verdicts reach Lender       | —                          |
| Lender         | —                               | —                                  | —                              | the credit journey          | —                          |
| Flowker        | —                               | —                                  | —                              | —                           | the orchestration platform |
| Brazil Rails   | —                               | messaging to BACEN                 | settlement extracts as sources | Consignado CLT (Dataprev)   | —                          |
| Interfaces     | —                               | the product surface                | —                              | —                           | —                          |
| Access Manager | tokens each service trusts      | tokens for partner plugins         | —                              | tokens for the ledger relay | webhook trigger permission |
| Console        | Midaz, Reporter, Tracer modules | Bank Transfer and Payments plugins | —                              | —                           | the Flowker module         |
| Streaming Hub  | ledger and Tracer facts         | CCS and SCR deliveries             | Matcher facts out              | Lender and Consignado facts | —                          |

Midaz carries a job in every column. Reporter, Matcher, and Flowker work with Midaz or with another ledger. None of them depends on Midaz. A dash means the piece has no documented role in that solution.

## Adopt one piece at a time

***

* Lerian does not pre-wire the pieces in a self-hosted deployment. You connect them in a setup step, and you can adopt a product on its own.
* When you compose the full stack, bring it up in order: Midaz, then Access Manager, then the products and interfaces, then the Console.
* Reporter, Matcher, and Flowker do not depend on Midaz. Point them at the ledger you already run.
* Lender originates a first loan with no Midaz and no event broker. Its postings wait in a durable outbox until you configure the ledger.
* CRM and the Fees Engine run inside the Midaz ledger process. There is no separate service to deploy.

## Where to go next

***

<Columns cols={3}>
  <Card title="Products" icon="https://mintcdn.com/lerian-49cb71fc/47c4N7ZVIXfTkwUf/images/icons/core-banking-yellow.png?fit=max&auto=format&n=47c4N7ZVIXfTkwUf&q=85&s=05a04a8e503c01720a0d7e20fdd752ef" href="/en/about-products" width="1250" height="1250" data-path="images/icons/core-banking-yellow.png">
    Read what each product, platform service, rail, and interface does on its own.
  </Card>

  <Card title="Building a complete core banking" icon="vault" href="/en/building-a-complete-core-banking">
    See what connects to what, and how much of the wiring you do yourself.
  </Card>

  <Card title="Deployment models" icon="cloud" href="/en/deployment-models">
    Compare Lerian Cloud against running the platform in your own cloud.
  </Card>
</Columns>