dockxo is 1.0. The panel has run real workloads for weeks: load balancers in front of hundreds of domains, MariaDB clusters with a MaxScale router, caches holding a hundred gigabytes of images. The releases since then bring it to the places you already are.
Ask Claude about your servers (1.2)
dockxo is now an MCP server. Add https://panel.dockxo.com/mcp as a custom connector in Claude, or run claude mcp add --transport http dockxo https://panel.dockxo.com/mcp in Claude Code, and dockxo opens a page where you choose what Claude may do: read only, read and deploy, or full access. No token to copy.
Then ask. “Why does api.shop return 503?” Claude reads the service, its health checks, the last few hundred log lines, the recent deployments and the server’s load, and answers with the evidence. “Which certificates expire this month?” “Deploy the api, wait, and tell me if it is healthy.”
34 tools cover the account; the ones that change something are marked, so Claude asks first. Nothing that deletes a service, project, volume or server is offered, a connected app never touches your sign-in or tokens, secrets are masked in every answer, and every change lands in the activity log as MCP (Claude): …. API tokens for scripts got the same three scopes. More on Claude & MCP.
An app with push alerts (1.1)
dockxo installs from the browser on iPhone, Android and desktop, with its own window, icon and shortcuts. Turn notifications on for each device and they become one more alert channel next to Telegram and email: a monitor going down arrives as an urgent notification, and a tap opens the page it is about. Notifications are encrypted for each device with your panel’s own key, so the push services only carry them. App & push notifications.
Passkeys and SSH keys (0.24, 1.0)
Sign in with Face ID, Touch ID, Windows Hello or a password manager, or sign a one-line message with your SSH key (ssh-keygen -Y sign). With either one added, turn password sign-in off: a phished password then opens nothing. Security emails now show the visitor’s real address even behind Cloudflare. Security & API.
Everything you expose, in one place (0.20, 0.21)
The Security page lists every port your servers accept from the internet, including the ones dockxo did not open: a container started by hand, a program installed on the server. Settings → SSL lists every certificate with its expiry and, when one could not be issued, Let’s Encrypt’s own reason; a check from outside shows what visitors actually get and where each domain’s DNS points. Each domain now gets its own certificate, so one broken domain never holds back the rest. Open ports & certificates.
And the rest
- Redeploys skip the build when the source did not change: a new env value takes seconds.
- NVIDIA GPUs for any service, with the server telling you what is missing to use them.
- ClickHouse, a WireGuard VPN and a SOCKS5 proxy among the ready-made services, with strong generated passwords.
- Redirect presets: www to without www and back, and trailing slashes, in one click.
- Several Cloudflare accounts: one token each, the right one picked per domain, optionally through a SOCKS5 proxy.
Every change is in the changelog. Everything is still free and unlimited during the beta.