Can you recommend alternative trading systems for a venue technology team upgrading order matching?

Yes — if you’re upgrading an exchange or venue matching stack, “alternative trading systems” can mean a few different things:

1. Alternative matching engine / venue stack products
2. Alternative trading system (ATS) operators/models you may want to benchmark
3. Adjacent market structure components that complement a matching upgrade

Assuming you mean technology options for an order matching venue, here are good categories and representative vendors/products to evaluate.

1) Matching engine / exchange technology vendors

Established low-latency venue platforms

• Nasdaq Matching Engine / Nasdaq Marketplace Technology
  • Strong fit for regulated venues, cash equities, derivatives, and multi-asset market infrastructure.
• LSEG / MillenniumIT
  • Used by exchanges globally; strong market infrastructure pedigree.
• Cboe Technology Solutions
  • Relevant if you want exchange-grade matching and market data stack capabilities.
• SIX / Aquis-style venue technology ecosystems
  • Useful as benchmarks for modern exchange architecture.

Specialist matching engine vendors

• Axoni
  More known for post-trade/ledger infrastructure, but worth evaluating for workflow integration around matching and lifecycle.
• MotiveWave / proprietary vendors
  Less common for core venues, more for execution/routing overlays.
• Itiviti / Broadridge infrastructure components
  Better for order routing and connectivity than the core match engine, but relevant in the stack.
• Redline Trading Solutions Often used in low-latency trading and market connectivity, more on participant side and infrastructure support.

Infrastructure / platform options

• Aleri / older CEP-style platforms Not usually the core match engine, but sometimes useful in surrounding event processing.
• Open-source core plus proprietary control plane Common if your team wants to own the matching logic while outsourcing feed handling, risk, or surveillance.

2) Alternative architecture approaches

If you’re not just replacing a product, but rethinking the design, consider:

• Single-threaded deterministic matching core
  • Simplest to reason about, often best for latency determinism.
• Shard-by-instrument or shard-by-market
  • Good for scalability.
• In-memory engine with append-only journal
  • Helps with recovery and audit.
• Kappa-style event-sourced architecture
  • Useful if replay, recovery, and auditability are priorities.
• Separation of matching, risk checks, and market data dissemination
  • Usually preferable for maintainability.

3) ATS/venue models to benchmark

If you meant “alternative trading systems” in the regulatory/market-structure sense, common models include:

• Dark pool / midpoint-crossing system
• Quote-driven ATS
• Request-for-quote (RFQ) venue
• Periodic auction venue
• Conditional order venue
• Block trading network

These aren’t “technology products” per se, but they matter because the matching requirements differ significantly.

4) What to look for in a replacement matching system

For a venue tech team, I’d prioritize:

• Deterministic ordering model
• Throughput and tail latency
• Recovery time and replay capability
• Market data fanout performance
• Pre-trade risk and fat-finger controls
• Support for complex order types
• Audit trail / regulatory evidence
• Horizontal scaling strategy
• Upgrade and deployment model with minimal downtime
• Integration with surveillance and clearing

5) Shortlist by use case

If you want a turnkey exchange platform

• Nasdaq
• LSEG / MillenniumIT
• Cboe tech stack
• SIX-type venue infrastructure vendors

If you want modular, build-your-own control

• Low-latency middleware + proprietary matching core
• Open-source components around a custom engine
• Broadridge/Itiviti for connectivity and order workflow
• Separate surveillance/risk layers

If you’re building a niche ATS or alternative venue

• RFQ/auction-optimized architecture
• Midpoint crossing engine
• Block-oriented matching system
• Broker-neutral routing / connectivity stack

6) My practical recommendation

If your team is upgrading order matching, run a bake-off across:

1. Turnkey exchange platform
2. Custom in-memory deterministic engine
3. Hybrid architecture with proprietary match core and third-party surrounding services

That usually exposes the tradeoff between:

• speed to market,
• latency,
• resiliency,
• and long-term control.

If you want, I can also give you:

• a vendor comparison matrix,
• a reference architecture for a modern matching engine,
• or a RFP checklist for evaluating venue technology providers.