# Nodes feed a hub. You own all of it.

> How Veodyn is built, from a single node to a hub to a region: anatomy, data flow, and the three deployment patterns. Data never leaves your environment.

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.

> **Diagram.** Agency nodes send normalized data to a hub, which serves planning, public dashboards, federal reporting and AI agents; the hub selectively pushes data back to nodes.

## Inside a node

A node is a full platform instance: adapters, normalization, a local warehouse, a REST API, and a visualization layer with an MCP endpoint. WebSocket streaming is an Enterprise capability. A node functions standalone. An agency without a hub deploys just a node and gets the full stack against its own data, free.

> **Diagram.** Inside a node: adapters feed normalization, which feeds the warehouse, which serves the APIs and the visualization and MCP layer.

## 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.

> **Diagram.** A hub has the same five node surfaces plus a federation layer: control plane, cross-agency aggregation, pushdown, and optional SSO.

## 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.

> **Diagram.** Three rules: node to hub by default; hub to node selectively; never node to node directly.

## 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.

> **Diagram.** A single agency runs one node that serves its own analysts; no hub.

### 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](https://veodyn.com/editions/)

> **Diagram.** Three agency nodes feed a regional hub that aggregates across them.

### 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](https://veodyn.com/editions/)

> **Diagram.** Many sub-jurisdiction nodes feed a state or federal 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](https://cal.veodyn.com/sawinyh/30min)

## 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.

- [Compare editions](https://veodyn.com/editions/)
- [See the case studies](https://veodyn.com/solutions/)
- [Book a call](https://cal.veodyn.com/sawinyh/30min)

---

Source: https://veodyn.com/architecture/
This is the plain-Markdown twin of that page. Every page on this site has one at the same URL with ".md" appended, or by sending `Accept: text/markdown`. Site index: https://veodyn.com/llms.txt