cmdop-server 0.0.3

Run your own CMDOP relay — the self-hostable hub your machines and AI agents connect through.

cmdop-server

Your own CMDOP relay, in your own network. The hub your machines dial into to become reachable from anywhere — run commands, edit files, stream a live AI agent, open tunnels — without opening a single inbound port. Self-host it instead of relying on the public cloud, and keep your fleet and its data where you want them.

pip install cmdop-server

📚 docs.cmdop.com — install, configure, and run. Server · Connect · Bots · SDK

What you get

🛰️ Reachable, anywhere	Machines dial out over gRPC — NAT- and firewall-friendly, no inbound ports.
💻 Full remote control	Terminal, remote exec, file ops, and tunnels across your whole fleet.
🤖 Built-in AI	Jarvis lives in the server and can drive your machines on its own.
🔒 Yours to host	Your network, your Postgres — on-prem or air-gapped. Fleets isolated by row-level security.
📦 One dependency	A single pure-Python package. Upgrade the whole engine by bumping one version.

How it works

Machines run the CMDOP agent and connect out to your server. Your apps, dashboard, and the SDK reach the same server over REST + WebSocket. The server ties the fleet together and hosts the AI.

   your machines ──gRPC(out)──▶  cmdop-server  ◀──REST/WS──  your apps · SDK · dashboard
   (anywhere, NAT-ok)              (you host)                 + Jarvis, the built-in AI

Make it yours

cmdop-server is the part that doesn't change — install it and keep your deployment thin. You add only what's yours:

• config — a few YAML / env values
• migrations — your database schema on top of the baseline
• your AI — Jarvis prompts and tools, tuned to your fleet
• your bots — Telegram, Discord, Slack
• extensions — your own routes and services

Links

• Docs → docs.cmdop.com
• Product → cmdop.com/server · Connect · Bots · SDK
• Source → github.com/commandoperator/cmdop-server
• CMDOP

License

Apache-2.0.