Pillar 01 · Core execution

One execution layer.
Multiple liquidity venues.

FIX connectivity, order booking, pre-trade risk and the client-facing terminal — plus the data plane that measures all of it. Four modules that determine whether the rest of the stack is credible.

FIX 4.4 / 5.0 SP2 WebSocket binary In-memory book OpenAPI 3.1 <1 ms bridge hop
01 · CoreVex Bridge

Own the connection.

A dedicated FIX aggregation and routing layer between the operator's book and external liquidity — with no third-party bridge vendor in the path.

Layer L01

For operators

  • Revenue. Removing a per-lot bridge fee changes unit economics on every ticket, permanently.
  • Risk. Venue failover, last-look filtering and depth aggregation are observable rather than assumed.
  • Capital efficiency. Clean, documented volume becomes negotiating leverage for tighter spreads and rebate tiers.

For technologists

  • FIX. 4.4 and 5.0 SP2 sessions with sequence recovery, heartbeat monitoring and logon-state alerting.
  • Routing. Best bid/offer aggregation across venues, per-tier dynamic markup, symmetric pricing across both booking layers.
  • Failover. Hot-standby session on a second site; automated re-logon with gap fill.
  • APIs. REST control plane for venue configuration, markup schedules and session state; WebSocket telemetry stream.
<1 ms
Bridge hop
99.6%
Fill rate
5
Depth levels

Design targets for a co-located deployment · measured at the CoreVex gateway against the venue quote, not end-to-end client latency

System view · aggregation topologyLD4 ⇄ NY4
Operator bookNetted exposure · dual-layer booking
CoreVex ConnectSmart aggregation · dynamic markup · last-look filter
LP-1 · Tier-1 bankFX · metals · 0.9 ms
LP-2 · Prime of primeFX · indices · 1.4 ms
LP-3 · Non-bank MMFX · 0.7 ms
LP-4 · SpecialistProfessional only · 2.1 ms
Sessions4 / 4 logged on
FailoverHot standby NY4
Depth5 levels · TOB + VWAP
Avg slippage · 30d+0.02 pip
Reject rate · 30d0.3%
Per-lot vendor fee$0.00
Every fill timestamped against the venue quote · feeds the published execution-quality report
Venue-agnosticMarkup schedules per tierInstitutional FIX tierLatency reported per session
Request bridge spec
02 · CoreVex Trade Engine

The book, the router and the risk pool.

An in-memory order and position engine with netting, dual-layer booking, continuous account classification and automated break-even hedging inside a published exposure ceiling.

Layer L02 · L03

For operators

  • Revenue. Routing decisions are deterministic and logged, so margin per ticket is measurable rather than estimated.
  • Risk. Internalised exposure cannot exceed a published ceiling; breach triggers automatic re-hedge, not a desk discussion.
  • Capital efficiency. Netting before hedging reduces margin posted at venues and the own-funds requirement attached to it.

For technologists

  • Booking. Dual-layer: externalised STP flow and bounded internal pool, both on one symmetric price feed.
  • Clearance. Per-ticket scoring against volatility regime, session context, correlation and stop geometry before routing.
  • Classification. Mean-variance decomposition, Kelly sizing and hierarchical risk-parity clustering recompute tiers continuously.
  • Hedging. Multi-instrument break-even engine with overflow re-hedge to the external layer when the band is breached.
<3.2 s
Clearance
0.00%
Toxic-flow breaches
45k+
Lots / month hedged

Clearance and toxic-flow figures are design targets · lot volume is a client-specific historic profile of one deployment and is not generalisable

System view · routing and risk poolNetting active
Cleared flowAll segments · per-ticket score attached
Smart routerContinuous tiers A–E · segment dispatch
External layerSTP to venues · institutional & profitable flow
Internal poolBounded · session caps · break-even hedged
Overflow re-hedgeAutomatic when the exposure band is breached
Net exposure vs ceilingWithin band
−CEILINGNET Δ ≈ 0+CEILING
Book VaR 99%0.62% of equity
Price symmetryVerified
Hedge modeBreak-even
Static client typesReplaced
Routing side is never exposed to the client · both layers execute on an identical price feed
Symmetric pricingPublished exposure ceilingAppend-only decision logFour-eyes on override
Request engine spec
03 · CoreVex Web Trade Engine

A terminal you own the roadmap for.

A browser-native execution surface streaming over WebSocket binary frames — running alongside MetaTrader on the same account, with no per-seat licence ceiling.

Layer L02

For operators

  • Revenue. Unit economics improve with every added user instead of every added seat licence.
  • Risk. Order-ticket behaviour and stop edits are structured telemetry the risk engine can read.
  • Brand. Full theming, custom domains and an independent feature roadmap — no vendor release cycle.

For technologists

  • Transport. WebSocket binary frames with delta updates; no polling, no re-subscribe storms.
  • Surface. Aggregated 5-level depth, candle rendering with indicators, on-chart drag-to-edit stops, position timeline with session filters.
  • Native modules. Copy-trading and managed-account allocation are hooks in the engine, not integrations bolted on.
  • Access. Mobile PWA with no download; institutional FIX tier; embeddable JS SDK for partner surfaces.
0.4 ms
Tick to screen
0
Downloads required
1
Login across brands

Tick-to-screen is a design target measured on a reference deployment over a co-located connection · real client latency depends on network path

System view · terminal surfaceWebSocket · binary
XAU/USD · M15 2,385.10 ▲ 0.42%
TOLERANCE NORMAL
M1M15H1H4D1 EMA 200 · RSI
Depth of market · aggregated
2385.656.2M
2385.4512.4M
2385.308.1M
Spread 0.1Mid 2385.25
2385.2010.2M
2385.0018.5M
2384.857.0M
RoutingExternal STP
Ticket score0.71 clear
SessionLondon · pre-NY
Mobile PWAInstitutional FIX tierJS SDKWhite-label theming Quantities illustrative · not a live feed
MT4 / MT5 side-by-sideCopy-trading nativeManaged-account hooks
Request terminal spec
04 · Live Market Data & Report API

One data plane for prices and for proof.

Market data, derived analytics, execution-quality measurement, client statements and regulatory reporting extracts — served from a single versioned API surface.

Layer L06

For operators

  • Revenue. Data and analytics are licensable to partners and professional clients as a standalone product line.
  • Risk. Execution quality is measured and published, which is the defensible position in a conduct review.
  • Capital efficiency. One plane removes duplicate feeds and the reconciliation work that comes with them.

For technologists

  • Streaming. WebSocket channels for ticks, depth, trades and derived signals; REST for history and batch.
  • Derived layer. Ensemble scoring across indicator, news-polarity, copy-flow, sentiment and calendar models, each weighted by trailing accuracy.
  • Reporting. Statements, transaction-reporting extracts, execution-quality reports and audit exports as versioned endpoints.
  • Governance. Scoped API keys, per-key rate limits, idempotency keys on writes, OpenAPI 3.1 schemas, generated documentation.
99.95%
Availability target
40 ms
API p95
3.1
OpenAPI version

Availability and latency are design targets with a published measurement method · actual figures vary by region and tenancy

System view · data planeREST + WebSocket
Ensemble signal · 30-day weighted
InstrumentSignalScoreModel votesNote
XAU/USDBUY0.72ind 71 · news 66 · flow 69Trend intact above 2,362
EUR/USDBUY0.58ind 63 · news 60 · social 52Range · watch 1.0900
US500SELL0.61ind 64 · flow 58 · cal 67Professional tier only
BTC/USDSELL0.54ind 60 · on-chain 67Outflow cluster
Endpoint surface
GET/v1/marketdata/{symbol}depth · tick · trades
WS/v1/streambinary delta frames
GET/v1/signals/ensemblescored · per model
GET/v1/reports/execution-qualityCOBS 11.2A shape
GET/v1/clients/{id}/statementspdf · csv · json
POST/v1/audit/exportidempotent · signed
Signal scores are illustrative model output · analytics are not investment advice and carry risk warnings in the client surface
Versioned schemaScoped keysBatch exportWebhook callbacks
Request API spec
Integration matrix

What each module exposes.

Every module ships the same integration contract: documented API, event webhooks, white-label surface and a stated service level.

ModuleLayerAPIWebhooksWhite-labelStandaloneSLA class
BridgeL01REST · FIX✓n/a✓Critical
Trade engineL02gRPC · REST✓n/aWith L01Critical
Web trade engineL02WS · JS SDK✓✓✓Critical
Market data APIL06REST · WS✓✓✓High

Standalone indicates whether the module can be deployed against a non-CoreVex stack · critical SLA class carries a named engineering contact and a documented recovery objective

Pillar 01 · next step

Scope the execution layer against your current stack.

Bring your venue list, your volume profile and your current bridge arrangement. We will return a dependency graph and a latency budget.

Book a technical discovery View architecture map
Book a call Architecture