A crypto exchange backend is the set of systems behind the trading screen. It creates and configures markets, accepts and matches orders, checks risk, tracks balances, and settles trades. The frontend is the interface that users see and trade through. Every exchange needs both, but they do not have to come from the same team: a venue can run its own frontend on top of a backend it does not operate itself.
Last updated: October 27, 2026.
What does the backend include?
| Component | What it does |
|---|---|
| Market setup | Creates markets and sets their rules, such as assets, price increments, and fees |
| Matching engine | Keeps the order book and pairs buy and sell orders |
| Risk engine | Checks margin and collateral before accepting orders, and triggers liquidations |
| Price feeds | Bring in reference prices from oracles or index providers |
| Ledger | Tracks deposits, withdrawals, positions, and balances for every account |
| Clearing and settlement | Works out what each side owes and moves the assets, offchain, onchain, or both |
| APIs and data | Let frontends, market makers, and trading systems send orders and read market data |
Not every venue has every part. A spot market without leverage needs only balance checks from a risk engine, while a derivatives market depends on it for margin and liquidations.
What does it take to create or modify a market?
Creating a market means defining what is traded and the rules that apply. That covers the base and quote assets, the price feed, the smallest price step and order size, and the fees. For perpetual futures, it also covers margin requirements, leverage limits, and funding rules, which push the contract price toward the reference price.
Modifying a market means changing those settings on a live market, or pausing or closing it. On an onchain venue, these settings usually live in smart contracts or in the chain's own state, so a change goes through whatever admin permissions or governance process the venue defines.
Do you need both a frontend and a backend?
Yes, but someone else can provide either one. The backend enforces the rules and keeps the records. The frontend is how users see markets and place orders. It can be a website, an app, or another party's interface that calls the backend's API. One backend can serve several frontends, and some venues offer only an API, so traders connect through their own software.
How does an onchain backend differ?
On a fully onchain venue, matching, risk checks, and settlement run as smart contracts or as part of the chain itself, so every order and trade is recorded onchain. In a hybrid design, matching runs offchain for speed while balances and settlement stay onchain. The guide to order books and AMMs compares the two main ways trades are matched.
FAQ
Is the matching engine the same as the backend?
No. The matching engine is one part of the backend. It pairs orders, while other parts handle markets, risk, balances, and settlement.
What is the difference between clearing and settlement?
Clearing works out what each party owes once a trade is confirmed. Settlement is the final transfer of the assets and the payment. The guide to post-trade for tokenized assets explains how the steps connect.
Can one backend run spot and derivatives markets?
Yes, if its risk engine and ledger support both. Derivatives need margin and liquidation logic that spot markets do not, and perpetual futures also need funding payments.
Build trading across chains
For tools to build applications that work across chains, see LayerZero developer resources.