Support

When something is wrong with CMDOP, this page is the front door. The right channel and the right diagnostic bundle save hours.

Support channels by plan

Plan	Channel	SLA
Personal	Community forum and email	Best effort
Team Starter	Email + cabinet ticket	1 business day
Team Scale	Priority chat + email	4 hours
Enterprise	Dedicated SRE, Slack Connect, phone	1 hour or per contract

Opening a ticket

The “New ticket” form pre-fills:

Machine UUID (if you click in from machines).
Agent version reported by the daemon.
Recent error from the local audit log.
Workspace and account identifiers.

Attach screenshots and log excerpts. Tickets reach the engineering team via the Django support app and are tracked end-to-end.

Diagnostic bundle

For agent / daemon issues, run:


cmdop doctor --bundle

The bundle includes:

Daemon logs (last 7 days, rotated).
daemon.status JSON.
permissions.yaml (sanitized — no bypass_token).
OS, kernel, agent version, build hash.
Network reachability checks against the relay.

Attach the resulting cmdop-bundle-<timestamp>.tgz to the ticket. CMDOP staff will not ask for unsanitized credentials.

Status page

Public status page covers regional uptime, ongoing incidents, and post-mortems. Subscribe via:

Email — incident-only or all updates.
RSS — https://status.cmdop.com/feed.rss.
Webhook — push to your incident management tool.

Link to the status page lives at the top of the support page.

Security disclosure

For security issues, do not open a regular ticket. Use the coordinated disclosure address listed on the support page (with a GPG public key for sensitive reports). Acknowledgement within 24 hours; standard 90-day disclosure window.

Where this data lives

Backed by apps/my/.../private/support/ and the Django support app.

Profile
Audit log — find request IDs to attach to tickets.
Troubleshooting