Warehouse
The system of record for your transportation data.
Transportation data infrastructure
One source of truth for everything your region operates.
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.
You know the symptoms: no single source of real-time information, riders and partners working across separate apps and systems, and the demand-response, rural, and micromobility services that never make it into a shared feed at all.
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
No lock-in, by design.
Procurement is turning against lock-in: agencies now write open interfaces, best-of-breed, and plug-and-play into their requirements. ITS Feed is built that way. Each member agency runs an open-source node, free to deploy and operate; your hub aggregates across those nodes into one warehouse, one API, and one visualization layer. You pay for the hub, not the agencies. If the hub dissolves, the nodes keep running.
Why now
The money and the mandate are both moving.
Federal programs are funding regional data hubs and open transit-data standards, and state DOTs are writing open interfaces into their requirements. The closed, single-vendor stack is becoming disqualifying. The agencies that stand up a data layer now own the standard their neighbors integrate against next.
Start here