Warehouse
The system of record for your transportation data.
Transportation data infrastructure
One data layer for every agency in your region.
Every agency runs a free node that normalizes its feeds. Your hub aggregates them into one warehouse you own.
The problem
Every agency's data lives in its own silo
A regional hub coordinates transit, freeway operations, traffic engineering, parking, non-motorized, and micromobility. Each member agency produces operational data in its own system, schema, and schedule. Aggregating it normally means a multi-year integration project or a closed analytics service nobody owns end-to-end.
The substrate
Five surfaces, on infrastructure you control
Normalization
Adapters for GTFS-RT, TMDD, NTCIP, GBFS, and your feeds.
Visualization
Dashboards, widgets, a copilot, and MCP endpoints.
APIs
REST and WebSocket. Real-time and historical.
Integration
We make it work, and keep it working.
The model
Open-source nodes. A commercial hub.
Each member agency runs an open-source node, free to deploy and operate. Your hub aggregates across those nodes into one warehouse, one API surface, and one visualization layer. You pay for the hub, not the agencies. If the hub dissolves, the nodes keep running.
Start here