Platform overview

One operation, one source of truth

Renaro is a dispatch operations platform: bookings, live assignment, driver workflow, passenger communication, payments, and reporting run against the same organization-scoped data. There is no sync between a booking system and a dispatch system — they are the same records.

Everything your operation does is an event on a booking, a driver, or a ledger. That is why the platform can answer questions other systems cannot: the history is the data model, not an afterthought.

• Dispatchers work the live board: unassigned jobs, fleet state, and assignment evidence in one view.
• Drivers and passengers use mobile surfaces connected to the same records dispatchers see.
• Owners get ledger-backed reporting instead of exported guesses.

The shape of the system

The operator dashboard is a fast static web app talking to a single API. Realtime state — driver positions, booking transitions, board updates — streams over WebSocket. Slow, third-party, or retryable work (SMS, payment capture, route calculations) runs through a durable job queue so a provider outage never blocks dispatch.

• PostgreSQL is the source of truth; every tenant's rows are organization-scoped.
• Redis carries pub/sub fanout and the hot GPS stream.
• Jobs and webhooks are idempotent: safe to retry, impossible to double-apply.

Transparency as an architectural rule

Automated decisions in Renaro are explainable by construction. Dispatch scoring writes its factors next to the assignment. Pricing changes can be simulated against history before they go live. Money lives in a double-entry ledger where every leg traces to a booking.

The practical effect: when a driver, passenger, or accountant asks why something happened, the answer is a record you can open, not a support ticket.

Where to go next

If you are setting up a new fleet, start with the onboarding guide. If you are evaluating how Renaro thinks, read the dispatch scoring and ledger concepts — they are the platform's character in miniature.