> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/tutorials/1.-welcome-to-surge.md). # 1. Welcome to Surge What Surge does, the five strategies, and how your keys stay safe. {% embed url="" %} Surge is a non-custodial automated trading platform for Cardano native assets. You set the rules once, and your strategies trade on-chain around the clock across Minswap, SundaeSwap, WingRiders and Splash. You never hand over your keys. ### What you'll learn * What Surge does and who it's for * The five strategies and when to use each * How Surge keeps you in control of your funds * How SURGE staking lowers your fees ### The five strategies | Strategy | What it does | | ---------- | ---------------------------------------------------------------------------------- | | Cadence | Builds or exits a position in many small, randomized trades across several wallets | | DCA | Buys or sells a fixed amount on a fixed schedule | | Arbitrage | Captures price gaps for the same token between DEXes | | Grid | Buys low and sells high on a ladder of levels inside a price range | | Rule-Based | Trades at price levels you draw on the chart | ### Why Surge * **Non-custodial.** Trades come from your own wallet or from hot wallets whose keys are encrypted in your browser. * **Guardrails.** Every strategy has limits such as loss caps, slippage, reserve floors and price bounds. * **Full audit trail.** You see every fee before and after a trade, and every transaction links to Cardanoscan. * **Lower fees with SURGE.** Holding SURGE earns ADA rewards every epoch and unlocks trading-fee discounts. ### Next [2. Connect your wallet and sign in](/tutorials/2.-connect-your-wallet-and-sign-in.md) --- # 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.surgecardano.com/tutorials/1.-welcome-to-surge.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.