Deployment

Deploying Cmdop means installing one binary on each machine you want to operate; there is no database, cache, or relay service to stand up beside it. That binary carries both the agent and an embedded relay, so a single machine is already a complete deployment. Running your own relay is an optional second step for several machines under one address you control.

TL;DR

Cmdop ships as one cross-platform cmdop binary. Installing it on a machine gives you the agent and an embedded relay. If you want machines to join a relay you control, run cmdop server create on one host and join the rest to it.

Install on the machine you want to operate

For most people this is the whole story. The binary is the deployment unit — there is no separate relay service, database, or cache to stand up.

See Install Cmdop, then Quickstart.

Run your own relay

Run one when you want several machines under one relay you control, or when you want to reach a machine from outside its network. One host creates and runs the relay; the others join it with a fleet join key.


cmdop server create --mode lan --no-prompt
cmdop server --detach
cmdop server status

--mode picks reachability: lan, public (a cmdop.dev subdomain through Cmdop’s managed reverse tunnel), or own_domain (your FQDN with ACME TLS).

The full walkthrough — reachability, joining machines, multi-relay setups, attachment storage — is Self-hosted relay.

Run it in a container

Docker is optional, not a second deployment model — but there is an official Compose project for people who want one. cmdop-docker packages a relay, a scoped agent, and an editable project into a single container, and the same image can instead join a relay you already run as one more machine. It is live at demo.cmdop.com .

See Docker.

What Cmdop operates

Account, plan, and marketplace services run as Cmdop-operated infrastructure. The public reachability mode also uses a Cmdop-operated edge. You do not deploy either; you choose whether to use them.

What should I read next?

Install Cmdop

Get the binary onto a machine.

Self-hosted relay

Run a relay and join machines to it.

Docker

The containerized workspace, and running an agent in a container.

Relay operation issues

When the relay does not come up.

Pricing

Machine and relay-address entitlements.

Common questions

What do I need to deploy Cmdop?

Install the cmdop binary on each machine you want to operate. That binary is the agent and also contains the embedded relay. Run your own relay only when you want several machines under one relay address you control.

Does Cmdop need Docker Compose, Redis, or a database?

No. The product deployment unit is one binary. There is no Compose stack, database, cache, or separate relay service required for the normal deployment path. A Compose project exists as a convenience — a ready-made containerized workspace — but nothing requires it. See Docker.

When should I run my own relay?

Run your own relay when you want a controlled fleet boundary, a private LAN relay, a public relay address, or your own domain. Otherwise install Cmdop on a machine and use the default local path.