Vikasa is an open-source transportation data fabric that helps agencies, vendors, and developers turn fragmented roadway data into shared, trusted streams.
Roadway data should move freely enough to support safety, operations, planning, and innovation. Vikasa helps unlock signals, sensors, connected vehicle data, and other infrastructure information so it can be reused across systems instead of trapped in silos.
So agencies keep control of their data.
So vendors plug into shared models instead of one-off integrations.
From traffic operations to digital twins.
Vikasa means growth, unfolding, and opening up.
Vikasa is an open-source transportation data fabric built to help public agencies and their partners free roadway data from closed systems. It creates a shared foundation for signals, sensors, connected vehicles, and analytics so more tools can work together with less friction.
The idea is simple: open infrastructure should stay open. Agencies should be able to govern their own data, vendors should compete on value, and developers should have a clean path to build useful applications without starting over every time.
From vendor lock-in to open infrastructure.
This overview explains why transportation needs an open, interoperable data fabric, how OpenITS works, and how Vikasa helps agencies modernize without replacing the systems they already own.
Transportation systems create valuable data every second, but too much of it is stuck inside disconnected devices, vendor platforms, and custom integrations.
Vikasa helps turn that fragmentation into a shared, governed data flow.
Vikasa brings together data from roadway devices, sensors, vehicles, and existing systems.
It organizes that data into clear, reusable models and event streams so different tools can understand the same information.
Applications, analytics, dashboards, and operational tools can use the same trusted data without rebuilding integrations again and again.
Vikasa is built for practical transportation outcomes, not just technical theory.
Support signal operations, corridor management, and better day-to-day decision-making with cleaner shared data.
Help power low-latency safety use cases for pedestrians, drivers, cyclists, and workers.
Connect roadway and freight data to improve visibility, timing, and access to real-time information.
Create a stronger data foundation for analysis, simulation, and digital representations of infrastructure.
Support long-term asset visibility with data that can be shared across operations, planning, and maintenance teams.
Make it easier to reuse information across departments, systems, and partners without starting from zero each time.
Vikasa is meant to be open, practical, and buildable.
Developers, integrators, and technical partners should be able to understand the architecture, explore the shared models, and build against a transparent framework. The goal is not to lock people into a product. The goal is to make it easier to build useful transportation tools on a common foundation.
OpenITS
OpenITS is an open, vendor-neutral vocabulary for intelligent transportation systems: a shared telemetry and control model for the road network, in the spirit of what OpenConfig did for networking. The standard lives at open-its.org.
vikasa-infra
The platform underneath. It provisions and secures the NATS/JetStream backbone that telemetry flows through: clusters, streams, and accounts, plus mTLS, JWT and nkey identity, PKI, secrets, and the cabinet leaf install, all managed through GitOps.
vikasa-demo
The whole architecture on your laptop. A faithful, containerized miniature of a multi-agency deployment that runs the full cabinet to regional to central to DMZ JetStream chain and federates it into a shared ClickHouse and Grafana view, so you can watch the end-to-end data path before you deploy anything.
vikasa-collector
The edge collector that runs in the cabinet. It polls signal controllers, RSUs, and other field devices over their native protocols such as NTCIP, normalizes each reading into a clean domain model, and publishes versioned OpenITS payloads as CloudEvents to the cabinet's local NATS JetStream.
Governance
The project is designed to support transparency, durability, and responsible participation as the ecosystem grows. Governance helps protect the openness of the core, clarify how decisions are made, and create a trusted structure for agencies, vendors, and contributors.
Our blog explores the ideas behind technology, offering thoughtful perspectives on the forces transforming how we connect, move, and innovate.
Open Infrastructure, Open Heart
Vikasa explains how it came to be, in its own voice: I was born in a research memo. Tech Memo 1, to be exact — a federally funded document about edge computing on roadway infrastructure, filed with a research center in McLean, Virginia. That is not, by any conventional measure, an origin story ...
Panthā / Panthās (पन्था / पन्थास्) — “path, road, course, way, manner,” with a strong sense of journey or passage; nice for an investor-facing “route to value.”
Use the contact form on this page to share a question, idea, partnership inquiry, or request for more information. Responses will be coordinated through the website while direct contact channels are being finalized.