The relaybuilt into the binary
The relay your fleet runs on — built into the same signed binary as the agent. Outbound-only, multi-tenant, isolated per customer.
One binary is the backbone
The relay your fleet runs on — built into the same signed binary as the agent. Outbound-only, multi-tenant, isolated per customer.
See the relayfrom the inside
Every screenshot below is the real Server panel of the cmdop web console — the operator surface the relay serves itself.
Agents dial out.No inbound ports.
The relay your fleet runs on — built into the same signed binary as the agent. Outbound-only, multi-tenant, isolated per customer.
Isolatedper customer
Every account gets its own relay domain, provisioned just for your fleet — TLS termination and routing that no other customer shares. Presence, audit and history stay within your fleet; nothing is routed across tenant boundaries.
A coordinatorthat lives in the relay
The server agent is an AI coordinator that joins the relay as a virtual peer — the "server" contact in your chats. Fleet-scoped and always on, it can reach the other agents — ask one, broadcast to many — and coordinate work across the fleet without anything running on your own box.
Your fleet,in your messenger
The relay bridges conversations to Telegram, Slack and Discord bots. Pair a chat once and the same agents answer there — deploy from your phone, get incident pings in the channel your team already reads.
Run the relay yourself
The relay is not a separate service to deploy — it is the same signed binary you install everywhere. Install cmdop, run `cmdop server`, and point your machines at it. One command brings up the relay, the web console and the coordinator together.
The relay your fleet runs on — built into the same signed binary as the agent. Outbound-only, multi-tenant, isolated per customer.
Run the fleetbackbone yourself
Spin up the relay, point your agents at it, and own the whole plane end to end.



