Skip to content
Execution

Where a signal becomes a real order

Execution is the part of a trading platform that has to work when everything else is under stress. This page describes exactly how yours runs — and what it cannot promise.

The path

Six hops, each one recorded

Nothing is inserted manually between a published signal and your broker, and every hop stores what it did.

01

Researcher

A strategy author publishes a signal from the research desk.

02

Strategy

The signal inherits the strategy's instrument scope and rules.

03

Signal

A structured, time-bound instruction enters the distribution layer.

04

Client Routing

Only accounts assigned to that strategy — and eligible for that instrument — are selected.

05

Execution Infrastructure

Validated instructions are turned into orders on isolated infrastructure.

06

Broker

The order is placed in your own broker account through your authorised session.

Validated before it exists

Risk rules run before an order is constructed, so a rejected signal never reaches the exchange.

Isolated per account

Execution for your account runs on its own infrastructure and is not shared with other clients.

Recorded end to end

Signal, validation result, dispatch and broker response are all stored and queryable.

Order placement depends on your broker and the exchange. Orders may be delayed, partially filled or rejected for reasons outside the platform's control.

Isolation

Your execution does not share a queue

Shared execution means one account's load becomes another account's delay. Allocating infrastructure per account removes that class of problem entirely.

Dedicated per account

Your execution runs on infrastructure allocated to your account rather than a shared queue, so another client's activity cannot delay or interfere with your orders.

Static outbound identity

Broker APIs frequently require a known origin. Each allocation has a fixed outbound address, which keeps your authorised session stable.

Scoped credentials

Only the authorisation needed to place orders for your account is held, and it is scoped to that account alone.

Independent monitoring

Health, session state and order flow are monitored per allocation, so a problem is detected for your account specifically rather than in aggregate.

Order lifecycle

What happens to a single signal

This sequence runs identically every time. Any stage can end it, and every ending is recorded.

01

Signal received

A published signal arrives with its instrument, direction and validity window intact.

02

Eligibility checked

The platform confirms your account is assigned to that strategy and permitted to trade that instrument.

03

Risk validated

Position rules, exposure limits and account-level constraints are evaluated. A failure here ends the process and is recorded with a reason.

04

Order constructed

Quantity, product type and order parameters are derived deterministically from your configuration — not chosen at runtime.

05

Submitted to broker

The order is sent through your authorised session. Retries are bounded and idempotent so a network fault cannot duplicate a position.

06

Response recorded

Accepted, rejected or partially filled — the broker's response is stored against the originating signal.

Limits

What execution infrastructure cannot do

A platform that only tells you what it can do is not describing trading. These are the boundaries, stated plainly.

  • We cannot guarantee that an order will be accepted, filled at a particular price, or filled at all — that is determined by your broker and the exchange.

  • Slippage between the price at signal generation and the executed price is normal and can be significant in fast or illiquid conditions.

  • Exchange-level halts, broker outages, margin shortfalls and instrument-level restrictions will prevent execution regardless of platform behaviour.

  • Positions already open are not closed automatically when you pause a strategy; managing them remains your responsibility.

Execution risk is inherent to all trading. Automation reduces hesitation and human error; it does not remove market, liquidity, broker or connectivity risk.

Broker setup

Check whether your broker is supported

Broker API capabilities differ, and that difference matters for execution. Tell us who you trade with and we will confirm what is possible before you subscribe.

Trading involves substantial risk of loss and is not suitable for everyone. Past performance does not guarantee future results.