Aero Logistics OS isn't another fleet dashboard. It's an event-sourced execution engine where every action creates an immutable record — not a row update.
We believe fleet operations deserve the same data integrity guarantees as financial systems. That belief shaped every architectural decision.
Evolution
From phone-call dispatch to sub-second event-sourced intelligence. Scroll through the three eras of fleet management.
Principles
Every action is visible. Every event is attributed. No black-box algorithms — the dispatch engine logs every decision step for full operator visibility.
The job_events table is your compliance backbone. Append-only, immutable, and replayable. Built for regulators, insurers, and legal disputes — not just dashboards.
Sub-second driver assignment via real-time constraint scoring. Schedule overlap rejection at the DB layer. Zero wasted dispatch cycles.
Philosophy
Traditional logistics systems write state. A job goes from “pending” to “assigned” and the original record is gone. When disputes arise, there's nothing to replay.
Aero OS writes events. Every state change is a new row in an append-only log. The current state is always a derived snapshot — computable from the event trail at any point in time.
This means full lifecycle replay, compliance-grade audit trails, and dispute resolution based on timestamped, attributed facts — not reconstructed memory.
Architecture Model
Client / Driver App
No direct DB access
Server Actions (RPC)
Validates & writes events
handle_job_event()
Appends to job_events
jobs (snapshot)
Derived state — never written directly
“Every action is an event. Every event is traceable. Every job is replayable.”