Build it once. Ship it across every Cyberwave fleet.
Robots, sensors, AMRs, drones, edge appliances, private‑5G modules — list once in the catalog and become reachable inside every customer's environment, simulation, and workflow.
The catalog is the contract. Your hardware is the product.
Single integration, every customer
Implement the Cyberwave SDK once. Your hardware shows up alongside arms, AMRs, drones, and sensors from every other vendor — no per-customer engineering.
- Open URDF / asset schema, no proprietary formats
- Drivers in Python via the `cyberwave` SDK; Greengrass / Jetson / IoT Edge supported
- Capabilities are tags — they light up the right workflow nodes automatically
Distribution starts in simulation
A digital twin in our catalog lets prospects evaluate your hardware in a working simulation before they sign a PO. The first impression of your product is no longer a sales call — it is a working twin a developer can drive.
- Same code in sim and on real hardware — software-in-the-loop is the buyer's first touch
- Catalog entries link to specs, drivers, supported capabilities, and reference programs
- Buyers compare your robot side-by-side with peers, on identical workflows
Mixed-fleet ready by design
Customers do not pick favorites. Cyberwave coordinates your hardware alongside other vendors' fleets — which means buyers can choose the best tool for each job without facing the dreaded "vendor lock-in" objection.
- Universal hardware abstraction: arms, AMRs, drones, sensors, edge devices
- Workflows orchestrate cross-vendor missions out of the box
- Telemetry and observability are normalized across OEMs
What integration looks like
Most robotics platforms force you to integrate per-vendor. We treat your hardware as a software-defined device — write the driver once, ship to every customer.
Define the asset
Bring a URDF (or our asset schema). We render the digital twin and validate kinematics inside the catalog.
Implement drivers via the SDK
Use the open-source `cyberwave` Python SDK to expose telemetry, commands, and capabilities. ROS / MCAP friendly.
Tag capabilities
Declare what your hardware can actually do (e.g. `capability:point_grounding`, `attr:rugged`). Cyberwave's planner picks it up automatically.
Ship a runtime image (optional)
Bundle your runtime as a Greengrass component or Jetson container. We orchestrate it across customer fleets and OTA-update it.
Why hardware vendors choose us
Real partnerships, real proof — not marketing slides.
Apeiroon, our private-5G catalog partner, won the European RESTART AI for Networks challenge running a Unitree Go2 orchestrated by Cyberwave over their 5G modules.
Vendors integrate once via the SDK; capabilities and UIs propagate through our backend and frontend without custom work per model.
Open formats. Real interfaces. No proprietary hostages — your customers' assets, data, and logs stay theirs.
Featured catalog partners
Hardware companies extending the Cyberwave catalog with purpose-built robots, sensors, and connectivity modules.