> For the complete documentation index, see [llms.txt](https://guida-2.gitbook.io/guida-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guida-2.gitbook.io/guida-docs/getting-started/going-live.md).

# Going Live

Once you've built a strategy and proven it through backtesting and paper trading, the final step is to put it to work. This page explains how deployment and 24/7 automation function — and how you stay firmly in control.

> **In early access, "going live" means running on live market data with simulated funds.** Real-capital execution is a later release. The mechanics below describe how automation works in both cases.

## Setting your guardrails

Before a strategy activates, you confirm the limits it must operate within:

* **Maximum spend** — the total capital the strategy is ever allowed to commit.
* **Position size** — how much it puts into any single trade.
* **Stop-loss** — the loss level at which a position is automatically exited.
* **Take-profit** — the gain level at which profits are automatically secured.
* **Expiry** — an optional date after which the strategy stops itself.

Guida will never act outside these boundaries. Think of them as the walls of the sandbox your agent plays in.

## What happens when it's live

Once activated, your strategy runs continuously. Guida:

1. **Monitors** the relevant markets around the clock — including nights and weekends.
2. **Evaluates** your conditions against live data, moment to moment.
3. **Acts** the instant your rules are met — entering, exiting, or adjusting positions.
4. **Records** every action, so your dashboard always reflects exactly what happened and why.

This is the core value of automation: it removes hesitation, emotion, and the need to be awake. Your strategy executes with the same discipline at 4 a.m. on a Sunday as it would at midday on a Monday.

## Staying in control

Automation should never mean loss of control. At any time you can:

* **Pause** a strategy to temporarily halt new actions.
* **Adjust** its rules or limits.
* **Stop** it entirely.
* **Review** its full history and current positions from the [dashboard](/guida-docs/features/dashboard.md).

Nothing happens that you didn't authorize through the rules and limits you set. Guida is an executor of *your* strategy, not an independent actor.

## Monitoring your strategy

A live strategy isn't "set and forget forever." Good practice is to:

* **Check in periodically** to confirm it's behaving as expected.
* **Watch for regime changes** — markets that behave very differently from the conditions you tested in.
* **Review and iterate.** Retire strategies that no longer make sense; refine ones that do.

The goal is a portfolio that works for you continuously, with you supervising the strategy rather than executing every trade by hand.

***

**Next:** Deepen your understanding with [Core Concepts →](/guida-docs/core-concepts/concepts.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guida-2.gitbook.io/guida-docs/getting-started/going-live.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.