CaboCab

Company work · private detailsJun 2024 - Aug 2026

Technical leadership across a live Node.js and MySQL mobility platform, including offline writes, private messaging, monitoring and support workflows.

Problem

A live mobility platform had to keep trip and support operations coherent through connectivity loss, retries, third-party cost anomalies and gaps in service visibility.

Implementation record

How I solved it

  1. 01

    Buffered trip writes locally and synchronised them after reconnection so a temporary network loss did not turn into a discarded trip update.

  2. 02

    Separated chat into a FastAPI and PostgreSQL SDK with UUID identities and idempotency keys; pilot-load tracing then isolated an idle WebSocket leak after an admin connection closed.

  3. 03

    Used self-hosted Docker OSRM map matching for the reported route drift, then extended monitoring and escalation across the operational path instead of treating routing, cost and support as separate incidents.

My role / what I owned

CTO and Technical Lead (Founding Team)

  • Set the Node.js and MySQL platform's founding technical direction and architecture as part of the company team.
  • Built the private chat SDK on FastAPI and PostgreSQL, using UUID identities and idempotency keys, then fixed an idle WebSocket leak found under pilot load.
  • Added offline trip-write recovery and self-hosted OSRM map matching after reported route drift.
  • Traced a reported Maps cost anomaly and built monitoring, escalation and driver-feedback workflows.

How it was built

Team
Work completed in the CaboCab company team. Nivish’s former founding-team role is public; the detailed implementation breakdown comes from his own account.
Tools
  • Node.js
  • MySQL
  • Docker
  • OSRM
  • FastAPI
  • PostgreSQL
  • UUID identities
  • Idempotency keys
  • Twilio
  • WhatsApp API
  • AWS S3
Use of AI
No project-specific AI contribution is documented for this work.

Source and current state

  • The public CaboCab affiliation confirms the CTO and Technical Lead (Founding Team) role.
  • The implementation details are my account of private production work and are not backed by a public repository or incident log.
  • The reported stories include a 5 to 10 percent route discrepancy, a roughly ₹12,000 daily Maps anomaly, monitoring across ten services and a support workflow used across six districts.
Status
Former CTO and Technical Lead (Founding Team) role. Nivish left CaboCab in August 2026; the platform was live in production during his time there, and the operational details on this page remain private company work.
What it shows
Nivish reports that the repaired systems have been used in production. No public impact metric is attached.
Public company affiliationOpens in a new tab