Case study
Mobility marketplace
Ground transport across worldwide operators: a supply platform, an admin portal for operations, and a mobile app.
One booking flowride-hail, chauffeur, rental
- Sector
- Ground transport operator
- Year
- 2026
- Role
- Team of eight
- Stack
- SvelteKit, Capacitor, Hono, PostgreSQL
- Runs on
- Terraform, AWS, Cloudflare, Google Cloud
The problem
Ground transport bought across ride-hailing, chauffeur and rental sits with different suppliers in every market, each with their own booking method and none of them sharing a system. Coordinating that by hand does not scale past a handful of suppliers, and the traveller sees the seams.
What we built
One platform covering all three transport types: a booking API, an admin portal for operations, and a mobile app, with supplier onboarding built into it so a new supplier can be trading rather than integrated. Infrastructure is defined as code across three cloud providers rather than configured by hand.
The long version
Ground transport is a fragmented supply problem before it is a software one. Every market has its own operators, every operator has its own way of taking a booking, and none of that is visible to whoever is trying to buy a ride in a city they have never been to. The platform exists to make one booking flow out of that, across ride-hailing, chauffeur and rental rather than treating them as three separate products.
Supplier onboarding is part of the platform rather than an operations task alongside it. A supplier that agrees to join gets an account and logs in, which is what makes the number of connected suppliers something that can grow without the operations team growing with it.
The infrastructure is Terraform across AWS, Cloudflare and Google Cloud. Three providers is not a preference, it is what the workload needed, and defining it as code is what keeps that from becoming three places to remember things about.