Phinity: a crypto exchange engine that matches 98,000 orders a second.
Phinity is our in-house exchange platform. It covers trading, custody, KYC and real-time market data, and we built it as a reference for exchange and brokerage projects. We open-sourced the matching engine so you can read the code before you hire us.
The matching engine is open source. A walkthrough of the full platform is available on request.
Start from proven parts, not a blank page.
An exchange is not much use without the hard parts: a matching engine that stays correct under load, custody that keeps keys away from your servers, KYC that satisfies regulators, and market data that updates in real time. Most exchange scripts for sale do these poorly, and building them from scratch for every client is slow and expensive.
So we built them once, properly, as one platform. When a client needs an exchange, a brokerage backend or a trading feature, we start from components that are already designed, tested and benchmarked. We made the engine open source because, for this kind of software, being able to read the code matters more than anything we could say about it.
Everything an exchange needs, built as services.
Eleven Spring Boot microservices behind one gateway, talking through Kafka, each one deployable and scalable on its own.
Trading core
- Limit, market, stop-loss and trailing stop-loss orders
- GTC, IOC and fill-or-kill time-in-force
- Price-time priority matching, one engine per pair
- Dedicated thread pool for high-volume pairs
- Order books restored from snapshots after a restart
Custody & wallets
- Fireblocks vaults and deposit addresses
- Signed webhook verification
- Blockchain deposit tracking via Alchemy webhooks
- Self-hosted wallet option with AWS KMS
- Withdrawals protected by OTP and 2FA
Users & compliance
- KYC and AML checks through ComplyCube
- Email and SMS verification, 2FA
- Location checks and bot protection
- Device and session management
- JWT auth; services only accept calls from the gateway
Real-time market data
- Live order book, trades and ticker over WebSocket
- Compact binary socket events
- TradingView charts with live candle updates
- Time-series storage for price history
Business & admin
- Asset and trading pair management at runtime
- Fee discounts by KYC level and trading volume
- Trading competitions and user levels
- User approval, analytics and system config
Infrastructure
- API gateway with load balancing and circuit breakers
- Service discovery for horizontal scaling
- Kafka, Redis, MongoDB and PostgreSQL
- Docker deployment scripts and hardware sizing guide
98,039 orders a second, on a laptop.
We sent 50,000 orders across 497 trading pairs through the matching engine. All of them were processed in 510 milliseconds, with every fill checked for correct price-time priority and no quantity lost. The test ran on an ordinary laptop (Intel Core i7, 10th gen, 16 GB RAM), not tuned server hardware.
Figures are for the matching engine itself, excluding network and persistence.
| 497 pairs, mixed load | 98,039 /s |
| Single trading pair | 84,276 /s |
| Concurrent stress test | 67,720 /s |
| Realistic order mix | 53,667 /s |
Your exchange, months sooner.
- Launching an exchange or brokerage: start from a benchmarked core, not from zero
- Already have a platform: we can plug in a faster matching engine, custody or KYC
- Adding trading features: stop orders, live order books, charts and alerts are already solved
- Full source code and IP handed over, with no licence fees
Building an exchange or trading platform?
Tell us what you’re launching. We’ll show you which parts are already built, in writing, within 48 hours.
Start your project →