Borsa

Strategies

Build browser-executed strategy flows with rule-based entry and optional exit logic.

The Strategy Builder lets you combine market selection, entry side, TWAP entry pacing, entry conditions, optional exit logic, and repeating behaviour into one configuration. It is a starting point: on Create in Studio the builder compiles your inputs into a Strategy Studio node graph and opens it there to refine and run. The builder no longer creates a standalone "quick" strategy that runs on its own — Studio is where strategies execute.

Info

This is separate from the order form's native TWAP, Scale, Burst, and ALO order types. Those are built-in order types that execute directly and are unchanged — only the builder's "create a saved conditional strategy" output now produces a Studio graph.

Strategy creation area

When the Builder Is Useful

The builder is useful when you want to:

  • Wait for a rule-based entry condition instead of clicking in manually.
  • Distribute entry execution over time with TWAP chunking.
  • Attach an optional exit plan to the same lifecycle.
  • Repeat a process through Loop Mode.

…without composing a node graph from scratch. The builder translates these intentions into a Studio graph you can then tune.

From Builder to Studio

A typical flow looks like this:

  1. Configure the strategy in the builder (market, entry side, conditions, TWAP pacing, optional exit).
  2. Create in Studio — the builder compiles the configuration into a node graph, adds it to your Studio library, and opens it.
  3. Refine the graph in Studio: resolve any approximated bits flagged with amber note nodes, then backtest, paper, or run it live.
  4. Run it from Studio or from the order form's Pro menu, which auto-lists every executable Studio strategy — see Strategy Frontends.

For the step-by-step builder workflow, see Strategy Builder Flow. For ready-made ideas, see Strategy Examples. For everything Studio can do, see Strategy Studio.

Loop Mode

Loop Mode is configured in Entry Conditions.

In practical terms:

  • Without Loop Mode, the strategy behaves like a single lifecycle: monitor, enter, optionally exit, then finish.
  • With Loop Mode, the strategy is meant to re-run the full entry and exit cycle on completion until a stop condition is reached.

Loop "max iterations" is one of the inputs the builder can only approximate in the compiled graph — it is flagged with an amber note node so you can wire the repeat/stop behaviour explicitly in Studio. Use Loop Mode when you want repeat behaviour, but monitor aggregate exposure carefully across manual positions, open orders, and active strategy runs.

Runtime Requirement

Warning

Compiled strategies run in Strategy Studio, in the browser while the app tab stays open. Closing the tab or leaving the app stops the engine. Switching to another tab or minimizing the window does not pause a running strategy—the engine uses a Web Worker heartbeat so timers keep firing in the background (unlike ordinary page timers, which browsers throttle). Studio runs also survive navigating away from /studio and are observable from the /strategies tab.

Running Multiple Strategies

You can run multiple strategies at the same time, including strategies with different entry conditions, exit conditions, execution intervals, and order types.

Always review exposure across:

  • Manual positions
  • Open orders
  • Active strategy runs (entries and exits)
  • Any repeating strategies using Loop Mode