Your AI needs context. That is what we build.

Vela Context is the new home of UNSBox and FIWAREBox. Same platform, sharper focus on the ETSI NGSI-LD open standard, and on what comes next.

The question changed

Five years ago, the operational data question was "how do we collect and store all this telemetry." It was a storage problem. Today, in cities, factories, ports, hospitals, and logistics corridors, the question is different: how do we make our operations legible to AI?

That is not a storage problem. It is a context problem.

AI agents and copilots are now real consumers of operational data. They do not read dashboards, they do not parse vendor-specific JSON, and they do not perform well on raw MQTT streams. They need entities with stable identifiers, typed relationships, semantic models, and provenance. Without that, AI initiatives stall in the same place every time: the messy gap between raw data and something a machine can actually reason over.

Vela Context exists to close that gap.

Context is a standard, not a vendor invention

There is already an open standard built precisely for this job: ETSI NGSI-LD. It specifies how to express entities, relationships, and semantic types in a way that is portable, vendor-neutral, and machine-readable. The Smart Data Models initiative provides the shared vocabularies for cities, industry, energy, water, agriculture, and more.

This is not a future bet. It is a published standard with growing adoption, sitting quietly underneath what every operational AI agent will need over the next decade.

Vela Context is a managed context platform built on the ETSI NGSI-LD open standard. The platform delivers an NGSI-LD compliant context broker, an adaptive pipeline that maps any source to validated Smart Data Models, and the tooling around it for security, monitoring, scale, and digital twins.

From two niche brands to one focused platform

For the past several years, we have been building this platform under two different names.

FIWAREBox spoke to smart city operators and mobility programs. They called what they needed "context data."

UNSBox spoke to manufacturing and process industry teams. They called the same thing "unified namespace."

Different audiences, different vocabularies, same engine underneath, same problem being solved. As the AI question moved into both audiences at the same time, two brands stopped looking like focus and started looking like fragmentation. Two storefronts, one warehouse, and a warehouse that looked smaller than it is.

Vela Context consolidates both into one platform with one name, named after the thing it actually delivers: context.

Why this name

Vela is a constellation, which ties the platform to our tooling family (CASSIOPEIA, LIBRA, TELESCOPIUM, CARINA, and the rest). Vela also means "sail" in Latin and several Romance languages, which carries a direction-of-travel meaning that "box" never did.

The word "context" is the working term used by the NGSI-LD standard, by Smart Data Models, by AI tooling, and by the operations teams now asking for AI-ready data. Putting it in the name aligns us with how this market will be talking for the next several years.

We chose to align with the open standard (ETSI NGSI-LD), not with any single foundation, vendor camp, or industry-specific dialect.

What does not change

For existing FIWAREbox and UNSbox customers, the change is the name on the door. Same team, same engineering, same NGSI-LD compliant broker engine, same SLAs, same integrations, same Smart Data Models. Existing deployments continue uninterrupted. Existing contracts are honoured exactly as written.

What is new is the sharper positioning, the unified roadmap, and the simpler conversation we can now have with everyone asking the same underlying question, regardless of whether they call themselves a city, a factory, a port, or a hospital.

What comes next

Explore the platform: the Vela Tools suite, the Starter Packs for cities, industry, mobility, logistics, and other verticals, and the pricing tiers built for direct procurement.

If you are coming from FIWAREBox or UNSBox: nothing on your side needs to change. Welcome to the same platform, now with a name that says what it does.