> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/concepts-and-reference/built-for.md).

# What TradeSurge is built for

What TradeSurge is designed to do, and the limits we state out loud.

TradeSurge is built for traders who already have an edge and want to run it across more funded accounts. It removes the operational work around trading. It does not replace your judgment, and it does not create an edge you do not have.

## What it is built for

* Running one strategy across three or more prop accounts from one cockpit.
* Sizing every copy of a trade in R, per account.
* Enforcing each firm's drawdown and target rules before a trade fires.
* Reviewing every account in one place, in R.
* Turning a strategy into code you can backtest, stress-test and later automate.

## What it is not built for

| Name                    | What it means                                              |
| ----------------------- | ---------------------------------------------------------- |
| **Finding you an edge** | TradeSurge scales an edge. It does not supply one.         |
| **Signals or advice**   | We do not tell you what to trade.                          |
| **Beating firm rules**  | We enforce firm rules. We do not help you get around them. |
| **Moving funds**        | Keys that can withdraw or transfer are refused.            |
| **Guaranteed passes**   | The simulator is a model, not a promise.                   |

## Limits during alpha

{% hint style="warning" %}

* Bybit demo opens first, to invited traders.
* MetaTrader 5 and MatchTrader are not connectable yet.
* Autotrade is coming soon. Strategy upload and backtesting open with the alpha.
* Invite-only while in alpha.
  {% endhint %}

## What safety does not remove

Resting stops, Breach Guard and circuit breakers reduce risk. They do not remove it. Fast markets can slip past a stop, and a venue outage can delay an exit. A firm can change its rules faster than we update them.

## Firm policies come first

Some firms forbid copy trading, bots or trading from shared IPs. TradeSurge refuses copy and autotrade on firms that forbid them, and warns you before copying across firms. Reading and following each firm's terms is still your responsibility.

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Supported venues and firms</strong></td><td>Which venues open first.</td><td><a href="/getting-started/supported-venues-and-firms.md">Supported venues and firms</a></td></tr><tr><td><strong>How order safety works</strong></td><td>The checks every order passes.</td><td><a href="/concepts-and-reference/order-safety.md">How order safety works</a></td></tr></tbody></table>


---

# 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.tradesurge.co/concepts-and-reference/built-for.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.