Product · Scripting

Your idea, in twenty lines,
on the chart tonight.

An editor inside the app, a sandbox that runs your code with no network and no file access, and the footprint data — bid, ask, delta per level — as the input. Indicators draw on the chart; strategies drive the simulated account, the replay or — once you arm it — the optional autopilot.

Download for Windows$9 first month
senzoukria — Scripting● SIMULATION
Three languagesJavaScript runs belowPython runs belowJavaScript and Python execute here, in the app’s sandbox. C++17 is compiled by a real Clang to WebAssembly inside the desktop app — a 30 MB toolchain that stays there. Its two default scripts are shown as they compile.

The editor as it is in the app. Edit the code, press Run — the sandbox executes it here, in your browser.

What it gives you

  • 01JavaScript, Python or C++Python on a bundled interpreter, C++17 compiled by Clang to WebAssembly — no install, no venv
  • 02Footprint as inputBid and ask per price level, delta, imbalances — not just OHLC
  • 03A real sandboxNo network, no files, no app API. Two seconds per run, then it is killed
  • 04StrategiesDecide on bar close; backtest JS and Python with walk-forward; arm the optional autopilot yourself on a compatible Rithmic account
  • 05Six templatesEMA ribbon, session CVD, imbalances, range levels, volatility, breakout
  • 06An assistant that reads codePaste a screenshot or ask for a change — it answers with a block you can apply
Before you install

Questions, answered

Everything we get asked twice. Anything else — ping us.

Yes. It is the same editor and the same sandbox worker as the desktop app, running in your browser. Press Run and the script executes on a synthetic bar series; the output preview and the console update from the real result. Nothing is sent anywhere.

All three. JavaScript is the default and runs instantly. Python runs on a bundled interpreter downloaded once (about 16 MB), so a script can use the standard library without installing anything. C++17 is compiled by a real Clang toolchain, downloaded once (about 60 MB), and executed as WebAssembly inside the same sandbox — the 256 most recent bars per call, 64 KiB of source, two seconds per run. Historical backtests run JavaScript and Python strategies; C++ runs as indicators and in replay.

The bars of the chart it is attached to, newest first, with open, high, low, close, volume — and the footprint per bar: bid and ask volume at every price level, delta, imbalances. That is the difference with a candle-only scripting language.

Not by itself. A strategy decides on bar close and trades the simulated account. On a compatible Rithmic account, a saved strategy can drive the optional autopilot — only after you arm it explicitly, with a contract cap, a daily loss limit and a STOP that flattens. The sandbox has no network, no file access and no access to the app API, and every run is killed after two seconds.

In Replay: pick a contract, a period, and the strategy; the auto-backtest runs it bar by bar on recorded data, with walk-forward validation across folds. The report is on the /backtest page.

Still stuck? Ping us

It is in the one plan

$9first month

then $29 a month · everything included · cancel in one click

Download for Windows