Platform
One context over the systems your city, region or company already runs. Data stays where it is, every owner decides who sees what, and your teams keep the tools they know.
One place to ask
Every system you run keeps its own database, and that does not change. Above them we place a context broker: one description of each real thing in your city or company, a street, a substation, a sensor, a room, written in the European standard NGSI-LD. Your people and your applications ask that one place a question instead of asking twelve systems twelve different ways.
A question like “every temperature sensor in this district and the building it belongs to” gets one answer, even when the sensors, the district map and the building register live in three different systems bought from three different suppliers.
Nothing moves, nothing is replaced
The water utility keeps its database and its rules. The traffic department keeps its own. A city dashboard still shows water next to traffic, because the brokers know about each other: a question arrives at one of them, travels on to whoever holds the answer, and comes back as one merged reply.
We check that nothing was copied along the way rather than assume it. Each department stays the owner of its data, which is usually the condition under which it agrees to share at all.
Every owner decides who sees what
Access rules are written in plain terms: this partner may read these kinds of data, within this area, under this condition. The rule is applied before a question reaches the data, so a partner who asks for more than they may see receives exactly the permitted part and nothing else. There is no error to argue about and nothing to filter afterwards.
Between organisations, a city and its region, a plant and its utility, the owner wants an agreement before the first byte moves. The platform handles that agreement once, through the European data space standards, and every later exchange runs under it.
What feeds the context
Most of the work in a project sits below the broker, in connecting what you already have.
- Sensors and telemetry: traffic counters, air quality, public transport positions, building meters, updated as measurements arrive.
- Maps and geometry: GIS layers and cadastral records, so a road or a parcel keeps its real shape.
- Registers and files: asset databases, spreadsheet exports, BIM models of buildings.
- Events and records: roadworks, cultural events, permits in progress, the notices a city publishes.
Models that keep their meaning
Two systems can exchange a record only if they mean the same thing by it. We build on the published Smart Data Models where they fit and extend them where they do not, and every extension is written down and handed over. The models describing your city are yours: you keep them, version them and take them with you, whoever runs the platform later.
When something has no agreed meaning yet, the platform shows the gap instead of hiding it. That is how a vocabulary problem becomes a short meeting rather than a wrong number on a dashboard.
Running it
The platform runs on your infrastructure, on a managed cluster in an EU region you choose, or on one server for a pilot. You receive the deployment, the models, the adapters and a runbook written for someone who was not in the project. Replace us later and it all keeps running.
What is not there yet
We would rather you hear it from us. A partner can read the current state of your shared data; the history behind it still has to be copied before it can be charted. Writing into a partner’s data under an agreement is designed and not yet delivered, so today a partner reads.
What we leave to others
We do not sell dashboards, devices or digital twins. Visualisation goes to whatever tool your teams already open in the morning, and we hand it one joined context to draw from.