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

# Getting started

> Begin with Lerian — evaluate the platform, choose a deployment model, and run your first double-entry transaction with Midaz to see the ledger in action.

Whether you want to evaluate the platform or start building, this is the place to begin.

<Note>
  **New to core banking?** If terms like *Ledger*, *debit and credit*, or *chart of accounts* aren't yet second nature, start with the fundamentals first — they'll make everything here click into place.

  **[Begin with Core Banking Fundamentals](/en/fundamentals/core-banking/what-is-core-banking)**
</Note>

## Evaluating the platform

***

Follow these steps to understand the platform's capabilities, architecture, and deployment options.

<Steps>
  <Step title="Understand why Lerian exists">
    Learn what problems the platform solves and who we built it for — in business terms.

    **[Why Lerian →](/en/why-lerian)**
  </Step>

  <Step title="Explore the architecture">
    Lerian organizes around four pillars — **Ledger**, **Transactional Services**, **Governance**, and **Connectivity** — that form a composable financial platform.

    **[Read the Core Banking vision →](/en/core-banking-vision)**
  </Step>

  <Step title="Choose a deployment model">
    Decide between Lerian Cloud (SaaS), fully managed by Lerian, or self-hosted BYOC based on your compliance requirements and operational maturity.

    **[Compare deployment models →](/en/deployment-models)**
  </Step>

  <Step title="See it in action">
    Explore real-world use cases — digital banking, global portfolios, Pix, marketplace payouts, and more.

    **[Browse use cases →](/en/midaz/use-cases)**
  </Step>
</Steps>

## Building with Lerian

***

Follow these steps to go from zero to your first double-entry transaction. Choose the path that matches your deployment model.

<Tabs>
  <Tab title="SaaS (Lerian Cloud)">
    <Steps>
      <Step title="Receive your credentials">
        Your Lerian onboarding team provides you with API credentials (client ID and secret) and the base URL for your environment.
      </Step>

      <Step title="Authenticate and get your token">
        Use the Access Manager Auth API to exchange your credentials for a JWT access token. This token contains your tenant context — you don't need to manage a tenant ID explicitly.

        **[Learn how to authenticate →](/en/platform/access-manager/using-access-manager)**
      </Step>

      <Step title="Make your first API call">
        Include the token as a Bearer token in the `Authorization` header of every request. Your calls are automatically scoped to your tenant.

        **[Make your first API call →](/en/reference/quick-start-guide)**
      </Step>

      <Step title="Create your first organization">
        Follow the same API flow as any Midaz deployment — create an organization, a ledger, assets, and accounts. The platform handles tenant isolation transparently.

        **[Follow the recommended workflow →](/en/midaz/recommended-workflow)**
      </Step>
    </Steps>

    <Tip>
      The API surface is identical across deployment models. Lerian Cloud and BYOC Multi-Tenant require a Bearer token and scope requests to the authenticated tenant. A permitted non-production BYOC Single-Tenant deployment can have authentication disabled. Learn more about [multi-tenancy](/en/multi-tenancy).
    </Tip>
  </Tab>

  <Tab title="BYOC (self-hosted)">
    <Steps>
      <Step title="Choose your deployment model">
        Decide how you want to run the platform. BYOC gives you full control over data, security, and networking — in your own cloud or on-premises.

        **[Compare deployment models →](/en/deployment-models)**
      </Step>

      <Step title="Understand the architecture">
        Lerian organizes around four pillars — **Ledger**, **Transactional Services**, **Governance**, and **Connectivity** — that form a composable financial platform. Understanding this helps you model integrations correctly from day one.

        **[Read the Core Banking vision →](/en/core-banking-vision)**
      </Step>

      <Step title="Install Midaz">
        Midaz is Lerian's double-entry core ledger. Install it when you need to model accounts and record transactions; other products remain modular and can be adopted independently.

        **[Install Midaz →](/en/midaz/midaz-setup)**
      </Step>

      <Step title="Create your first resources through the API">
        With Midaz running, create the essential building blocks: an organization, a Ledger, assets, and accounts.

        **[Make your first API call →](/en/reference/quick-start-guide)**
      </Step>

      <Step title="Follow the recommended workflow">
        Move beyond isolated API calls and follow the end-to-end operational workflow — from resource setup to transaction routing and balance management.

        **[Follow the recommended workflow →](/en/midaz/recommended-workflow)**
      </Step>
    </Steps>
  </Tab>
</Tabs>

## What's next?

***

With your Ledger running and your first transactions created, pick the capability you want to add next.

<CardGroup>
  <Card title="Reconcile transactions" icon="code-compare" href="/en/matcher/getting-started/matcher-quick-start" cta="Try Matcher">
    Run your first automated reconciliation between a bank statement and your Ledger.
  </Card>

  <Card title="Validate in real time" icon="shield-check" href="/en/tracer/getting-started" cta="Try Tracer">
    Set up spending limits and validation rules to evaluate transactions before they proceed and return an ALLOW, DENY, or REVIEW decision for your authorization flow to act on.
  </Card>

  <Card title="Generate reports" icon="file-chart-pie" href="/en/reporter/using-reporter" cta="Try Reporter">
    Create a report template and generate your first financial report from a configured data source. For Midaz data, connect Reporter to Midaz first.
  </Card>
</CardGroup>