Console
Provisioning, fleet health, firmware and endpoint configuration in one place. The console arrives with the v3 shipment — the integration documentation is already published, and this page explains how your devices reach you in the meantime.
Sign-in is not open yet
We are not taking console registrations before the hardware ships, because an account with no device attached to it does nothing useful. If you have an order in flight, the provisioning card in the box is what connects you. There is nothing to set up in advance.
You do not need an account to build on the hardware. The full integration documentation — wire protocols, the minimum server, provisioning, firmware and worked code — is published and open, so you can read the entire contract before you buy a single unit.
Documentation
The console handles provisioning and fleet health. Everything the device does on the wire — and everything your own backend has to answer — is documented in full, in public.
Developer documentation17 pages covering all three devices: the udp-v1 push-to-talk wire format, the framed-PCM walkie, the full-duplex agent socket, the print bridge, the fleet plane, firmware and OTA — with copy-paste code for every one.Read the docsWhat happens after you order
- 01
Your order is confirmed
You get an order reference by email straight away. Devices are built and shipped within 10 days.
- 02
Provisioning arrives with the hardware
Every device ships with a QR provisioning card in the box. Scanning it binds the device to your account. The card is the credential, so keep it with the unit.
- 03
The device joins your network
Wi-Fi details are set during provisioning. From that point the device is reachable for firmware updates and remote commands.
- 04
You choose where the audio goes
Set the stream endpoint to your own backend from the console and the device feeds the voice AI you already run. Guided use-case setup in three easy steps arrives once the console is finalised.