- Role
- Full-stack developer · Vozi
- Year
- 2025
- Type
- Enterprise
- Status
- Shipped
Overview
Corporate travel usually runs across phone calls, spreadsheets and vendor invoices nobody can verify. Corpora puts corporates, vendors, drivers, fallback vendors and internal admins in one system that follows a ride from booking to reconciliation. Billed distance is checked against GPS mileage, every ride starts and ends with an OTP, invoices are generated from the trip record, and compliance rules raise alerts and track SLAs. If a vendor can't take a trip, it is reassigned to a trusted fallback vendor. At Vozi I worked across the front end and the API, building the role-based dashboards, booking flows and trip tracking.
At a glance
- stakeholder roles in one closed-loop system
- 5
- stakeholder roles in one closed-loop system
- booking modes: single, bulk, recurring and event
- 4
- booking modes: single, bulk, recurring and event
- core modules, booking to reconciliation
- 8
- core modules, booking to reconciliation
System sketch
A simplified view of how the main parts connect.
What I built
Ride booking engine supporting single, bulk, recurring, and event-based travel
Live GPS tracking with route deviation checks and OTP-verified ride start/end
Automated fare computation and reconciliation with invoice proof validation
Fallback trusted-vendor allocation to prevent service disruption
Role-based dashboards for corporate, vendor, driver, and admin stakeholders
Policy and compliance engine with audit logs, alerts, and SLA monitoring
Vendor and fleet lifecycle management with compliance scoring
Exportable reports on utilisation, cost and vendor performance
Gallery
01 / 05Admin dashboard: trip, SOS and revenue totals, SLA performance and a revenue trend
Stack
- Fastify
- Drizzle ORM
- Better Auth
- TypeScript
- SQL
- REST APIs
- Modular Backend Architecture
Next case study
Drova