Prop Rails watches trading accounts in real time, detects configured rule breaches, cuts exposure, cancels working orders, and records exactly how long the response took.
Interface mock-up with sample values — not a recording of a real account. Every measured figure on this site comes from the published benchmark: see the data and method.
A challenge rule only protects a firm when exposure is actually removed. Prop Rails measures from breach detection to the exchange’s own position push confirming the account is flat.
50 forced breaches on a dedicated OKX demo account, measured from a Windows 11 host in Johannesburg. The benchmark records dispatch, exchange acknowledgement, fill events, flat confirmation and request paths.
OKX demo result from 16 Sep 2026. Demo is not production and network location materially affects end-to-end latency. Read the methodology and caveats →
Start without trade permissions, establish the current baseline, then decide whether Prop Rails should become an active enforcement layer.
Observe your existing risk stack with a read-only key and measure when your own system reacts.
Continuously enforce configured challenge rules on live or demo accounts.
Force repeatable breaches on a dedicated demo account to measure the complete cut path.
Prop Rails maintains account state from exchange streams, re-marks equity, evaluates rules, dispatches parallel cut operations and verifies the final account state.
Monotonic timing, persistent breach state, account isolation and auditable request / fill / flat events.
The useful work is not the dashboard. It is deterministic behaviour through dropped sockets, rate limits, partial fills, restarts and unexpected re-entry.
Parallel close and cancel operations are initiated immediately after a breach.
REST state re-read and retry logic handles incomplete or failed first paths.
If exposure reappears after a breach, the account remains latched and is cut again.
Reports distinguish acknowledgement, fills and final flat confirmation.
Rule state and breach state survive process restarts instead of silently resetting.
WebSocket reconnection and account-level isolation reduce single-failure blast radius.
Every run can be reconstructed from structured events, timestamps and outcomes.
Pilot mode refuses trade-capable OKX keys and state-changing client calls in code.
Give Prop Rails read-only access to an observed account. It records account events and measures when your current risk system intervenes, without sending trade instructions.
Most crypto prop firms hand the trader a Bybit sub-account and take an API key. Prop Rails plugs into that arrangement from the read-only side first, and can add OKX as a second venue on exactly the same pattern.
A read-only key on one of your existing Bybit accounts. Prop Rails records the breach instant and when your current system actually reacts.
The read-only path was checked against a live Bybit Demo Trading account on 17 September 2026: private stream authenticated in 1.6 s, key reported read_only, nothing sent.
OKX demo trading uses the same connect-your-API model as Bybit, so offering it to traders is a venue addition rather than a platform migration.
Stated plainly: active cutting is implemented and benchmarked on OKX v5. On Bybit, Prop Rails observes and reports — it does not claim production enforcement.
Prop Rails is not a funded startup with a sales team. That is the point: the claims on this site are small enough that one person can stand behind every one of them.
Start with a read-only pilot, or review the public OKX benchmark first.
