Automation

Your rules, run the same way every day.

Describe a trade once: when to enter, which legs, how to work the order, when to get out. Check it, backtest it, then let it run on paper while you watch.

YAML algos

An algo is a short text file

A schedule, conditions on indicators such as VIX, legs chosen by delta, premium or offset, a combo order that walks from mid in steps, and exits: a stop as a multiple of the credit, take-profit, a time, or days in the trade.

The tester build ships sample drafts to start from: an iron condor, a put spread, and BTC and ETH ones.

Validate, Save, Backtest and Deploy from one tab; a deployed algo arrives paused.

A sample iron condor algo in YAML in the Draft tab, with Validate, Save, Backtest and Deploy, and the check passed.

sample-put-spread.yml, one of the drafts the tester build ships

algo: 1
name: Sample put spread
instrument: SPX
mode: copilot

schedule:
  zone: America/New_York
  days: [MON, TUE, WED, THU, FRI]
  at: { after-open: 20m }
  until: { after-open: 60m }
  skip: [holiday, early-close]
  max-open: 2
  max-per-day: 1

conditions:
  - { indicator: VIX, is: below, value: 30, max-age: 5m }

legs:
  - { name: sp, side: sell, ratio: 1, right: P, expiry: { dte: "1|3" }, strike: { delta: 0.20, tol: 0.02, widen: { by: 10%, every: 30s, max: 3 } } }
  - { name: lp, side: buy,  ratio: 1, right: P, expiry: { same-as: sp }, strike: { ref: sp, offset: -25 } }

order: { as: combo, start: mid, step: 0.05, every: 1m, max-steps: 5, cap: { past-mid: 50% }, cutoff: 15m }

exits:
  - { name: sp-tp,    scope: leg:sp,   take-profit: /4 }
  - { name: put-stop, scope: side:put, stop: { close-at: x3, of: side-credit } }

Build with AI

Say it in plain words, get a draft

Describe the trade the way you would to a colleague. Your own Claude Code or Codex, on your own machine, turns it into a YAML draft and runs the app's own check on it.

The assistant only reads the docs and the schema, lists your algos and validates. Saving, deploying and trading stay with you.

The assistant can read, list and validate. It cannot save, trade or change a mode.

Backtesting

Run it over past days first

Pick past days and run the draft against recorded or historical option prices. The result lists each day, each trade with its legs and exits, the P/L, and a journal of the run.

A backtest runs in a sandbox: nothing is sent to a broker.

Running algos

Auto, copilot or paused, per algo

Each algo has a mode: auto, copilot, paused or off. A fault stops new orders at the broker.

An algo decides once; its allocations decide how much each account takes: the capital, the most contracts per trade, a margin share, and on or off. Each entry is sized per account from them. Allocations for several accounts →

In copilot mode every entry waits for your Approve or Dismiss.

Private

Your algos are yours

Your algos are files on your own computer. We never see them, collect them or share them with anyone.

Your algos are private: never shared, never published.

Coming: algo marketplace

Publish an algo, only if you choose to

An algo marketplace is planned: a place where authors who choose to can publish their algos for others. It will be opt-in: nothing of yours is listed unless you publish it yourself. It is not available yet.

Coming later, opt-in. Not available today.

Algo API · coming

Code your own strategy

For strategies that do not fit in YAML, there is an algo API with Java and Rust/WebAssembly bindings. It is not open to testers yet; it comes later.

Not open to testers yet.