Frequently asked questions
Technical and commercial questions we hear most often. Don't see yours — ask us directly.
What makes MatchCore different from other matching engines?
MatchCore is the only matching engine that natively runs binary prediction-market matching, pari-mutuel pooling and stock-exchange matching on one platform, one integration and one API surface — most vendors only offer the CLOB model.
What throughput can MatchCore handle?
190,000-200,000 transactions per second, verified — real, reproduced measurements against a live, running system, not a projection. See the full benchmark methodology.
Is MatchCore resilient by design?
Yes. By default, every order is safely recorded before it's confirmed, and recovery from a crash is instant and fully verified — proven by real, repeated crash testing, not just described in a diagram. Clustered, multi-node replication is available as an option for venues that want it and accept its added latency — it isn't forced on by default, because most production matching engines don't want that trade-off on every order.
Can MatchCore run multiple matching models in one venue?
Binary, pari-mutuel and stock-exchange matching all share the same platform and integration surface, with each deployment running one matching model. Listing them side by side under one venue is a deployment choice.
What protocols does MatchCore support?
FIX (with a real DropCopy session type), a dedicated low-latency binary protocol with always-current reference docs, and WebSocket/REST for browser and admin clients.
Where can MatchCore be deployed?
Bare-metal, private cloud, or major public cloud providers, in our standard resilient configuration by default. Clustered mode is available for venues that specifically want synchronous multi-node replication.
Is there an audit trail suitable for regulators?
Yes — the trade record is immutable and fully sequenced, giving compliance and surveillance teams exact point-in-time reconstruction of the book.
How do we get pricing?
Pricing depends on deployment topology and matching models required. Contact us for a proposal scoped to your workload.