Fleet backbone

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.

Architecture

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.

The Server panel

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.

The relay at a glance

Online and ready: the advertised address machines connect to, uptime, mode and engine control — served by the binary itself.

cmdop server overview — the relay running, its advertised address, uptime and engine control
cmdop server overview — the relay running, its advertised address, uptime and engine control

Every machine, dialing in

Presence and heartbeats for every connected machine — who is online, who went stale, and when each was last seen.

cmdop server connections — every machine dialing in, with presence and heartbeats
cmdop server connections — every machine dialing in, with presence and heartbeats

Telegram, Slack and Discord

Bridge conversations to messenger bots: pair a chat once and the same agents answer there — with paired users, chats and message counts in view.

cmdop server bots — the Telegram bridge connected, with paired users, chats and message counts; Slack and Discord alongside
cmdop server bots — the Telegram bridge connected, with paired users, chats and message counts; Slack and Discord alongside

The relay, narrating itself

The live log stream of the relay process — connections, sessions and bridge activity as they happen.

cmdop server logs — the relay's live log stream
cmdop server logs — the relay's live log stream
Connectivity

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.

Multi-tenancy

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.

Server agent

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.

Bots

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

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.

Loading code...

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.