Trading strategies for multiple accounts

When you want to run the same trading strategy across many accounts, the first decision is how to design it. This post explains the two common design approaches, where each one works best, and the choice we suggest.

The two design approaches

One strategy instance per account

Here you build a strategy that is meant to run on a single account. To run it across many accounts, you start multiple copies of the same strategy, one copy per account.

One strategy for all accounts

Here you build the strategy so that a single copy can handle many accounts at once.

How to choose the right approach

Each approach has pros and cons. The right one depends on your specific setup, such as the language you code in and how complex your strategy is.

One strategy instance per account

Pros

• Keeps the code simple, so there is less complexity.
• Scales well. You can run it across many accounts.
  • Works well with high-level languages like C# or Java.
  • Not ideal for charting software such as AmiBroker or MetaTrader.

Cons

• New programmers can find this approach harder.
• Does not scale well on charting software.
  • The main reason is that charting software is hardware intensive. This makes sense, because graphics processing needs a lot of CPU.
  • For these tools, use options like scanners, which process faster.
• Starting many strategy instances across a lot of accounts can be a tiring job.
  • This is mainly a limit for charting software, which is not really a trading system.
  • A good trading system has a single start button (most of these are custom built).

One strategy for all accounts

Pros

• Easier for new programmers to code. For example, a feature like a group account maps internally to many trading accounts.
  • This is easy, but only for very simple strategies that mostly just place an order.
• Easy to manage on charting software, since you do not have to start many charts. This removes the work of setting strategy parameters on each chart.
• Needs less hardware, which helps with charting software.

Cons

• Debugging and investigating issues becomes harder.
• Not easy when the strategy is complex and involves things like order modification, order cancellation, or fund management.

Conclusion

Weigh the points above against your own use case and pick what fits.

If we have to recommend one, we will always say go with one strategy instance per account.

To plan the setup behind these strategies, see our guides on group accounts and the quantity multiplier, and the AmiBroker library setup if you trade from charting software.