Rider Booking App
Set a pickup, pick a vehicle class, see the fare before confirming, and watch the captain approach. iOS, Android, and a booking website that shares the same account and fare engine.
Booking
Vehicle classes
Upfront fare
Live tracking
Safety
Payments
Captain App
Go online, take trips, get paid. Requests arrive with pickup distance and fare visible, navigation covers both legs, and the earnings ledger reconciles against the payout the console sends.
Onboarding
Online & zones
Trip requests
Navigation
Waiting & tolls
Earnings
Fleet & Dispatch Console
The operator's surface: a live map of every vehicle and trip, manual dispatch for phone bookings, and the configuration that governs fares, zones, surge, and captain payouts.
Live map
Manual dispatch
Fares & surge
Captain management
Vehicles
Payouts
Corporate Portal
The surface that makes B2B revenue practical: companies add employees, set travel policy, book on account, and get one monthly invoice instead of hundreds of individual receipts.
Employee accounts
Travel policy
Book on behalf
Cost centres
Monthly invoicing
Reporting
Ride Types, Set as Configuration
Each type is a set of rules on the same engine — vehicle class, fare model, matching radius, and cancellation policy. Adding one is a form, not a release.
City rides
Airport transfers
Outstation & intercity
Rentals by the hour
Employee transport
Scheduled rides
One Ride, Across All Four
The apps are separate surfaces on one state machine. A single trip moves through them without anyone re-keying it.
Trip requested
Captain matched
Pickup and trip
Watched and corrected
Billed and settled
Safety and Compliance, Built In
Ride-hailing carries obligations delivery does not. The passenger and captain surfaces ship with the controls regulators and riders expect, configurable per city.
Mobility FAQ
What ships, what you configure, and how mobility differs from the delivery branch.
Still have questions? Talk to our team
Is mobility a different platform from delivery? +
No. Mobility runs on the same core as DeliveryStack's delivery apps: the same matching engine, pricing rules, payments, wallet and admin. What changes is the front end, with riders instead of customers, captains carrying people instead of parcels, and ride types instead of order types.
Can we run delivery and ride-hailing together? +
Yes. Both run from one admin. A captain can be enabled for rides, deliveries or both, and if you launch as a super app, riders use one account and one wallet across services. Many operators start with one service and add the second once the fleet is stable.
How are fares calculated? +
You set a fare card per vehicle class and zone: base fare, per km, per minute, minimum fare, waiting charge and night charge. Surge multipliers apply by zone and time window. The rider sees the fare before booking, and it changes only for route changes, waiting time, tolls or extra stops.
Do you support cash rides? +
Yes. Cash, cards, wallets, UPI, and corporate accounts run side by side, with cash collections reconciled against captain payouts automatically.
What about local licensing and regulation? +
The software covers the controls regulators usually ask for: document checks, trip records, SOS, masked calling and transparent fares. Operating licences and permits are yours to hold in each city, and we configure the apps to match what your regulator requires.
Walk the Four Apps With Us
We'll open the real builds against your city, your vehicle classes, and your fare rules, then show the same trip move through all four surfaces.