Connect the data you already have

Why it takes weeks today

Transport, energy, water and the building department each bought their own system. The same street sits in four vocabularies, so a question that crosses two departments turns into a meeting instead of a query.

What we put in place

A context broker over the systems you already run. It speaks NGSI-LD for the entities, DCAT-AP for the datasets and ODRL for the terms of use, so data stays where it lives and every owner decides who reads which part. A partner receives the subset your policy allows, and nothing else leaves your broker.

Proof, unedited

• A map of the shared bike stations, asked for in plain words and on screen in 92 seconds. Watch it
• An AI assistant asks the shared endpoint what is on in Helsinki and gets the list back in 18 seconds. Watch it
• Claude Code builds a map app from the endpoint address alone, recorded with the clock running. Watch it

The measurements behind the platform, taken across a city, its region and a university, are on the platform page.

How a project starts

1. Inventory. We map every system that holds your data: protocol, model, owner, refresh rate, and who may read it.
2. Pilot on one question. We take a question your teams already ask across two or three systems and make it one NGSI-LD query.
3. Roll out. Adapters, models and access rules move to your infrastructure or ours. Your teams keep the tools they know.
4. Open to partners. When a neighbouring organisation should read part of your data, its connector negotiates the terms and your policy decides the rest.