> For the complete documentation index, see [llms.txt](https://references.everstrike.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://references.everstrike.io/technical-architecture/off-chain-matching.md).

# Off-Chain Matching

Everstrike runs matching and risk engines off-chain. Clients connect through the Everstrike API.

### Order lifecycle

1. Submit an order through the Everstrike API.
2. The risk engine verifies that the order is well formed.
3. The risk engine verifies that your account meets margin requirements.
4. Valid orders enter the internal order book.
5. Immediately matching orders execute as trades.

Orders without an immediate match remain in memory until a match occurs.

### Matching priority

Everstrike uses first in, first out (FIFO) price-time priority.

Price determines the first level of priority. At the same price, earlier orders have priority over later orders. The oldest order at a price level executes first.

### API deployment locations

The Everstrike API runs in these Google Cloud Platform regions:

| Environment | Region  |
| ----------- | ------- |
| Mainnet     | Belgium |

{% hint style="info" %}
Market makers should place latency-sensitive infrastructure in the matching environment's region.
{% endhint %}

For the complete system model, see [Technical Architecture](/technical-architecture/technical-architecture.md).