This page is a quick reference for the vocabulary used throughout Cyberwave. For deeper explanations, follow the links to the relevant feature pages.Documentation Index
Fetch the complete documentation index at: https://docs.cyberwave.com/llms.txt
Use this file to discover all available pages before exploring further.
API Token
Cyberwave uses API tokens to authenticate requests for the Python SDK, REST API calls, and MQTT connections. Each token is scoped to a specific workspace. See Authentication for setup.Asset / Asset Catalog
The Asset Catalog is Cyberwave’s library of pre-configured robot assets. Each asset includes a unique registry ID (e.g.the-robot-studio/so101), a URDF describing joints and links, a 3D model, and metadata about capabilities. Asset types include robot arms, mobile robots, quadrupeds, and drones. See Catalog.
Controller Policy
A controller policy determines how a robot acts. Cyberwave supports manual control (dashboard or SDK), teleoperation (leader → follower), remote operation (dashboard → follower only), and AI models (trained policies that execute autonomously).Dataset
A dataset is a collection of recorded robot operations used for training ML models. Each dataset contains multiple episodes with joint positions, camera feeds, and timing data.Digital Twin
A digital twin is a virtual replica of a physical robot that mirrors its behavior, capabilities, and state in real time. It includes an accurate 3D model, physics simulation, virtual sensors matching the physical setup, and bidirectional sync with the physical robot. See Digital Twins.Driver
A driver is a Docker container that translates between a piece of hardware’s native interface (serial, USB, ROS, gRPC, Modbus, etc.) and Cyberwave’s MQTT layer. Drivers are managed by the Edge Core and can be installed from the catalog or written custom. See Drivers Overview.Edge Core
The Edge Core is the central host-level service of the Cyberwave edge runtime. It handles identity, authentication, device registration, driver orchestration, and coordination with Cyberwave Cloud over MQTT. See Edge Overview.Edge Node
An edge node is a physical compute unit deployed at the periphery of the platform (industrial PC, embedded computer, Raspberry Pi, Jetson) — typically co-located with one or more robots. Edge nodes run under strict latency, bandwidth, and reliability constraints and are designed to operate even under degraded connectivity.Edge Worker
An Edge Worker is a containerised module — usually an ML model or data pipeline — that runs alongside the Edge Core for low-latency, on-device inference. Frames and telemetry never have to leave the device. See Edge Workers.Environment
An environment is a 3D space where your digital twins exist and interact. It can represent a physical facility (warehouse, lab, outdoor site), a testing scenario, or a pure simulation environment. Environments support Edit Mode (designing and configuring) and Live Mode (real-time operation and monitoring). See Environment Editor.Episode
An episode is a single recording of a robot completing a task from start to finish. Record 10–15 demonstrations of the same task with slight variations for better model generalisation.ML Model
ML Models are AI models registered in your workspace that process inputs (video, images, audio, text, robot actions) and integrate with workflows. Cyberwave provides the full pipeline: collect data → create datasets → train → deploy as a controller policy → execute autonomously. See ML Models.Operator Alerts
Cyberwave can raise alerts when a robot is missing required calibration, or when a controller is attached, removed, or swapped, so operators complete setup in the right order. The UI may disable actions while these conditions apply, to reduce the risk of unsafe behaviour. See Driver Alerts.Organization
The organization is the top-level account that owns all workspaces, environments, and resources for your company or team.Remote Operation
Remote operation controls a follower arm directly from the Cyberwave dashboard — no leader arm required. Useful for testing, calibration, and manual joint control without a physical leader. See Live Teleoperation.Teleoperation
Teleoperation uses a physical leader arm (or other input device) to control a follower in real time. Ideal for collecting demonstration data for training. See Live Teleoperation.Workflow
Workflows are automated sequences of robot operations built through visual orchestration. Connect nodes to compose complex behaviours without writing procedural code. Workflows can be triggered manually, on a schedule, by events, by webhook, or by camera frames (on the edge). See Workflows.Workspace
A workspace is your team’s container for environments, workflows, and resources. It provides centralised authentication, team collaboration, permissions, resource sharing across environments, and billing.Related Reference
Architecture
How the cloud, edge, and hardware layers fit together.
Data Model
Organization → Workspace → Environment hierarchy.