Full source · one-time purchase · live demo running

Launch a ride‑hailing business you actually own.

Rider, driver and fleet-partner apps plus the operator console — one codebase that ships genuinely local in 15 markets: 12 payment rails, 14 languages with RTL, local fares and safety conventions. Rides, parcels, rentals and intercity, on one spine.

Get the code See it running

2,054 counted test cases · every number on this page is counted from the repository at build time

Operator console — live dispatch queue and map

Rider app — choosing a ride with upfront fares

Driver app — an incoming ride offer with a countdown

India·INR·pixMexico·MXN·mercadopagoUnited Arab Emirates·AED·moyasarRTLSouth Africa·ZAR·paystackKenya·KES·xenditPhilippines·PHP·tapKuwait·KWD·tapRTLEgypt·EGP·stripeRTLCanada·CAD·stripeUnited Kingdom·GBP·stripeAustralia·AUD·stripeNew Zealand·NZD·stripeGermany·EUR·stripeFrance·EUR·stripeMorocco·MAD·flutterwaveRTLIndia·INR·pixMexico·MXN·mercadopagoUnited Arab Emirates·AED·moyasarRTLSouth Africa·ZAR·paystackKenya·KES·xenditPhilippines·PHP·tapKuwait·KWD·tapRTLEgypt·EGP·stripeRTLCanada·CAD·stripeUnited Kingdom·GBP·stripeAustralia·AUD·stripeNew Zealand·NZD·stripeGermany·EUR·stripeFrance·EUR·stripeMorocco·MAD·flutterwaveRTL

1,253

backend test cases

103 suites

764

app + console test cases

rider · driver · partner · admin

37+13

end-to-end checks

Playwright · Maestro

preset markets

one config row each

payment rails

local first, cards fallback

app languages

RTL included

Counted from the repository at build time — never typed into marketing copy. How we count

One purchase, four surfaces

Everything a ride business runs on, already built.

Three mobile apps and the console that runs them, sharing one backend, one ledger and one set of market rules.

iOS · Android · Expo

Rider app

Rides, parcels, rentals, intercity
Wallet with the market's own rails
Safety centre, trip sharing, SOS

iOS · Android · Expo

Driver app

Offers with a countdown, auto-accept
Earnings, quests, instant payouts
Destination mode and trip preferences

for people who own the cars

Fleet partner app

Live drivers and the fleet's cars
Trips with the money split
Withdraw the fleet's own balance

Next.js · 15 languages

Operator console

Live dispatch on a map, no UUIDs
Money, tax, payouts, incidents
Markets, zones, pricing, promos

Four verticals, one spine

A person, a package, an hour, or another city.

All four run on the same dispatch, ledger, pricing and safety spine — each with the domain logic that makes it real, not a renamed ride type.

City rides

Fixed upfront quotes or inDrive-style bidding, per market
Multi-stop (up to 3) with per-leg fares
Women-only rides, market-gated, fail closed before pricing
Fare integrity: recomputed from actuals, a waiting meter both sides watch

Parcel delivery

OTP at both ends + photo proof, codes hidden from the courier
Priced failure paths: free retry, then return-to-sender at 60%
Chain of custody in the console, per-market size and weight tiers
Courier paid for both legs on a return

Hourly rentals

Package ladder (1h/10km … 12h/120km) seeded from each market's fare
Live overage meter mirrored in rider and driver apps
Mid-trip destination edits, package-expiry sweeper
The rider ends the trip, not a timer

Intercity

One-way 1.3× · round-trip 0.85× with a 250 km/day floor
Driver daily and night allowances, tolls and permits as line items
Driver opt-in is a dispatch predicate — no surprise long-hauls
30-minute dispatch lead on scheduled departures

How the four verticals share one spine

Genuinely local

15 markets that each feel local — because they are.

One preset table drives currency, timezone, dial code, distance unit, payment rails, tax engine, top-up amounts and languages for every market. Seeding, the installer and all three apps read the same source, so nothing drifts. Launching a country is a config row and an admin toggle, not a fork.

14 app languages, parity-tested

العربية · বাংলা · English · Español · ગુજરાતી · हिन्दी · Bahasa · ಕನ್ನಡ · मराठी · Português · தமிழ் · తెలుగు · ไทย · Tiếng — with true RTL layout, enforced by parity tests so a new string can't ship English-only.

Local emergency numbers

The SOS button dials the right number in every market — not a hardcoded 911 shipped to Nairobi.

3 government e-invoicing engines

Brazil NFS-e (municipal ISS) · Mexico CFDI 4.0 · Saudi ZATCA (TLV QR) — credential-gated with a deterministic local fallback; invoicing never blocks a ride.

South Asia

1 market

India

INR · pix · +91

Southeast Asia

1 market

Philippines

PHP · tap · +63

Middle East

3 markets

EgyptRTL

EGP · stripe · +20

KuwaitRTL

KWD · tap · +965

United Arab EmiratesRTL

AED · moyasar · +971

Africa

3 markets

Kenya

KES · xendit · +254

MoroccoRTL

MAD · flutterwave · +212

South Africa

ZAR · paystack · +27

Latin America

1 market

Mexico

MXN · mercadopago · +52

Other

6 markets

Australia

AUD · stripe · +61

Canada

CAD · stripe · +1

France

EUR · stripe · +33

Germany

EUR · stripe · +49

New Zealand

NZD · stripe · +64

United Kingdom

GBP · stripe · +44

What "genuinely local" means in code

Payments & money

The rails people actually pay with — on a double-entry ledger.

In Nairobi the norm is M-Pesa; in São Paulo it's Pix; in Manila, GCash. Every rail sits behind one provider interface with an async-outcome path for instruction-then-confirm rails, and the resolver prefers each market's local rail over cards.

Every movement balances to zero

Settlements, refunds, credit notes, payouts and promo discounts post as double-entry journal lines in each currency's true minor units — JPY and KWD included.

Refunds that respect reality

Wallet debit first, then the gateway leg with compensation on failure; over-refunds are refused stating the max refundable.

Uncertainty never moves money

Payout reconciliation returns driver funds only on confirmed failure. Rails degrade to cash with no keys configured.

Rails, ledger and the honest-status system

Operator console — a completed trip with route, timeline and settlement

Pix (Asaas)live-tested

Brazil

Flutterwavelive-tested

Pan-Africa

Cash / manuallive-tested

Everywhere

Moyasarlive-tested

Saudi Arabia

Paystacklive-tested

Nigeria · Ghana

Razorpaylive-tested

India

Stripelive-tested

Global cards

xenditlive-tested

GCashunverified

Philippines

mercadopagounverified

M-Pesaunverified

Kenya

OXXOunverified

Mexico

tapunverified

Read the amber pills. 5 newer rails declare integration: 'unverified-adapter' in code until they clear a real transaction against the live provider — and the console shows operators exactly that, never a fake "Connected". With no keys configured, every market falls back to cash and nothing crashes. That honesty is a feature you inherit.

Built for operating, not just demoing

The unglamorous parts are the product.

Safety centre

Trusted contacts + SOS fan-out SMS with a live-trip link
Automatic ride check-in: long-trip and stationary signals escalate
Tokenized public trip sharing — identity, phone and money structurally excluded

Fleet partners

Revenue-share or fixed-lease terms per driver
Verify applications, see every fleet's cars, trips and earnings
Fleet withdrawals from the fleet's own ledger account

Markets & pricing

Per-market fares, surge zones and vehicle types
Promos with per-user and global caps
Corporate accounts billed on the ledger

Live dispatch

Search riders, click the map, assign by name — no UUIDs
Driver and rider 360°, KYC queue, payout queue
Audit log with before-state snapshots; RBAC with a last-admin guard

Why trust code you haven't read yet

This codebase tells you the truth about itself.

Unverified means unverified

Payment adapters that haven't cleared a live transaction say so in code, and the console shows operators an amber pill — never a fake "Connected". The same honesty runs through the docs and this site.

Dormant by default

Anything that moves money or files with a government is credential-gated: no keys → deterministic local behaviour (cash rail, local invoice), loudly logged, never a crash, never a silent fake success.

No fake anything

No invented testimonials, no sales counters, no fabricated logos. Claims link to their proof: the live demo, the docs, the changelog, and test counts computed from the repo at build time.

The full honest-engineering story Read the changelog, bugs included

Watch it work

Two recordings, no narration, no cuts.

The console being driven by an operator, and a whole ride from the rider's phone — recorded against the live demo.

Operator console walkthrough

1 min 56 s

Sign in, then dashboard → live dispatch (map + queue) → trips, drivers, riders, vehicles, payouts, pricing, markets, providers, reports, safety, promos, CMS, settings.