> 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/strategies.md). # Strategies A Strategy is code you upload, in Python or Pine Script. You backtest it, stress-test it and later deploy it to autotrade. A Strategy is your edge written as code. You upload it in Python or Pine Script, backtest it on real candles, stress-test it against a firm's rules and, once autotrade ships, deploy it to your accounts. The same code runs in backtest and simulation. {% hint style="info" %} **Coming soon:** autotrade and Pine upload. Python upload, versioning, backtesting and the simulator open with the alpha, for invited traders. {% endhint %} ## One interface, three uses Every strategy answers one question: given these candles, what signals do you give? The signals are enter long, enter short, exit long and exit short. Backtesting and simulation call the same function, and autotrade will too. ## Strategies are pure A strategy is not allowed to reach the network, read files, check the clock or use randomness. The same candles and parameters always give the same signals. That makes every backtest repeatable. ## Every upload is a version Each upload creates a new version. Backtests, simulations and deployments all point at a specific version, so a result can always be traced to the exact code behind it. ## Explore


Upload a Python strategy	Write to the Strategy API and upload.	Upload a Python strategy
Upload a Pine Script strategy	Translate a TradingView strategy.	Upload a Pine Script strategy
Backtest a strategy	Results in R, with parameter sweeps.	Backtest a strategy
Autotrade and the promotion ladder	How a strategy earns the right to trade.	Autotrade and the promotion ladder

## Next steps


Upload a Python strategy	Start with the Strategy API.	Upload a Python strategy
SurgeAI (coming soon)	Describe your edge and let the copilot draft it.	SurgeAI

--- # 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/strategies.md?ask=&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.