> For the complete documentation index, see [llms.txt](https://quantinfra.gitbook.io/quantinfra-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quantinfra.gitbook.io/quantinfra-docs/core-concepts/strategies-and-accounts.md).

# Strategies and accounts

<figure><img src="/files/fEINpScHyoaFi9gibWuu" alt=""><figcaption></figcaption></figure>

## Strategies

**Trading Strategy:** An independent instance of trading logic that runs on its own account. Strategies are written using the C# API. When deploying, the parameters are configured for this particular instance of the strategy, so the code can be reused across different contracts or parameter sets. Each strategy runs on its own subaccount, where orders, trades, positions, and performance are tracked independently.

**Execution Strategy:** Handles signals generated by a trading strategy and aligns the real position on the strategy’s account with the desired position.

## Execution modes

**Strategy Subaccount (SSA):** A trading strategy that places orders directly onto the broker (through a unified API) and handles execution logic (including order rejections and reconciliations).

**Executable Subaccount (ESA):** A trading strategy trades on a virtual account (a paper trading account inside the platform). One or more ESAs may be subscribed to a single strategy. Any trade executed on the trading strategy’s account is processed by an Execution Strategy that implements some specific execution rules (e.g., simple market order vs. a TWAP). Different ESAs can use different Execution Strategies and different execution parameters.

## Account types

**Broker accounts:** Multiple SSAs and ESAs used by different strategies can use the same broker account. A single strategy can be traded on multiple broker accounts if it uses different contracts. A broker account maintains its state in accordance with the trading account state on the execution venue and handles reconciliations. It automatically forwards execution and trades to the strategies’ subaccounts.

**Fund accounts:** Combine strategies in defined proportions into funds to manage overall risk and exposure. Funds also help automate AUM management: whenever a fund's investment changes, the change is propagated to its strategies, which can automatically adjust their positions.

**Client Subaccounts:** A fund may be subdivided into subaccounts, each of which tracks the investment and performance of a particular client. If configured accordingly, clients may access reports for their subaccounts via the Client Portal.


---

# 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://quantinfra.gitbook.io/quantinfra-docs/core-concepts/strategies-and-accounts.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.