> For the complete documentation index, see [llms.txt](https://docs.symm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.symm.io/exchange-builder-documentation/frontend-builder-introduction.md).

# Frontend Builder Introduction

Symmio is built for censorship resistance, so it provides the technical infrastructure for executing aMFQ peer-to-peer (p2p) symmetrical trades and doesn't host a frontend itself. It supplies the technology for these trades without using it to make markets or offer products to users.

To trade Symmio markets, use one of the [third-party frontend applications](https://symm.io/frontends).

### Business-to-business (B2B)

Symmio operates strictly business-to-business. The infrastructure is offered to developers and exchanges, so they can build on decentralized derivatives without handling the backend themselves.

If you're interested in launching a Symmio frontend and creating your own markets on the Symmio stack, see the [Profit Sharing Model](/exchange-builder-documentation/settlement-costs-in-symmio/perps-settlement-costs.md).

### Integrating with Symmio

Symmio gives you a full perpetual-exchange backend to integrate into an existing or new exchange. The functionality on the [Symmio demo frontend](https://cloverfield.exchange/trade/BTCUSDT) can be incorporated into your platform by forking the codebase under a Frontend Use Grant, or by using the Frontend SDK. For deployment details, see the Frontend Builder Technical Guidance.

This also avoids the liquidity fragmentation that comes with forking vAMM-based perps (e.g. GMX, Gains) or order-book-based ones (e.g. dYdX). Symmio routes to a large pool of institutionally-backed liquidity providers, called *Hedgers*, so liquidity is aggregated rather than fragmented.

Reach out any time for more information or support.

## Disclaimer

{% hint style="info" %}

#### Decentralized Frontend Applications <a href="#decentralized-frontends" id="decentralized-frontends"></a>

In our quest of making the system more decentralized and censorship-resistant. Symmio itself doesn't offer any trading or promote the trading of any derivatives; Symmio only provides the infrastructure for symmetrical peer-to-peer matchmaking; 3rd party providers can use that to build a fully functional on-chain derivatives exchange. Frontend Builders (Dealers and Market Makers) offer services directly via 3rd party services. To see their offering, make deposits, request trades, etc. Users thus have to use one of the frontends provided by third parties.​[ #https://symm.io/frontends](https://symm.io/frontends)

#### Which Frontend do I pick?  <a href="#which-frontend-do-i-pick" id="which-frontend-do-i-pick"></a>

Deciding which Frontend to use is a personal decision based on various factors, including UI, UX, features, tools, and the Frontend Operator's liquidity on the platform or offering of products and assets.​

#### List Disclaimer <a href="#list-disclaimer" id="list-disclaimer"></a>

Frontend Operators provide descriptions. The list of Frontend Operators is provided for informational purposes only. Neither is the list conclusive nor has Symmetry Labs AG conducted any due diligence on these operators. Accordingly, Symmetry Labs AG does not make any statement regarding technical functionality and the trustworthiness of the Frontend Operators listed below.&#x20;
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.symm.io/exchange-builder-documentation/frontend-builder-introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.