Once you implement a strategy, you can launch it.

When creating a new instance of a strategy in the Control Panel, the following must be provided:

• Name of the C# class containing the strategy
• Strategy config containing the list of contracts the strategy trades, market data it uses, and parameters
• Type of the account on which the strategy will be executed:
  • Virtual account — a paper-trading account inside the platform. Results of the trading may be copied to one or several ESAs (Executable Subaccounts).
  • Strategy subaccount — a subaccount within some Broker Account configured in the platform.
• Accounts Service instance to host the account
• Strategies Service instance to host the strategy
  • There is 1:N link between AS and SS — multiple instances of Strategies Service can use one Accounts Service
  • Every Strategies Service can host one or several strategies

Deploying a new strategy requires restarting the respective Strategies Service.

States

A strategy can be in one of 4 states:

• Stopped
• Running
• Paused
  • Positions, if any, remain open, but Strategies Service doesn’t invoke any callbacks of the strategy
• Stopping
  • Strategies Service invokes the OnStopRequested callback and waits for the strategy to close all positions and confirm it is now stopped

Transition between states can be triggered from the Control Panel.

Strategy subaccounts and broker accounts

One broker account can host multiple strategies, each running on its own subaccount. A particular strategy operates within its subaccount and therefore sees only the orders and positions belonging to it.

A subaccount may be linked to one or several broker accounts. The latter is required if your strategy trades different contracts provided by different brokers. The contract specification defines which of the broker accounts an order will be routed to.

Once the broker account is determined, the platform will populate the order's BrokerAccountId property. All the orders from different strategies can be seen on the broker account.

<aside> 💡

Note: virtual orders (Stop, Market-if-touched, and synthetic contract orders) are not reflected in the broker account until the platform triggers them and sends them for execution.

</aside>