Onboarding and device identity
A device claims itself with a single-use token and receives its own certificate. Every connection uses mutual TLS, certificates renew automatically, and a decommissioned device is refused at once.
In development
One platform for the robots and devices at the edge.
MeshLogiq onboards, monitors, controls and updates robots and IoT devices — microcontrollers, edge computers, ROS 2 ground robots and PX4 drones — from one self-hosted server, with a secure identity for every device.
By design
443
The one port a device needs, outbound
0
Inbound ports on a device
Mutual TLS
A certificate for every device
1
Operator in control of a robot at a time
Built for mixed fleets
ESP32 & STM32
Jetson, Raspberry Pi & Orange Pi
ROS 2 ground robots
PX4 drones
The platform
Everything a connected fleet needs, in one place
MeshLogiq is in development. This is the system we are building, from a device's first connection to the software it runs years later.
Digital twins
Each device has a desired and a reported state. Write what a device should be doing; it converges and reports back, and picks up the latest state after being offline.
Telemetry and events
Metrics and events over MQTT 5, buffered on the device through outages and backfilled afterwards, charted live in the console.
Live video and remote driving
Low-latency video from a robot to an operator over WebRTC, with gamepad control, an operator lock and a watchdog on the robot.
Missions
Waypoint missions are authored on the server and run entirely on the robot or its autopilot, so a mission continues through a lost link and can be paused, resumed or taken over.
Fleet map
Live positions, status and tracks on a map built on open map data, with indoor robots shown on their own floor map.
Staged software and model updates
Containers, AI models and firmware roll out in stages: a canary group first, then waves, with health checks and rollback.
Alerts, recordings and diagnostics
Rules on telemetry raise alerts. Robots keep a rolling recording that can be uploaded on demand, and logs and a time-boxed remote shell avoid site visits.
Users, roles and audit
One organization per installation, with users, roles and permissions scoped to sites, groups and devices, and an audit log of every command and change.
Devices
One protocol, from a microcontroller to a drone
Anything that speaks the device protocol is a device, so very different machines are managed the same way.
Edge computers
NVIDIA Jetson, Raspberry Pi and Orange Pi. One small agent, a single static program, runs outside the robot software and keeps working when that software crashes.
Microcontrollers
ESP32 and STM32 on Wi-Fi, Ethernet or cellular connect directly with a small C library that speaks the same protocol as the edge agent.
ROS 2 ground robots
A bridge container on the robot maps chosen ROS 2 topics to telemetry and carries drive commands and missions. Robot middleware never leaves the vehicle.
PX4 drones
A companion computer links the autopilot to the platform. Missions fly in PX4 itself, and its own failsafes handle a lost link, low battery and geofences.
How it works
The robot owns its own safety. The server never drives.
Losing the network must never leave a machine uncontrolled, and a device should need nothing from its network but one outbound connection.
Outbound only
Devices open every connection themselves, on port 443. No inbound ports, so they work behind NAT, firewalls and cellular networks.
The robot owns its safety
Nothing on the server sits in a control loop. Watchdogs, speed limits and the operator lock live on the vehicle, which stops on its own when the link or the operator goes away.
AI stays at the edge
The server needs no GPU. Inference runs on the edge computer on the robot, next to the camera, and models are deployed to it like any other update.
Secure by default
Security at every layer
Identity and encrypted transport come first, before any feature that moves a machine.
Keycloak identity
Users sign in through Keycloak, with roles and permissions for each site, group and device.
TLS via Traefik
Every public endpoint is encrypted, with automated certificates and a single open port.
Least privilege
Each device holds its own short-lived certificate and can reach only its own data. High-risk commands are signed, and updates install only when signed by your release key.
Tell us about your fleet
MeshLogiq is in development. If you run robots or connected devices and want to follow along or try it early, tell us what you run.