Logistics · 720-hour cycle
kaedax builds logistics and fleet software — dispatch boards, route-optimization engines, driver apps, last-mile delivery platforms — in a fixed 30-day (720-hour) cycle. Hours-of-service limits, ELD data integration, DOT compliance posture, vehicle-capacity enforcement, and proof-of-delivery are designed into the spec from day one, because a dispatch board that ignores HOS is a liability, not a product.
On-time delivery
96.4%
+3.1% wow
Active vehicles
38
of 42 fleet
HOS alerts
2
pre-violation
Open PODs
7
of 214 runs
[ §01 ] the problems we're hired for
FMCSA hours-of-service rules cap driving time at 11 hours in a 14-hour window, with mandatory 10-hour breaks. Dispatch systems that don't surface remaining drive time in the assignment UI create violations even when drivers are complying on their ELDs. We wire HOS state into every load-assignment card so dispatchers see the constraint before they assign the run, not after.
Time-window delivery SLAs, vehicle weight limits, hazmat routing restrictions, driver skill certifications — most off-the-shelf routers ignore at least two of these and surface the violations as phone calls at 7 a.m. We build constraint-aware routing that rejects infeasible assignments before they become dispatch mistakes.
A missing POD on a $40 parcel is $40; a missing POD on a $4,000 pallet can void the carrier liability claim entirely. Photo capture, GPS-tagged timestamps, and recipient signature are event-sourced at the driver app — not added later when a claim arrives.
Dispatch decisions made in spreadsheets, driver updates via WhatsApp, and ETAs calculated by feel — the pattern that works at 20 drops a day breaks at 200. We've built full dispatch boards for logistics operators and the pattern transfers: one surface, all state, zero heroic coordination.
[ §02 ] what ships
The shapes of logistics work that fit a 720-hour cycle. Every build ships with runbooks, monitoring, and 30–60 days of post-launch on-call.
Real-time vehicle map, load-assignment queue with HOS-aware driver cards, exception surfacing, and SLA countdown timers.
Constraint-aware routing: time windows, weight limits, hazmat restrictions, driver certifications — infeasible assignments rejected before dispatch.
Next-stop navigation, delivery task list, GPS-tagged proof-of-delivery (photo + signature), HOS status display, and offline-tolerant sync.
Customer-facing ETA links, on-time-delivery dashboards, exception alerting, and carrier-grade POD records for claims.
[ §03 ] proof
Our logistics posture is built on adjacent regulated work — see all case studies across fintech, healthtech, insurance, and AI products. The engineering disciplines transfer; the scope call establishes the specifics.
We expected a prototype. We got a production console with audit trails our compliance team was actually happy with. Three days early.
[ §04 ] questions
Off-the-shelf telematics run $30–40 per vehicle monthly on multi-year contracts; custom dispatch platforms from agencies quote $60,000–$250,000 over 3–6 months. kaedax prices per fixed 720-hour cycle, shared on the scope call. One cycle ships a dispatch board with route optimization, driver app, and POD tracking.
Yes — HOS remaining drive time is a first-class field in the dispatch data model. Driver cards in the dispatch UI show available hours before a load is assigned; the system rejects assignments that would put a driver into violation. We integrate ELD telematics feeds via adapter layers with contract tests around the vendor schemas.
Yes — time-window SLAs, vehicle weight and volume limits, hazmat routing restrictions, and driver certifications are modelled as hard constraints in the optimizer. Infeasible assignments are rejected at planning time with an explanation, not discovered by the driver at the delivery window.
GPS-tagged photo capture, recipient digital signature, timestamped delivery event — all event-sourced at the driver app and synced to the dispatch board in near-real-time. POD records are immutable and carrier-grade: suitable for liability claims and customer disputes.
Yes — adapter layers around your TMS, ERP, Samsara, Verizon Connect, or other telematics provider are scoped on the call. Vendor API quirks break our CI, not your dispatch ops. Integration depth is scoped honestly; deep bidirectional TMS sync may span two cycles and we say so upfront.
For a focused operation — a dispatch board with route optimization, driver app, and POD — yes. Multi-tenant fleet-as-a-service platforms with carrier onboarding, EDI integrations, and freight billing span multiple cycles, and we map that on the scope call.
A 15-minute scope call with a kaedax founder and the engineer who'd lead your build. We either fit your logistics product into 720 hours, or we tell you why not — same call.
▷ other verticals