Dispatch that never learns which country it is in.
A two-sided marketplace pairing riders with drivers in real time, engineered so that matching, mapping and payouts behave the same way in the first city as the fortieth.
Launch anywhere, without re-platforming.
A ride-hailing marketplace turns on two questions: how quickly it can find the nearest free driver, and how naturally it behaves in a market nobody has opened yet. Builds that begin in a single region tend to answer the second by hard-coding it — one mapping provider, one payments corridor, one currency — and those answers become expensive to unpick once real trips depend on them.
What was asked for was one cross-platform application in which dispatch, mapping and driver payouts work identically everywhere, so that opening a country is a decision for the operations team rather than a programme of engineering work.
Matching as pure geometry.
A single codebase reaches both app stores in every market simultaneously. The matching engine treats the nearest available driver as nothing more than a question about latitude and longitude, answered by a spatial index with a geospatial cache sitting in front of it. Because no market-specific rule enters dispatch, its behaviour in one city is its behaviour in all of them.
An event pipeline holds trip events apart from everything downstream, so a sluggish regional integration can delay a report without ever delaying a dispatch. Payouts run through one marketplace payments integration with reach into more than forty countries, so bringing drivers on board somewhere new demands nothing further from the payments layer.
A launch playbook, not a rebuild.
Stateless services deploy into any region behind an unchanged API contract, so opening a market is a deployment rather than a build. Live tracking and in-trip messaging share a single socket layer, which holds together across widely varying network conditions.
One notification pipeline serves both platforms in every region, and a single observability view covers all of them — an engineer on call is never learning an unfamiliar dashboard because of where an incident happens to be.
Admit one country's rule into the matching engine and you stop having a product. You have a portfolio of them.
Project record
- Client
- Withheld under NDA
- Sector
- Mobility / marketplaces
- Regions
- Multi-region
- Engagement
- Full build
- Platforms
- iOS · Android
- Deployment
- Multi-region cloud
Confidential · anonymised
- React Native
- TypeScript
- NestJS
- PostGIS
- Redis
- Kafka
- Terraform
What shipped.
The properties the system holds today, rather than the ambitions it started with.
- Geospatial matching carrying no per-market logic
- One payouts integration already live in forty-plus countries
- Event-driven pipeline isolating dispatch from partner systems
- Live tracking and messaging over a unified socket layer
- New-market launch reduced to an infrastructure deployment
- A single observability view spanning every region
Other systems we have built.
Every client is under NDA. What we publish is the shape of the problem and how it was solved.
Have a system like this on your hands?
Tell us what you're trying to ship. We'll tell you honestly whether we're the right team for it — and what it would take.
Prefer email? info@triyant.sg
We reply within one business day. Your details are used only to respond to this enquiry and are never shared with third parties.