PARTNERS / SENSOR AND DEVICE MAKERS
SELL INTO EUROPEAN CITIES
WITHOUT BUILDING A EUROPEAN CLOUD
CITIES BUY SENSORS FROM ANYONE. THE DATA HAS TO ARRIVE IN AN OPEN STANDARD, STAY INSIDE THE EU, AND COME WITH A PARTY THEY HOLD TO A CONTRACT.
VELA CONTEXT IS THAT LAYER AND THAT PARTY. YOU KEEP THE HARDWARE SALE AND THE CUSTOMER. WE SELL NO SENSORS.
WHY SENSOR VENDORS WORK WITH VELA CONTEXT
REASON ONE
A EUROPEAN CITY ASKED YOU FOR AN NGSI-LD OR SENSORTHINGS FEED
The city runs Vela or another open data layer and wants your readings in the standard, with history. Send us one payload. We publish the mapping, your device plugs in, the city stops asking. Free, in two weeks. If your device is in the LoRa Alliance device repository, we reuse your own decoder and you are half listed already.
REASON TWO
YOU ARE ENTERING THE EU MARKET AND YOUR CLOUD FAILS THE TENDER
GIBIT in the Netherlands, EVB-IT in Germany, data residency everywhere. A portal hosted outside the EU loses before the datasheet is read. We become your European contract party for the data layer. You ship hardware, we sign with the city.
A filter before you read on. Where does your customer's data live after twelve months? If the answer is your portal and your login, your portal is your product and we are the wrong partner. If the answer is an export on request, your portal is a demo, and this page is for you. Keep your portal. Add one forwarding rule.
THREE QUESTIONS EVERY EUROPEAN TENDER ASKS YOU
You answer the hardware questions already. These three are about the data, and they decide the bid.
Will my data format be
accepted?
We map your device payload once to ETSI NGSI-LD and the Smart Data Models and publish the mapping as open code under EUPL 1.2. Your bid gains the standards sheet the tender asks for, without you writing a line.
Inputs today: JSON, REST, MQTT, CSV, OPC-UA.
Roadmap: ChirpStack, The Things Stack, ThingsBoard, LoRa Alliance device repository.
Output: NGSI-LD, Smart Data Models, DCAT-AP.
On request: OGC SensorThings.
IS MY CLOUD ALLOWED?
Your portal stays yours. The city copy of the readings lives in the EU, in the region the city picks, under the city's jurisdiction, with history the city owns and exports any day. No hyperscaler in the chain.
WHO SIGNS WITH THE CITY?
We do. The city signs with a European company for the data layer, the SLA and the exit clause. You keep the hardware sale and the customer relationship. We never sell sensors, so we never compete with you in the same tender.
One contract, one number, EU jurisdiction.
Works WITH LORAWAN, MQTT, REST, OPC-UA and others
No new firmware, no new cloud. Your readings leave your network server or your portal the way they do today, and land in the city record.
LORAWAN NETWORK SERVERS, ROADMAP
Decoded uplinks, device list, gateway metadata. Your repository codec will run unchanged. Dashed means in development.
IOT PLATFORMS AND PROTOCOLS
One rule-chain node or one topic subscription forwards readings. Your portal stays as it is.
STANDARDS OUT
The standards sheet your bid needs, written once, maintained in the open.
Every connector on this page is open code under EUPL 1.2, published the day it ships. Your devices work in the free edition of Vela as well as in the managed one. Certification pays for maintenance and support, never for access.
THREE WAYS ONTO THE LIST
Every route ends the same way: a validated Smart Data Model mapping in the public connector repository, your company and device named, repository codecs reused, not rewritten.
ROUTE 1
A CITY ON VELA ASKS FOR
YOUR DATA
The city needs your readings in the standard. We map one device family, publish it, and the city plugs your devices in. No city, no free mapping: our time goes where a deployment waits for it.
ROUTE 2
YOU MAP IT YOURSELF
The connector repository is open, the mapping format is documented. Fork it, write the mapping for your device, open a pull request. We review it and publish it under EUPL 1.2 with your name on it.
ROUTE 3
WE MAP IT FOR YOU,
NO CITY YET
You want to be ready before the tender. Send one payload, we quote a fixed price before any work starts, then map, validate and publish within two weeks of your go.
WHAT IT COSTS YOU
Your devices work in the free edition of Vela as well as in the managed one. You pay for our time when no city is waiting for it, and for maintenance once your city customers rely on the mapping.
LISTED
€0
when a city on Vela asks, or by
your own pull request
Mapping to a Smart Data
Model
Published as open code,
EUPL 1.2
Your name in the connector
catalogue
MAPPED FOR YOU
from
€490
one-off, no city required
€490 for a device in the LoRa
Alliance repository
€1,490 for any other JSON
payload
Fixed quote before work
starts
Published under EUPL 1.2
CERTIFIED
€1,900
per year, per device family
Certified connector badge for your bids
Mapping maintained across
codec, model and firmware
versions
Second-level support for
your city customers
Joint case study and listing
on this page
HARD PROTOCOL
€4,900
one-off
Private binary formats,
device management stacks
Delivered into the public
repository
Certification optional
afterwards
Bring us a city and you earn a finder commission under the Channel Partner Agreement. Resell the data layer with your hardware and the reseller rates apply. Prices exclude VAT.
WHAT THE TENDER ASKS FOR, BY COUNTRY
tell us about your device
One message from one device and who is asking for it. If a city on Vela asked, the mapping is free. If not, we send a fixed quote first and start only on your go. We reply within five working days. No demo call, no slide deck.
VELA CONTEXT DATA HUB · ONE SHARED DATA LANGUAGE FOR SMART CITIES · EU OPEN STANDARDS (NGSI-LD) · YOUR INFRASTRUCTURE, YOUR RULES