Architecture

Nodes feed a hub. You own all of it.

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 ITS Feed-operated multi-tenant service exists, and data never crosses customer boundaries.

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.