Nexma Event Broker
A scalable way to track millions of people, vehicles, and machines — stream their live locations to dashboards and field devices, keep a detailed route history, and run spatial logic like geofences and zones.
Connectivity
Stream locations and readings from anything that moves or measures. Vehicles, vessels, aircraft, GPS trackers, sensors, and apps connect over the protocol they already speak — every update stored with its position and timestamp.





Legacy Challenges
Moving objects send a constant stream of positions over many protocols. Generic message queues have no notion of space or time, so updates arrive unordered, unlinked to the map, and impossible to replay as a route.
Devices speak HTTP, MQTT, TCP, WebSocket, and gRPC, each needing its own handler — and none of them understand space.
Core Capabilities
Nexma Event Broker takes location updates over any protocol, streams them live to dashboards and devices, stores every point as route history, and runs spatial logic as data flows through.
Ingest HTTP, MQTT, TCP, WebSocket, gRPC, and native SDKs through one broker, normalized into spatial events.
Product Benefits
One scalable layer to ingest location at any volume, stream it everywhere, keep the full history, and act on it in real time.
Stop maintaining a handler per device. A single broker takes HTTP, MQTT, TCP, WebSocket, and gRPC and turns every update into a position on the map.
The same stream feeds real-time dashboards and the permanent record in the DataBase — one system for what's happening now and everything that led to it.
Geofence, zone, and proximity rules fire alerts and trigger workflows in real time, so the gap between an event and a response is milliseconds, not hours.
Feature Details
Nexma Event Broker ingests, streams, stores, and acts on location updates from millions of objects at once.
HTTP, MQTT, TCP, WebSocket, gRPC, and native SDKs through one normalized ingest path.
Absorb millions of events per second from fleets, sensors, and live feeds without backpressure.
Each protocol's payload is mapped into typed spatial events on the way in.
Related Products
One platform for all spatial data and workloads, from design to field operations.
FAQ
It is the platform's real-time location layer. It ingests position and sensor updates from any protocol, streams them live to dashboards and devices, stores each point as route history, and runs spatial logic — geofences, zones, proximity — as the data flows in.
HTTP, MQTT, TCP, WebSocket, gRPC, and native SDKs, all normalized into typed spatial events through one ingest path.
The broker streams telemetry into the DataBase's compact, time-aware store, so live positions and full historical recall come from one system rather than two pipelines.
Yes. Thresholds and geofences fire agentic workflows the instant they're crossed, collapsing detection-to-response from hours to milliseconds.