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. Veodyn 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.
FAQ
Common questions about Veodyn
What is Veodyn?
Veodyn is transportation data infrastructure for a region. Every agency runs a free, open-source node that normalizes its feeds, and a regional hub aggregates those nodes into one warehouse the region owns, with a single API and visualization layer on top.
Is Veodyn open source, and is the node free?
Yes. The node is free and open-source, so any agency can deploy and operate it at no cost. The hub is the commercial part: you run it as a subscription or have us manage it for you. You pay for the hub, not for the agencies that feed it.
How much does Veodyn cost?
The node costs nothing to deploy or run. The hub is a subscription you operate yourself, or a fully managed service we run for you. Pricing scales with the hub, not the number of member agencies, so adding a node never adds a license cost.
Does my data stay private?
Yes. Veodyn is single-tenant end to end. Each node and hub runs inside your own infrastructure and your data never leaves your environment. AI access through the MCP endpoint reads your system of record directly instead of copying it out.
What data formats and standards does Veodyn support?
Veodyn normalizes the standards transportation agencies already publish: GTFS and GTFS-RT for transit, TMDD and NTCIP for traffic management, GBFS for micromobility, and your own feeds through custom adapters. Everything lands in one consistent schema in the warehouse.
Can I use AI on my transportation data?
Yes. Every node and hub ships a native Model Context Protocol (MCP) endpoint. Agents like Claude and GPT query the same normalized warehouse an analyst does, grounded in your system of record, without anything leaving your environment.
Who runs the node and who runs the hub?
Each member agency runs its own node, or the region hosts one on its behalf for agencies with no IT staff. The hub is run by the region that owns the data layer, as a subscription or as a service we manage. If the hub dissolves, the nodes keep running.
Start here