Project Case
Designing a Multi-Tenant Ride & Logistics Platform
How I designed and led backend development for a multi-tenant transportation platform supporting bookings, driver fulfillment, pricing, real-time communication, and multiple client-specific workflows.
Context
The platform needed to support more than a basic ride-booking flow. Multiple client companies could operate transportation services through the same platform, while customers could book rides through a customer application or WhatsApp and drivers could fulfill them through a dedicated driver application. Operations teams also needed tools to monitor rides, manage drivers, handle exceptions, and intervene when automated workflows could not complete successfully.
Constraint
The system needed to support different companies without creating separate implementations for every client. Pricing rules, driver eligibility, ride workflows, and operational behavior could vary between companies. The platform also needed to maintain a consistent ride lifecycle across different booking channels while supporting real-time location, communication, fare negotiation, payment-related workflows, and production-scale operations.
Approach
- Mapped the complete ride lifecycle from booking and driver discovery through assignment, fare negotiation, confirmation, trip progress, completion, and settlement before implementing individual APIs.
- Designed the backend around a shared ride lifecycle so bookings originating from the customer application, WhatsApp, or operational dashboard could enter the same core workflow instead of maintaining separate business logic.
- Built company-aware pricing logic supporting time-based pricing, distance-based pricing, tiered distance bands, time-of-day surcharges, per-stop charges, and passenger-based charges.
- Separated shared platform behavior from company-specific configuration so new client requirements could be introduced without duplicating the entire ride system.
- Designed driver matching around eligibility, availability, location, current ride state, and company-specific requirements rather than simply selecting the nearest driver.
- Added real-time capabilities for workflows where immediate updates were important, including driver location, ride status, customer-driver communication, and fare synchronization.
- Designed operational recovery paths for cases such as driver reassignment, cancellation handling, and exceptional ride states so operations teams could resolve issues without engineering intervention.
- Kept backend services as the source of truth and treated client applications and communication channels as interfaces to the underlying business workflows.
Result
The resulting backend became a reusable multi-tenant transportation platform supporting 15K+ completed rides per month, with bookings coming through both WhatsApp and the customer application and fulfillment handled through a dedicated driver application. The architecture allows new client-specific requirements to be implemented as extensions to the existing platform instead of separate applications.
Lesson
Multi-tenancy is not only a database concern. It affects pricing, authorization, workflows, integrations, configuration, and operational behavior. A reusable platform needs to define what should be shared, what should be configurable, and what must remain isolated before implementation begins.