Single agency, no hub
One node, standalone. The full stack on one agency's data, with nothing to aggregate. Join or stand up a hub later without re-architecting.
For a single agency or a pilot
Free, open-source →Architecture
Nodes feed a hub. You own all of it.
This page covers two things: how Veodyn is built, and the scales it deploys at. The shape is the same at every scale. Each node sits inside its agency's network and normalizes that agency's data. The hub is the customer-side instance a regional operator or state DOT runs; it aggregates across nodes. The architecture is single-tenant end to end. No Veodyn-operated multi-tenant service exists, and data never leaves your environment.
Inside a node
A node is a full platform instance: adapters, normalization, a local warehouse, REST and WebSocket APIs, and a visualization layer with an MCP endpoint. A node functions standalone. An agency without a hub deploys just a node and gets the full stack against its own data, free.
Inside a hub
A hub has the same five surfaces on the operator's own data, plus federation features that only make sense across nodes: a federation control plane (node registration, keys, fleet health), cross-agency aggregation, selective hub-to-node pushdown, and optional cross-agency SSO. The federation layer is what the hub buyer pays for.
How data moves
Default direction is node to hub: each node ships normalized data upward on a configured cadence. Pushdown is hub to node, selective only: the hub propagates specific data sets back when configured, typically cross-agency incidents or regional weather. There is no direct node-to-node path; cross-agency communication always routes through the hub.
Deployment patterns
Same architecture, three scales
The shape above does not change as you grow. It just adds nodes. In every case the customer owns the infrastructure: cloud account, on-prem, or self-hosted. No multi-tenant SaaS exists.
Regional hub with members
A commercial hub aggregates across member-agency nodes and selectively pushes data back down. This is the primary motion.
For a regional coalition or operator
Commercial hub →State DOT or federal program
The same architecture at scale. The state or federal program runs the hub; sub-jurisdictions run nodes for statewide reporting and multi-jurisdiction analytics.
For a state DOT or federal program
Talk to us →Own the whole stack.
The node is free and open-source; the hub is the commercial federation layer. Either way it runs on infrastructure you control, and your data never leaves it.