Robotics & drones
High-rate sensor and pose streams, fleet current-state, and geospatial queries on one engine — line-rate ingest with constant-time reads.
The problem
Why this is hard today
A robot or drone fleet emits high-rate sensor and pose telemetry continuously, and operations needs the live position and health of every unit right now — plus geospatial questions like which units have left their assigned area.
The usual stack splits pose streams into a processor, current position into a cache, and geospatial history into a warehouse — three systems that drift, and a fleet view that lags the units it tracks.
The fit is one engine that ingests pose and sensor streams at line rate, keeps per-unit current state as O(1) reads, and answers geospatial queries with built-in functions in the same SQL.
Where NYXDB fits
Use-case journeys
Pose & sensor ingest
Absorb high-rate pose and sensor streams durably, with backpressure instead of data loss.
IoT & telemetryLive fleet dashboards
Dashboards read keyed current-state tables and subscribe to live position updates.
Real-time dashboardsGeospatial in SQL
Proximity and geofence queries with built-in geo functions over live fleet state.
IoT & telemetryArchitecture
How NYXDB fits a robot fleet
Pose and sensor events append durably at line rate under the memory governor; keyed tables hold the latest state per unit; built-in geospatial functions answer proximity and geofence questions over the same data.
- 01
Line-rate ingest
Shard-owned, lock-free write paths, WAL-backed, governed under pressure.
- 02
Fleet state
Keyed tables keep the latest pose and health per unit — O(1) reads.
- 03
Geospatial
geo_distance, great_circle_distance, geohash, and H3 cell functions in SQL.
- 04
Live streams
STREAM SELECT pushes pose and health deltas to fleet dashboards as they commit.
Real SQL
Representative queries
SELECT unit_id, lat, lonFROM fleet_stateWHERE distance_m > max_range_m;Every statement follows the engine’s own test SQL shapes. See the SQL reference for full syntax.
Capabilities
What you get
Line-rate ingest
Lock-free shard-owned write paths.
Geospatial in SQL
geo_distance, geohash, and H3 cell functions.
O(1) fleet state
Latest pose and health per unit, instantly.
Edge to cloud
One 154MB image runs on-vehicle or in the datacenter.
Proof
Measured on the vetted benchmark lane
durable pose/sensor ingest, single core
1M-row batches, best durable mode
vetted table
View benchmark98.3nscurrent-pose point consult
warm postings
vetted table
View benchmarkcontainer image, edge-ready
geospatial functions built in
image
Measured on AMD EPYC 9554P 64-Core Processor (64t), 1505GB RAM, 6x NVMe — measured on server-class hardware. Release build, median of 5 (re-captured stragglers: median of 3), commit-pinned (7945ae33, 2026-07-09). Ingest figures are engine-side. See the full benchmark suite.
Learn more