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

# Get Started

> Explore our guides to implement, configure, and operate Levery securely.

<Frame>
  <img style={{ borderRadius: "0.5rem" }} src="https://mintcdn.com/levery/6C5ksHgEFzZe_XUM/images/levery-home-dark.jpg?fit=max&auto=format&n=6C5ksHgEFzZe_XUM&q=85&s=6a6071c5f46f19c3bd3359f478b15f0c" alt="Levery Account Dashboard" className="block dark:hidden" width="2880" height="1800" data-path="images/levery-home-dark.jpg" />

  <img style={{ borderRadius: "0.5rem" }} src="https://mintcdn.com/levery/6C5ksHgEFzZe_XUM/images/levery-home-dark.jpg?fit=max&auto=format&n=6C5ksHgEFzZe_XUM&q=85&s=6a6071c5f46f19c3bd3359f478b15f0c" alt="Levery Account Dashboard" className="hidden dark:block" width="2880" height="1800" data-path="images/levery-home-dark.jpg" />
</Frame>

# Introduction

Levery is a **compliance-first, white-label DeFi exchange stack** designed for regulated institutions that want to
offer on-chain markets without rebuilding core trading infrastructure, access controls, and operational guardrails
from scratch.

***

## Levery core capabilities

Levery bundles everything a regulated Virtual Asset Service Provider (VASP) needs to run a branded DeFi trading venue.

The stack provides a complete environment, aligned with the institution’s brand and policies, incorporating the controls
and interfaces required by risk, compliance, treasury, and operations teams.

<CardGroup cols={2}>
  <Card title="White-Label Client Platform" icon="store">
    Admitted customers interact through a fully branded user interface within a streamlined trading and portfolio view.
  </Card>

  <Card title="Institution Admin Console" icon="shield-halved">
    The console handles KYC/KYB review and wallet admission, asset policies, real-time monitoring and management of user
    permissions.
  </Card>

  <Card title="Liquidity Pool Creation" icon="droplet">
    Through the console, the institution configures and launches permissioned pools and can allocate ring-fenced house
    liquidity.
  </Card>

  <Card title="Access Control" icon="user-check">
    All client entities must complete KYC/KYB to join the venue. Once approved, designated wallets are admitted and linked
    to the legal entity.
  </Card>

  <Card title="Pre-Trade Checks" icon="gavel">
    Before any swap or liquidity action, policies are checked by the smart contracts ensuring consistent, audit-ready
    enforcement.
  </Card>

  <Card title="Post-Trade Records" icon="receipt">
    Each action emits standardized, timestamped events that populate client statements and operator dashboards.
  </Card>

  <Card title="API Integration" icon="code">
    Secure, well-documented APIs for deep integration with banking systems, compliance engines, reporting tools, and
    client portals.
  </Card>

  <Card title="Monitoring Dashboard" icon="chart-line">
    A comprehensive monitoring and audit dashboard gives operations, compliance, and risk teams real-time visibility into platform activities.
  </Card>
</CardGroup>

<Note>
  This documentation explains **how Levery works** and **how to integrate and operate it**. It’s not legal advice.
  Always validate requirements with your compliance and legal teams for your jurisdiction.
</Note>

***

## Design principles

Levery is engineered around a set of architectural principles that keep policy, risk controls, and operational
responsibilities explicit, enforceable, and auditable across every market and participant.

<CardGroup cols={1}>
  <Card title="Permissioned AMM Engine" icon="shield-check">
    Before any state change, Levery runs on-chain admission and risk checks. Non-compliant calls revert deterministically
    with clear reasons; compliant actions execute normally, so that only authorized accounts can access pools and add or
    remove liquidity.
  </Card>

  <Card title="Auditable On-chain Execution" icon="file-lock">
    There is no third-party custody or intermediation in the execution path, assets move under the control of smart
    contracts. Code and state are immutable once deployed, execution is deterministic across validators, and every state
    transition is recorded on the ledger, producing a tamper-evident audit trail.
  </Card>

  <Card title="Oracle-Guided Dynamic Fees" icon="chart-line">
    Levery integrates market-price oracles to support fair pricing and dynamic fee calculations. The engine monitors
    oracle-to-pool divergence, adjusting fees in real time to anchor execution to an external reference while balancing
    competitive pricing with liquidity-provider protection.
  </Card>

  <Card title="Non-Transferable Positions" icon="fingerprint">
    Liquidity positions are tokenized as special ERC-721 that are non-transferable, binding each position to its verified
    owner. This design enforces KYC/KYB status across the entire LP lifecycle, prevents unauthorized transfers, and
    simplifies compliance reporting.
  </Card>

  <Card title="Administrative Controls" icon="sliders">
    On-chain administration functions allow institutions to update administrators, adjust fee parameters globally or per
    pool, update oracle references, and reset the permission manager when required by procedure.
  </Card>

  <Card title="Configurable Service Fee" icon="users-gear">
    A programmable service fee routes to a secure vault, enabling transparent treasury and revenue-sharing models.
    Accruals and distributions are executed by contract and recorded on-chain, giving teams clear accounting.
  </Card>
</CardGroup>

The result is a DEX-like experience that can be operated with the rigor expected in financial services: on-chain markets
with explicit rules, verifiable controls, and native evidence for reconciliation, audit, and continuous oversight,
without relying on trust in intermediaries or manual off-chain processes.

***

## Key concepts you’ll see everywhere

These concepts are the “language” of Levery. Getting comfortable with them early makes the rest of the docs much easier.

| **Concept**      | **Definition**                                                                                                      |
| ---------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Accounts**     | Wallets linked to a user or entity, used for trading and liquidity actions.                                         |
| **Policies**     | Rules that govern which actions are allowed (trade, provide liquidity, access pools) based on identity and context. |
| **Assets**       | Tradable instruments with metadata (decimals, symbols), pricing sources, and risk flags.                            |
| **Pools**        | Permissioned markets that define the trading pair, fee behavior, and policy boundaries.                             |
| **Positions**    | Liquidity positions with defined ownership, lifecycle events, and auditable outcomes.                               |
| **LP fees**      | Fees paid by traders into a pool and accrued to liquidity providers under market-specific fee rules.                |
| **Service fees** | Protocol/operator fees charged according to configuration, with traceable accounting.                               |
| **Oracles**      | Optional on-chain feeds (market price) used to inform fee logic and risk controls depending on pool setup.          |

<Tip>For a complete list of definitions, see **[Glossary](/glossary).**</Tip>

***

## Security audit

Levery’s smart-contract suite is audited by Runtime Verification, a Chicago-based security audit firm globally
recognized for more than a hundred publications and tools that shaped the field. Active in blockchain security since
2017, the team has served high-TVL protocols including Ethereum, Uniswap, Lido, Maker, and Optimism.

The mission was to move beyond code review and establish whether critical properties hold in all admissible executions,
using mathematically grounded techniques in addition to conventional analysis.

<Tip>
  For a deeper view into Levery’s security model, controls, and assurance posture, see **[Security](/security).**
</Tip>

***

## Next steps

Choose your path based on your role and what you need next:

<CardGroup cols={3}>
  <Card title="What is Levery" icon="layer-group" href="/what-is-levery">
    Product overview, key differentiators, and institutional digital asset stack.
  </Card>

  <Card title="Architecture" icon="diagram-project" href="/architecture">
    A technical view of on-chain components and end-to-end flow.
  </Card>

  <Card title="Security" icon="shield-check" href="/security">
    Review Levery’s security posture and the smart-contracts audit report.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Institutional Deployments" icon="server" href="/institutional-deployments">
    Single tenant deployment options for regulated institutions with trust boundaries and strong governance.
  </Card>

  <Card title="End-User Guide" icon="book-user" href="/end-user/onboarding">
    How customers onboard, connect accounts, trade, invest, and manage assets and positions.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Common Questions" icon="circle-question" href="/end-user/common-questions">
    Operational FAQ for end users of the institution’s venue instance.
  </Card>

  <Card title="Glossary" icon="spell-check" href="/glossary">
    Core concepts and terminology used across the platform.
  </Card>
</CardGroup>
