Skip to main content

How it works · The system

From market data to measured decisions.

Five stages, one direction. Every decision is recorded, every simulated order request is checked by a risk engine that strategy code cannot bypass, and no part of the system can place a real order.

Paper trading onlyNo custodyNo exchange keys

The decision engine

One path. Four ways it can end.

An observation enters, becomes features, models decide whether to ask for anything, and a separate risk engine judges every request. Pick a scenario to see where the signal stops, and why.

Illustrative scenario

Example values

Scenario C, Paper order approved: the signal reaches data, models, risk, paper execution, evaluation and completes at evaluation. Approved, sized by the risk engine, filled on paper and measured.

C · Runs to 05 Evaluation

Approved, sized by the risk engine, filled on paper and measured.

  • WITHIN_LIMITS
  • BINDING_ALLOCATION

The request passes every check. The risk engine sizes it, not the strategy: the 20% allocation cap binds first. The paper broker fills it at the next bar open with spread, slippage and a 0.1% fee, and the ledger records it. The outcome is then measured against a no-trade baseline.

Illustrative · example values on default limits, not a recorded result

  1. 01

    Data

    Passed

    Binance public spot candles

    Fresh closed candle

    Stream
    BTC/USDT · 1h
    Closed
    14:00 UTC
    Age
    38 s · max 2h 1m 30s
  2. 02

    Models

    Passed

    Strategies and shadow models

    Proposes entry

    Strategy
    BUY @ 67,240.00
    Stop
    65,900.00
    Request
    ENTRY · BTC/USDT
  3. Independent boundary · no skip switch

    03

    Risk

    Passed

    Independent risk engine

    Approved

    Size
    0.00059 BTC
    At risk
    0.92 / 1.00 USDT
    Binds
    Allocation 20%
  4. 04

    Paper execution

    Passed

    Paper broker and ledger

    Filled at next open

    Fill
    67,291.46
    Notional
    39.70 USDT
    Fee
    0.04 USDT
    Ledger
    +4 journal lines
  5. 05

    Evaluation

    Recorded

    Measured, then stored

    Measured and stored

    Marked
    Every bar
    Versus
    No-trade baseline
    Label
    Simulated result

What each stage does, in the product today

  1. 01 · Binance public spot candles

    BTC, ETH and SOL on 15m, 1h and 4h. Only closed candles are used. A stream without a fresh closed candle is flagged stale and new entries are blocked.

    Status: BetaMarket data feed
  2. 02 · Strategies and shadow models

    Versioned strategies read the closed-candle window and may propose a simulated order. Shadow models only record forecasts before the outcome is known; they have no route to orders.

    Status: BetaShadow forecasts
  3. 03 · Independent risk engine

    Outside strategy code, with no skip switch. Checks every simulated order request: loss limits per trade, day and week, exposure caps, kill switch. Long only: no leverage, margin or shorts.

    Status: BetaIndependent risk engine
  4. 04 · Paper broker and ledger

    Approved requests fill against a simulated USDT portfolio at the next bar open, with fees and slippage, and are written to an append-only, double-entry ledger.

    Status: BetaPaper trading
  5. 05 · Measured, then stored

    Positions are marked to market every bar, forecasts are scored after their horizon, and strategies are compared with a no-trade baseline. Results are labelled as simulated.

    Status: BetaStrategy backtesting

Safety architecture

Boundaries the system enforces.

Each limit is a property of the code or the database: a route that does not exist, an engine strategies cannot skip, a policy that keeps workspaces apart. Data comes in. Nothing goes out to an exchange.

Safety architecture. Outside the platform: public market data flows in; there is no route out to real exchange order endpoints, no exchange keys are accepted today and funds are never held. Inside the paper-only platform: a platform kill switch; workspaces isolated by Postgres row-level security; in your workspace a portfolio that starts paused, and an independent risk engine boundary around the paper broker and append-only ledger; an append-only audit log across the platform.
Outside
  • Binance public market data

    Public candles in, read only

    In · data only
  • Exchange order endpoints

    No adapter can send an order to a real exchange

    No real order route
  • Your funds and exchange keys

    No keys accepted today; funds never held

    No custody
Platform boundary

Paper only.

The only execution mode is paper. Asking for any other executor raises an error.

Platform kill switchStops every portfolio at once
Tenant isolationPostgres row-level security
Your workspacePaused by default

Simulated portfolio · USDT. Nothing runs until you start it.

Independent risk engineChecks every request

Paper broker

Fees and slippage, next-bar fills

Ledger

Append-only, double-entry

Another workspace

Its rows are invisible to yours, and yours to it. The database enforces it, not the page.

Audit log · append-onlyPortfolio state changes and the kill switch are recorded. The database refuses edits to recorded rows.

Watch the engine decide. Join the beta.

Join waitlist Open dashboard