Executable nodes
129+
Events, markets, indicators, logic, risk, execution, and chart output.
Blueprint Engine
Turn trading logic into executable node blueprints.
The blueprint engine keeps market reads, indicators, branches, risk guards, order intent, and chart feedback on one canvas, giving each strategy a clear path from idea to validation and execution.
Built-in templates
10+
Breakout, grid, martingale, trend, and range systems as starting points.
Runtime modes
3
backtest, paper, and live share one runtime entry.
Indicator modules
36+
EMA, ATR, ADX, VWAP, MACD, RSI, and other modules can be assembled directly.
Why Blueprint
Blueprints are not demo blocks. They are the assembly layer for trading strategies.
They break trading judgement into connected, debuggable, reusable nodes: market sources, indicators, state checks, exposure controls, order intent, exit rules, and chart annotations can all be inspected inside the desktop client.
01 / Blueprint
An executable node canvas
Event, market, indicator, logic, risk, and execution nodes connect on one canvas, making strategy structure visible while leaving room to grow from simple conditions into branched systems.
- Node links express the strategy flow
- Branching and state logic are supported
- Parameters stay manageable in the inspector
02 / Blueprint
One path from market reads to order intent
Blueprints separate market:read, trade:intent, and chart feedback. The system can produce reviewable order intent before it reaches paper or live execution.
- Market, account, and order semantics stay separate
- Order intent can be inspected before execution
- Built for multi-exchange adapters
03 / Blueprint
Backtesting, replay, and debug frames
Backtests are more than an equity curve. The runtime can replay node state, order intent, and chart annotations bar by bar, showing why a strategy entered or skipped.
- Bar-by-bar replay
- Traceable node execution order
- Chart marks and order history in one view
04 / Blueprint
Risk before execution
Cooldowns, rate limits, max exposure, ATR stops, circuit breakers, and exit conditions can sit before order placement instead of being explained after the report.
- Pre-order risk guards
- Circuit breaking for abnormal state
- Unified exposure and frequency constraints
05 / Blueprint
Template assets and version flow
Blueprint templates can be imported, exported, and versioned so teams can turn reusable strategies, parameter presets, and chart styles into maintainable assets.
- Built-in templates accelerate setup
- Blueprint zip import and export
- Useful for team knowledge bases
Runtime Flow
One blueprint can move through backtest, paper, and live execution.
The runtime reads market context first, then processes indicators, state, risk, and order nodes. Each mode shares the same structure, reducing rewrites from research to execution.
01
Read market context
Collect inputs from exchange services, candle series, account snapshots, and positions.
02
Compute indicators and state
Run EMA, ATR, trend state, branch conditions, and variable updates inside the node graph.
03
Generate intent through risk
Check cooldowns, exposure, frequency, and circuit breakers before producing order intent.
04
Replay, paper, or live
Move the same structure into backtest, paper, or live while keeping debug frames as evidence.
Guardrails
Risk control sits before execution.
The blueprint engine works best when risk is part of the strategy structure instead of an explanation after the equity curve.
Cooldowns and rate limits
Control repeated triggers and excessive order intent frequency.
Exposure and position checks
Check max exposure, direction, and position context before orders are formed.
Circuit breakers and exits
Place loss cooldowns, ATR exits, take-profit logic, and abnormal-state breakers before execution.
Reconciliation and audit
Keep order intent, runtime state, and debug frames for review and team audits.
Strategy Assets
Turn strategy experiments into reusable assets.
Templates, parameters, chart marks, and node structures can become versioned assets that later feed the extension layer or team knowledge base.
Template start
Start from breakout, grid, trend, range, and other templates instead of rebuilding from zero.
Import and export
Use blueprint packages to back up, move, and share strategy structures.
Chart feedback
Write entries, exits, state changes, and debug output back into the chart view.