Operational platform · Fleet network operations

RouteSentinel

A three-pane fleet NOC console that runs from a single file.

Build something like this

In production since Jan 2025
8 delivered capabilities

RouteSentinel interface — a three-pane fleet noc console that runs from a single file — Interface rendering of RouteSentinel, produced from the system's real screen architecture. The live installation sits behind client authentication.

Overview

A network operations console for a transport control room: live fleet state, a vehicle routing optimisation pipeline, speed-limit modelling against real road geometry, and SOS handling — delivered as one self-contained vanilla JavaScript file that needs no build step.

The problem

Control-room tooling is usually a heavy single-page application that takes thirty seconds to load on the shift terminal and breaks when the build pipeline drifts. Operators need something that opens instantly and keeps working when the network does not.

How we approached it

No framework, no bundler, no package manager — one file, twelve iterated builds. Routing runs through OSRM, street addresses resolve against a self-hosted Overpass instance so the console is not hostage to a public rate limit, and speed modelling matches road geometry with hysteresis so a warning does not flicker at the limit.

Where it stands

A console that loads in one request, survives a dropped connection and can be deployed by copying a file. The self-hosted Overpass extract removes the external dependency that would otherwise take the address lookup down.