The public website and booking widget, the API layer, the admin dashboard your team logs into, and your isolated database are four faces of one backend management system — each reading from and writing to the same core.
Eight modules cover the full back office — from the live dispatch board your team lands on, through fleet, rates, billing, reports, staff accounts, email, and payment handling.
Updates in real time over a server-sent-events stream — no manual refresh. Status flows assigned → en route → arrived → in progress → completed, live for everyone.
Vehicles, license and background-check status, and your driver roster all live in one place. Onboard drivers and assign vehicles without a separate spreadsheet.
Flat, hourly, and mileage-based pricing per vehicle, with zone overrides. Promo codes and tip handling are built in. Edit a rate once and it surfaces on the widget automatically.
Standing accounts with net-terms invoicing. Corporate rides attach to the right profile and generate an invoice — billing is a side effect of completing a ride.
Revenue summary, revenue over time, ride status breakdown, and driver performance — all from one schema, assembled automatically.
Role-based staff accounts with Admin sub-roles (Owner, Dispatcher, Accountant). Optional two-factor authentication, email-verified setup, self-service password reset.
Automated branded confirmation emails go out on booking and on confirmation — in your brand, the moment a reservation is created.
Optional one-time card payment for a ride's fare through a hosted Stripe Checkout session — not a saved card on file with automatic charging.
Admins, drivers, and riders are all managed from the same backend — each with their own role, permissions, and lifecycle.
Your back-office team
Provisioned with scoped sub-roles — Owner, Dispatcher, Accountant — and can enable optional two-factor authentication.
Can do
Chauffeurs on the road
Onboarded by an admin with vehicle assignment and license/background-check status. Access is through authenticated API access — there is no dedicated driver mobile app today.
Can do
People who book
Created on booking and tied to corporate accounts and booking history. There is no separate customer self-service portal — riders book through the widget on your site.
Can do
These eight modules are the "what." For the "how" — the four-layer architecture, a booking's path from quote to report, and the six security layers between a request and your data — see How it Connects.
See the architectureDrivers do not want a complicated tool. They want their rides, their status, their map, and their pay — in that order, on one screen, with no logins to fight.
A spreadsheet can hold your rides. It cannot push a new booking to a driver’s phone, update a rider’s ETA, or stop a double-assignment. It is time to retire it.
Tell us about your fleet and current setup — we will walk you through exactly how the central backend would manage your website, drivers, customers, dispatch, and billing.
