burneh

Strategy in, orders out, every step traced.

Automation across brokers, prop firms, and platforms, with the risk guards that keep it from running away.

strategy desk · backtester
broker · sim
ES breakout · ES · 5m · 2y
net · costs inraw signal
NET
+58.0%
MAX DD
-18.4%
SHARPE
1.24
WIN
47%
PF
1.40
sideentryexitpnl
long58425871+29
long58605852-8
short58905866+24
long59015918+17
risk guards · live
Max position3 · using 1
Daily loss cap−$1,500 · at −$420
Per-trade stop−$300 hard
Kill switcharmed
one instrument, fees + slippage in. a green backtest is a hypothesis, not a promise.
we guarantee how the tool behaves · we never guarantee the market

Toggle the costs. Watch the promise shrink.

The gap between the raw signal and the net curve is the fees and slippage most backtests quietly leave out. We report the honest one, with the risk guards that keep a bad run survivable.

Strategy in, orders out, every step traced.

A signal doesn't become an order until it clears the risk gate. Size, stop, and the daily loss cap are checked before anything is sent, the order carries its own protection, and every step is logged, so a trade is always explainable and a runaway is stopped before it starts.

signalconfirmed rulerisk gatesize · stop · caporderstop + targetbrokerMT5 · prop · dexfilled · tracedloggedblockedover a limitpassfail0102030405
01
Signal

A rule you define fires on confirmed data, the same way every time. No discretion, no hesitation.

02
Risk gate

Position size, stop, and daily-loss checks run before an order exists. Fail one and it's blocked.

03
Order

Sized to the risk, with the stop and target attached in the same request, not bolted on after.

04
Broker

Routed to MT5, a prop firm, or the exchange, and tracked to a real fill, not assumed.

05
Trace

Signal, decision, order, and fill are logged, so every trade is explainable after the fact.

Guards that keep it from running away.

The market outcome isn't ours to promise, but how much a bad run can cost you is ours to bound. Limits, stops, a daily loss cap, and a kill switch are declared up front and enforced before every order, so the worst case is survivable instead of an account-ender.

risk.yml
1# risk.yml — the guards that run before every order
2max_position: 3 # contracts, hard cap
3per_trade_stop: 300 # dollars, attached to the order
4daily_loss_cap: 1500 # dollars, then flatten and halt
5no_averaging_down: true # never add to a losing position
6kill_switch: manual + auto # one command, or on breach
Sized to risk, not to hope

Every order is sized from the stop distance and your risk-per-trade, so one loss is a known number.

A daily loss cap that halts

Cross it and the system flattens and stops for the day. No revenge trading, no 2am blow-up.

A kill switch that means it

One command cancels every resting order and closes out, and breaches trip it automatically.

No averaging into a loser

The single most common account-ender is disabled by policy, not by willpower.

A green backtest is a hypothesis, not a promise.

It's easy to make a backtest look incredible by leaving the costs out and fitting the parameters to the exact past you're testing on. That curve sells, and it doesn't survive contact with a live market. We build the honest one, and we're plain about what it can and can't tell you.

what we put in
  • ✓commissions, per contract
  • ✓slippage on entry and exit
  • ✓an out-of-sample split
  • ✓realistic fills, no perfect entries
what a hype curve hides
  • ✕look-ahead bias
  • ✕survivorship in the data
  • ✕zero-cost, perfect fills
  • ✕parameters curve-fit to the past

We scope the tool. We don't promise the market.

A trading system is software: it executes a rule you define, fast and the same way every time. What it can't do is guarantee a market outcome, and anyone who tells you otherwise is selling you something. So we build the execution, the risk guards, and the honest backtest, and we stay clear about the line: how the tool behaves is ours to guarantee. What the market does isn't.

Tell us the strategy, not the target.

Send the rule and the risk limits it has to respect. We come back with a scope, a plan, and where a demo proves it. We won't promise a return.