Platform · Deploy

Deployment

It goes to paper the moment it earns it. Live stays off until you turn it on — and you're the only one who can.

What you get
Paper first, always

A strategy builds a real record before real money is discussed.

Live is yours to arm

Off by default. Nothing on this platform switches it on for you — not the brain, not us.

Your broker

Bring your own MT5. Or route alerts to a webhook and keep execution wherever it already lives.

Reversible

Everything deployed is tagged and can be pulled back.

Whatever you build here is tested against real market conditions and graded out-of-sample, so you always know whether it's working — on your own strategy, not a marketing figure. How the proof engine grades.

What we don't publish

We don't publish the execution safeguards in detail.

We publish what a module does and what it's for. We don't publish how it works. The method is the product — and anyone holding the method holds the product.

Evaluating this for a desk? Talk to sales and we'll go as deep as an NDA allows.

Worth knowing

Live trading is your decision and your risk. We build research and tooling; we don't manage money and we don't send trade advice.

How it works
  1. 01
    Paper first, on the same engine

    A deployed strategy runs on the identical execution logic the backtest used, against live prices, with no money at risk — so the forward record is comparable to the tested one rather than a different system wearing the same name.

  2. 02
    Live is off by default

    Nothing switches on real money for you. Arming happens on your own broker, by you, as an explicit act.

  3. 03
    Exported as what was tested

    Export writes the same rule graph that was measured. Where something cannot be represented faithfully in the target platform's language, it is reported rather than silently dropped.

Worked example
What an export is allowed to leave behind

A strategy with filters, custom logic, a wall-trail exit and position sizing, exported to a foreign platform.

Rules the target language can express
written faithfully
Rules it cannot
named, not dropped
Export labelled complete when partial
never

An export that silently omits your exit is worse than a refusal, because it runs. You are told exactly which parts survived the translation before anything leaves.

What it refuses to do

Every one of these is a thing we could ship and choose not to. They are here because the limits are the part of a research tool you actually have to trust.

It won't trade your live account for you

Live execution runs on your broker, armed by you.

It won't export a strategy it can't express faithfully

Untranslatable parts are named, not dropped.

Where deployment sits
Describe → Build → Prove → Train → Paper → You arm liveevery improvement re-proves before it counts1DescribePlain English, a pastedscript, or a chart photo2BuildA runnable strategy —one shape everywhere3ProveBacktested and gradedout-of-sample4TrainThe Conscious works it,condition by condition5PaperA real forward record,no money at risk6You arm liveOff by default. Only youcan turn it on

One pipeline, one strategy shape end to end. What you backtest is byte-for-byte what papers and what exports — there is no re-implementation step where drift can hide.

Questions people actually ask
Does QuantParadox trade my money?

No. Live deployment runs on your own broker and is armed only by you. Paper trading is the default and nothing escalates automatically.

Is the paper record comparable to the backtest?

Yes — deliberately. Paper runs on the same execution engine against live prices, so a divergence between the two means something real changed rather than that you are comparing two different systems.

Where can I export to?

Pine and MQL, for running on TradingView or MetaTrader. The exporter reads the same rule graph the backtest measured, and anything the target language cannot express faithfully is named rather than quietly omitted.

How long should I paper trade before going live?

Long enough that the record means something — and that is a function of trade count, not calendar time. A strategy trading twice a month needs many months; one trading daily needs weeks. The platform shows the sample size beside every figure so the answer is visible rather than guessed.

Also in deploy
Build
Strategy Builder

Draw your rules on a canvas, or just describe them in plain English. Either way you end up with a strategy the platform can test, trade and grade like any other.

Build
Import

Bring a strategy you already run. An MT5 expert or a Pine script comes in and gets held to the same standard as everything else here.

Build
Chart Reader

It reads the chart the way you do — structure, swings, ranges, compression, the shape of the candles — and it reads it as of that bar, never with hindsight.

Train
Evolution Brain

Most strategies aren't good or bad — they're good somewhere and bad somewhere else. This finds which conditions carry yours, and which quietly bleed it.

Train
Reconciliation

Every losing trade is evidence. This reads all of them, finds what they had in common, proposes a change to the rule — and proves the change before it ships.

Train
Orchestrator

Every module has an opinion. This turns them into one call, with the reasoning attached — and it will only act on an edge that has actually proved out.

Prove
Proof Engine

A backtest tells you what a strategy would have made. This tells you whether its decisions were actually any good — against history it was never shown.

Prove
Market Data

A decade of minute-resolution history across thirty instruments — the thing that decides whether a backtest is evidence or an opinion with a chart attached.

Deploy
Strategy Health

Edges decay. A strategy exported six months ago is quietly rotting on someone's terminal, and nothing tells them. This does.

Bring a strategy you already trade.

Test it yourself — or bring your desk's questions to us.

No card required · sales is for desks and teams