> 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/platform/platform.md).

# Platform overview

The Platform is the signed-in side of TradeSurge. You connect your prop accounts once, then prepare, execute, review and refine from one place.

The Platform is the signed-in side of TradeSurge at `app.tradesurge.co`. You connect your prop accounts once, then run one strategy across all of them from a single cockpit. This page is the map of every screen.

{% hint style="info" %}
**Early access.** The Platform opens first to invited traders, trading on Bybit demo accounts. Pages describe how each screen works.
{% endhint %}

## Start here

{% stepper %}
{% step %}

### Prepare

Connect your accounts and set each firm's rules and your risk per trade.
{% endstep %}

{% step %}

### Execute

Send one order to every account you select from the Terminal, each copy sized in R.
{% endstep %}

{% step %}

### Review

Read every account, trade and rule on the Dashboard and in the Journal.
{% endstep %}

{% step %}

### Refine

Backtest and stress-test your strategy, then scale it to more accounts.
{% endstep %}
{% endstepper %}

## Explore the Platform

<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>Accounts</strong></td><td>Connect venues, paste trade-scoped keys and set each account's phase.</td><td><a href="/platform/accounts.md">Accounts</a></td></tr><tr><td><strong>Rules &#x26; Limits</strong></td><td>Firm limits enforced before a trade fires, with Breach Guard on top.</td><td><a href="/platform/risk.md">Rules &amp; Limits</a></td></tr><tr><td><strong>Terminal</strong></td><td>One order, copied across selected accounts, sized in R for each.</td><td><a href="/platform/terminal.md">Terminal</a></td></tr><tr><td><strong>Dashboard</strong></td><td>Every account in one view, measured in R.</td><td><a href="/platform/dashboard.md">Dashboard</a></td></tr><tr><td><strong>Journal</strong></td><td>Every trade logged, tagged and grouped by playbook.</td><td><a href="/platform/journal.md">Journal</a></td></tr><tr><td><strong>Strategies</strong></td><td>Upload Python or Pine, backtest it and prepare it for autotrade.</td><td><a href="/platform/strategies.md">Strategies</a></td></tr><tr><td><strong>Simulator</strong></td><td>Test your own backtest results against a firm's rules.</td><td><a href="/platform/simulator.md">Simulator</a></td></tr><tr><td><strong>SurgeAI (coming soon)</strong></td><td>The copilot that will turn a plain-language edge into a strategy.</td><td><a href="/platform/surgeai.md">SurgeAI</a></td></tr><tr><td><strong>Telegram</strong></td><td>Breach, fill and recap alerts on your phone.</td><td><a href="/platform/telegram.md">Telegram</a></td></tr></tbody></table>

## 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>Connect Bybit</strong></td><td>Add your first account step by step.</td><td><a href="/platform/accounts/connect-bybit.md">Connect Bybit</a></td></tr><tr><td><strong>Place an R-sized trade</strong></td><td>Send your first order from the Terminal.</td><td><a href="/platform/terminal/place-a-trade.md">Place an R-sized trade</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/platform/platform.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.