Case study

A statewide network where the cities still own their data

A state DOT wants every county and city in its operating picture, and none of them want to become tenants on a vendor's platform. Veodyn brings them in as owners, not tenants.

02

The setup

A state DOT wants county and city traffic data in its statewide operating picture. Municipal signals, county incident feeds, local transit, all visible in one place so the state can coordinate across jurisdictions during a storm, a game-day surge, or a regional evacuation.

The locals are willing in principle. The county runs its own signal system, the two biggest cities each have their own, and a handful of small towns have almost no budget at all. None of them want to hand control of their data to the state's vendor. The small towns cannot afford a per-seat license on a commercial platform.

The state has to choose how to bring everyone in.

03

The data problem

The usual offer is a statewide license on one proprietary central platform. The state stands it up, and the locals federate onto it. It works, and it ships fast, but it has a cost that does not show up in the contract: the locals become tenants. Their data lives on infrastructure the state's vendor controls, governed by the state's contract, exportable on the vendor's terms. A small county that wants to leave later finds its history locked inside someone else's system.

So the bigger locals stall, the smaller ones cannot pay to join, and the statewide picture has holes in exactly the places the state most needs to see.

04

The Veodyn architecture

Veodyn federates without making anyone a tenant. Each local agency runs its own node, on its own infrastructure, owning its own data. The node normalizes the agency's feeds and publishes them into the statewide layer. The hub stitches every node into one consistent picture through a single open API and an AI query surface.

County and city signals (NTCIP) appear next to state freeway data
Local incidents and events (TMDD) flow into the same statewide map
Local transit (GTFS and GTFS-RT) shows up alongside roadway operations
A small town with no IT staff can run the free Community node and still join, at no license cost

The state gets the complete picture. Each local keeps ownership of its own data and can walk away with it. Joining the statewide network is a decision a local makes, not a dependency it takes on.

05

What the federated network can do

The capability	What powers it
Statewide coordination across jurisdictions	TMDD events and NTCIP signal status, normalized from state, county, and city nodes.
Local agencies join without a license fee	Open-core Community node, run on the agency's own infrastructure.
Each local keeps and can export its own data	Agency-owned nodes, not tenant accounts on a central platform.
Transit and roadway in one regional view	GTFS-RT and TMDD on the same normalized layer.
Add an agency without re-architecting	New node joins the existing normalized layer.

06

When a central platform is the better choice

A central platform is simpler to buy. One contract, one vendor, one throat to choke, and the state can mandate it. If the state does not care who owns the local data and wants the fastest possible path to a statewide dashboard, a central platform is a reasonable choice.

Veodyn wins when local buy-in and the absence of lock-in actually matter. On a central platform the locals are tenants. On Veodyn they are owners: their node, their infrastructure, their data, exportable on their terms. If you have ever watched a city refuse to join a state system because it would not give up control of its own data, that is the problem federation solves. The trade is that you are coordinating a network of owners rather than administering a single platform.

07

Why the holdouts say yes

Open-core is what lets the small town join for free and the big city join without surrendering control. Because the node code is open and the data stays with each agency, the statewide network is not locked to one vendor or one budget cycle. A local can adopt it without a procurement, run it without a license, and leave with its data intact. That combination is the reason a federated network reaches the agencies a central platform leaves out.

08

See it on your network

Tell us which locals you need in the picture and what is holding them back, and we will map the fit. Book a call.

09