Platform

One platform, four layers, zero glue code

MatchCore ships as a single deployable core with a consistent access, matching, risk and persistence layer — not a bundle of separately-versioned services you have to integrate yourself.

MatchCore layered architecture from access protocols down to persistence and audit Access Layer FIX · low-latency binary API · WebSocket · REST MatchCore Engine Prediction markets · pari-mutuel pools · stock-exchange order books — three matching models, one platform Data & Risk Layer Market data distribution · pre-trade collateral checks · house position limits Persistence & Audit Every order safely recorded · instant, verified recovery · regulator-ready audit trail

The four layers

  • Access layer — FIX, a dedicated low-latency API, WebSocket and REST, each keeping client traffic clear of the matching engine itself.
  • MatchCore engine — the matching core itself: stock-exchange, binary and pari-mutuel order books, one platform, one integration.
  • Data & risk layer — real-time market-data streaming, pre-trade collateral checks, house position limits.
  • Persistence & audit — every order safely recorded before it's confirmed, instant verified recovery, and optional multi-node replication for venues that want it.
Core components

What ships in the box

Matching core

Consistent, high-precision matching with nanosecond-resolution timestamps — every order safely recorded before it's applied.

Gateway layer

Connect over FIX, our low-latency API, WebSocket or REST, with client traffic kept clear of the matching engine itself.

Risk & controls

Pre-trade position limits evaluated inline with matching, so exposure never gets ahead of the book.

Admin & surveillance

Market lifecycle management and a full sequenced audit trail for compliance teams.

Deployment

Runs where your latency budget lives

TopologyNodesBest for
Standard (default)1Production venues — this is how most production matching engines actually run, and how MatchCore runs by default. Recovery is instant, not a failover process.
Clustered (optional)3+Venues that specifically want synchronous multi-node replication and are willing to trade some latency for it.

Read the architecture in depth

Replication & clustering →