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. Under the hood, Levery combines:- Deterministic, on-chain enforcement (permissioned pools, policy checks, and configurable fee behavior)
- Institutional operations (audit-ready receipts, monitoring, reporting, and admin controls)
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.
Choose your path
What is Levery
Product overview, key differentiators, and institutional digital asset stack.
Architecture
A technical view of on-chain components and end-to-end flow.
Security
Review Levery’s security posture and the smart-contracts audit report.
End-User Guide
How customers onboard, connect accounts, trade, invest, and manage assets and positions.
Admin Guide
How operators configure policies, users, roles, assets, pools, and day-to-day controls.
API Documentation
Authentication, conventions, and the structure of Levery’s APIs.
Glossary
Core concepts and terminology used across the platform.
Changelog
Version history and notable changes.
What you can do with Levery
Levery is built to help institutions ship production-grade on-chain markets with a clear separation of concerns.Launch a branded exchange experience
Deliver a web or embedded interface for spot swaps and liquidity with your own brand, UX, and customer journey.
Enforce policies on-chain
Apply access rules by user, asset, pool, and jurisdiction — with clear enforcement boundaries and auditable
outcomes.
Operate with institutional rigor
Use receipts, logs, monitoring, and incident controls designed for auditability and daily operations.
Integrate into existing workflows
Connect Levery to your identity, risk, and reporting stack (KYC/KYB, AML, approvals, and internal controls).
How Levery works in 60 seconds
A practical mental model you can keep in your head while reading the rest of the docs:- Onboard users (individuals or institutions) and attach the right compliance profile.
- Configure policies (who can trade, what can be traded, and where).
- Trade & invest using permissioned pools with deterministic enforcement and traceable results.
- Oversee activity through operator dashboards, receipts, and reporting pipelines.
Components at a glance
Levery is a stack. You’ll see these layers referenced throughout the docs:On-chain enforcement
Permissioned pools and hook-based policy checks. Fee behavior can be configured per pool and may incorporate oracle
inputs.
Off-chain services
Indexers and APIs that transform canonical on-chain activity into queryable, audit-ready operational data
(positions, swaps, fees, balances).
Operator & user interfaces
A user-facing trading experience plus an admin console for policies, users, assets, pools, and operational controls.
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 or institutional accounts 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, hooks, fee behavior, and policy boundaries. |
| Positions | Liquidity positions with defined ownership, lifecycle events, and auditable outcomes. |
| Service fees | Optional protocol/operator fees charged according to configuration, with traceable accounting. |
| Oracles | Optional price/reference feeds used to inform fee logic and risk controls depending on pool setup. |
| Indexers | Services that ingest canonical events and produce operational datasets (TVL, volume, fees, history). |
/glossary).
Security posture
Levery is designed for environments where security and compliance are non-negotiable:- Deterministic enforcement boundaries: rules are applied consistently where they matter.
- Audit-ready data: events and outcomes are represented in a way that supports oversight and reporting.
- Operational controls: configuration and policy changes are designed to be observable and governable.
Security
Threat model, trust boundaries, and operational recommendations.
Architecture
The system diagram and end-to-end data flow.
Next steps
Pick the next page based on what you’re trying to do:- Evaluating Levery → start with What is Levery and Architecture
- Operating Levery → jump to the Admin Guide
- Integrating Levery → start with API Documentation (
/api-reference/introduction), then see the endpoint examples - Using the product → follow the End-User Guide