OpenVibe.Bot

OpenVibe.Bot is "The open control panel for robots" at openvibe.bot on port 4630. It pairs a robot's machines, keeps their state and gates every operator command: a device opens one outbound WebSocket to /device, and a person drives it from /control or the REST API through the same gate of roles, per-robot limits, cooldowns and the turn budget.

What it does

Bot owns robots, their profiles, per-robot limits, allow lists, roles and operators; the curated kit catalogue; devices and their hashed credentials; pairing codes; the /device and /control WebSockets, the command gate and the latched e-stop; and a command audit kept 30 days. A sim.rover robot is driven by an in-process simulator so the panel works before hardware exists, and server-side ONVIF cameras attach in-process. The panel renders from the robot's profile, with a touch joystick, keyboard and gamepad, a latency meter and one camera tile per camera. Owner-only streaming and recording toggles record live sessions to OpenVibe.Media or mirror them to the owner's OpenVibe.Live channel.

What it does not do yet

Bot does not own identity, which is OpenVibe.Network's, or video: a device publishes over WHIP to OpenRestream. When OpenVibe.Billing is unset, job usage readings wait in run_usage_outbox rather than being dropped.

How it fits the network

Bot depends on OpenVibe.Network for user and service tokens, node tokens and identity resolution, OpenRestream for the WHIP ingest base devices publish to, and OpenVibe.Billing for job usage readings. A device's installer command points at the released OpenVibe.Node script.

Status

Production runs the Node process under systemd as openvibe-bot.service on port 4630 behind nginx, which terminates TLS and upgrades the WebSockets. PostgreSQL applies migrations/ at boot; Valkey is optional for shared per-actor limit counters. STATUS.json records stage alpha and the service deployed.