How It Works
Every hardware connection follows the same pattern:- Add a digital twin from the catalog (or create a custom one)
- Install the Cyberwave edge stack on a device connected to your hardware
- Pair — the driver is installed automatically and your hardware starts syncing in real time
Featured Hardware
These platforms have dedicated setup guides with step-by-step instructions.SO101 Robot Arms
Open-source 6-DOF manipulator arms for desk-based manipulation, teleoperation, and imitation learning.
UGV Beast Rover
Off-road tracked rover with a Raspberry Pi + ESP32 dual-controller architecture and ROS 2 stack.
Unitree Go2
Intelligent quadruped with 4D LiDAR, AI-powered locomotion, and autonomous navigation.
Universal Robot UR7e
Industrial collaborative arm connected via a Raspberry Pi running ROS 2 and an MQTT bridge.
Boston Dynamics Spot
Quadruped robot for inspection, patrol, and autonomous missions.
Camera
USB webcams and laptop cameras for live streaming, vision workflows, and dataset recording.
Full ROS Compatibility
Cyberwave is fully compatible with ROS 1 and ROS 2. The open-source cyberwave-os GitHub organization provides SDKs and reference implementations for bridging ROS topics with Cyberwave’s MQTT-based digital twin layer. A typical ROS integration uses the MQTT bridge pattern: a lightweight node subscribes to ROS topics (joint states, odometry, camera feeds) and publishes them to the Cyberwave MQTT broker. Commands flow in the opposite direction — from the dashboard or API, through MQTT, and into ROS action servers or publishers.Custom Integrations
Integrate with ROS, VDA5050, OPC UA, Modbus, and other industrial protocols
Industrial Protocol Support
Cyberwave’s driver architecture is not limited to ROS. The same pattern works with any protocol your hardware speaks:| Protocol | Use Case |
|---|---|
| ROS 1 / ROS 2 | Robot arms, mobile robots, sensor stacks |
| VDA5050 | AGV and AMR fleet communication |
| OPC UA | Industrial automation and PLC connectivity |
| Modbus TCP/RTU | Sensor and actuator networks |
| gRPC / REST | Custom services and microservice architectures |
| Serial / USB | Direct device control (servos, microcontrollers) |
Extend Cyberwave with Custom Drivers
If your hardware isn’t in the catalog, you can write a compatible driver and connect it in minutes. A driver is a Docker container that translates between your device’s native API and Cyberwave’s MQTT interface.Writing Compatible Drivers
Full guide on driver architecture, environment variables, and packaging
Driver Overview
How drivers are registered and managed by Edge Core
Python SDK
Build drivers and applications with the Cyberwave Python SDK
C++ SDK
High-performance SDK for embedded and latency-sensitive drivers
Reference Implementations
These open-source drivers are good starting points:| Driver | Repository |
|---|---|
| Camera | cyberwave-os/cyberwave-edge-camera-driver |
| SO-101 arm | cyberwave-os/cyberwave-edge-so101 |
What You Can Do Once Connected
Regardless of which hardware you connect, every digital twin on Cyberwave gives you access to the same platform capabilities:- Real-time teleoperation — control your hardware from the dashboard, SDK, or API
- Live telemetry streaming — monitor sensor data, joint states, camera feeds, and more
- Dataset recording — capture episodic datasets for training and evaluation
- ML model training and deployment — train models on recorded data and deploy them as autonomous controller policies
- Simulation — test in a browser-based 3D environment before deploying to physical hardware
- Workflows and automation — chain actions, models, and logic into repeatable workflows
Browse the Catalog
Hardware Catalog
Browse all 80+ supported devices and add them to your environment