Adapters
Pull from the agency's existing systems: signal controllers, AVL/CAD, fare collection, ITS feeds, and custom sources. Standard adapters cover GTFS-RT, TMDD 3.0, NTCIP, and GBFS.
01
Product
Five surfaces, one substrate
A node is a complete platform instance scoped to one agency. It ships all five surfaces below. A hub runs the same five on its own data, plus federation features that aggregate across nodes. Same building blocks, two scales.
02
The surfaces
What each one does
Normalization
Harmonize incoming data against those standards and the agency's own schema conventions. Resolve units, time zones, identifiers, and reference frames into one shape.
Warehouse
Local storage on infrastructure the agency controls. The node is the system of record for that agency's transportation data.
APIs
REST and WebSocket. Real-time streaming and historical query. The agency's own systems consume directly, with no intermediary service.
Visualization
Embeddable widgets, dashboards, a copilot, and a native Model Context Protocol endpoint for agents.
03
Node and hub
The same surfaces, two scales
An agency without a hub deploys just a node and gets the full stack against its own data, free. A region or state runs a hub: the same five surfaces on aggregated data, plus a federation layer that registers nodes, aggregates across them, and selectively pushes data back down.
See the architecture → See the deployment patterns →
Book a call