Live today on real city data

Connect a source once.
Every system can use it.

Each source you plug into Valo instantly becomes a provider for every other system — and a consumer of all of them. One shared layer, not a tangle of point-to-point integrations.

Proven now: 16 Helsinki open-data sources across 9 protocols, fused into one real-time situation layer.

Stop building integrations one pair at a time

Every system that wants to share data with every other normally needs a custom connection for each pair. Valo replaces that with a single shared layer in the middle.

Without Valo N × M connections

Every new source means re-integrating with everything already connected. The cost grows with the product of both sides.

With Valo N + M connections
VALO

Each source connects to Valo once. From that moment it can serve, and draw from, everything else on the layer.

One pipeline, any source

However the data arrives — a REST poll, a real-time stream, a webhook push — it lands in the same shared model. Consumers never know or care which source produced it.

01

Connect

Point Valo at any API, stream, or device — or have the source push to its own ingest endpoint. 9 protocols supported out of the box.

02

Normalize

Raw payloads become a small set of shared types — Observation, Event — each carrying source, timestamp, and provenance.

03

Distribute

Everything flows through one event backbone. Pulled or pushed, the data looks identical to whoever reads it.

04

Reuse

A map, an alert, a report, an AI agent — every consumer reads the same fused layer. No new integration per use.

Different shapes in, one model out
Traffic API (REST/JSON) Observation(traffic_density)
FMI weather (OGC WFS/XML) Observation(wind)
HSL transit (GTFS-RT/Protobuf) Observation(vehicle_position)
Open311 (webhook push) Event(issue_report)

Every source is both a provider and a consumer

There's no separate "publisher" and "subscriber" tier. The moment a system joins the layer, it can offer its data to everyone and combine everyone else's — and that's where new value appears.

Weather + Traffic
Congestion risk
Events + Transit
Crowd-flow pressure
Open311 + Location
Incident mapping

None of these combinations needed a new integration. They are reads against data that was already on the layer.

Running today

Proven on a real city

Our public demo connects 16 Helsinki open-data sources across 9 protocols into one live situation layer — with 2,500+ national datasets discoverable behind it. This is the substrate working, not a mock-up.

Transport & mobility

  • HSL real-time (stream)
  • Traffic volumes
  • Routing & stops

Environment

  • FMI weather
  • Geospatial / boundaries

City & services

  • Service Map
  • Open311 issues
  • Linked Events

Data & demographics

  • HRI catalog
  • Statistics & postal areas
  • Schools

Where Valo fits

The same primitives — connect once, normalize, reuse — apply anywhere independent systems need to share an operational picture. Civic is what's proven today; the architecture is built to extend.

Proven today

Government & city operations

Agencies and municipalities publish APIs that rarely talk to each other. Valo turns them into reusable data — already live across 16 Helsinki-area sources.

  • One integration, many downstream systems
  • Cross-agency reuse without duplication
  • Discoverable data with provenance
Adjacent fit

Critical infrastructure

Power, water, transit, ports — each runs its own systems. Valo brings them onto a shared operational layer without forcing anyone onto one platform.

  • Cross-domain situation awareness
  • Independent systems stay independent
  • Real-time visibility across operators
Forward direction

Defence & multi-source operations

Drones, radar, RF, EO/IR, comms — independently built, rarely interoperable. The same shared-model approach connects them into one picture, with trust-aware fusion on the roadmap.

  • Multi-source operational picture
  • Cross-vendor by design — no lock-in
  • Trust-aware fusion under stress (in development)

What's proven, and what's next

The civic demo proves the substrate moves data reliably. The next tracks move the picture from how much data flows to how much can be trusted.

Working today
  • 16 live sources across 9 protocols (pull + push) into one model
  • Real-time stream fused with slow reference data
  • Dynamic source registration with auto-detected schema
  • Provenance and source carried on every record
In development — the trust engine
  • Entity stability — identity persistence, split & merge rates
  • Negative evidence — "expected signal absent" becomes a real observation
  • Reconnection honesty — backfill state shown, so the picture stays trustworthy
  • Fusion provenance — which observations formed an entity, with what weights

Principles

Adapters stay flexible. The shared model stays strict.

Shared meaning before shared interfaces

Data is normalized into a common structure before it is exchanged.

Connect once, reuse everywhere

Each source integrates once and becomes reusable across systems.

Sensitive access stays under customer control

Protected systems are reached through controlled connectors and delegated authority.

Built for federation, not silos

Systems act as both providers and consumers in a shared layer.

Policy travels with data

Access, classification, and provenance remain attached to data.

Resilient by default

When a source goes down, the last known-good data is served and clearly marked.

Valo is not another system

Not a sensor platform Not a data dashboard Not an API gateway

It's the interoperability layer that lets independent systems work together in real time — each one a provider and a consumer at once.

See it move real data

The fastest way to understand Valo is to watch sixteen unrelated city feeds become one live picture.