SenLab d.o.o.

SenLab d.o.o. is a technology company from Ljubljana, Slovenia, EU. We operate Vela Context Data Hub (velacontext.com), the data layer beside the platforms a city already runs.

Your parking, traffic, air quality, waste, cameras, utility systems and earlier FIWARE pilots stay in place. Vela connects them on the European standard for city data, ETSI NGSI-LD, the same standard adopted across EU data spaces, and keeps the history. The result is one real-time API across every source, and one record you share with the parties you owe answers to: a river authority, a transport operator, a partner city, the European Commission.

In production: a large Dutch city runs Vela under the GIBIT municipal framework, with AI cameras and sensors feeding one NGSI-LD layer. OASC MIM1 and MIM2 in production. PROSAFE-TWIN under Horizon Europe. Code public on GitHub under EUPL 1.2.

Three fixed-scope entries, each ninety days and below procurement threshold:

1. An evidence record you defend. A continuous, timestamped record across systems and organisations behind one decision: flood and storm events, operator performance against contract, alert chains.

2. A live feed under your digital twin. Your twin stays yours. Vela feeds traffic, transit, weather and sensor data in NGSI-LD with history, and gives project partners governed access.

3. A conformant feed into the space you report to. TEN-T urban node indicators due 31 December 2027, High-Value Datasets, national data spaces, DCAT-AP catalogues. Your sensor register lists devices. Vela publishes what they measure.

For automation and IT teams, Vela is a production-grade environment for integration and testing without building infrastructure first. SandBoxOS underneath carries 130 or more open-source packages pre-installed, so teams validate vendor integrations and feed Local Digital Twins from day one.

Deployment as a dedicated EU cloud instance or on your own servers, under your jurisdiction, with integrated security, automatic updates and GDPR compliance. No hyperscaler dependency. Every client keeps the data, the models and the standard, and receives a quoted exit price on day one.