Skip to content
Getting started Install the MZPanel agent on a VPS and connect your first server to the dashboard.

Getting started

MZPanel manages many WordPress VPS from a single web dashboard. You install a lightweight agent on each VPS; the agent dials back to the control plane over an outbound WebSocket — no open ports, no domain required on the VPS. Getting online takes three steps.

Sign up at app.mzpanel.com. The Free plan lets you connect 1 VPS; higher tiers raise the quota (see Tiers & quotas).

In the dashboard open Add server, keep the default Run a command method, then Generate install command. You get a one-liner carrying a one-time token:

Terminal window
curl -fsSL https://get.mzpanel.com | sudo INSTALL_TOKEN=<token> bash

SSH into your fresh Ubuntu 24.04 box and paste it. The install token is valid for 1 hour; the moment the agent registers it swaps the token for a long-lived agent token, so the one-time value is never reused.

Your server appears online within seconds and provisions its base LEMP stack in the background. From here you can create WordPress (or static / PHP / Node / Python / Go) sites, run backups, issue SSL, switch PHP versions, and monitor the box — all from the dashboard.

MZPanel is dashboard-driven. You click in app.mzpanel.com; the action is sent to the agent over its WebSocket; the agent runs it natively on the VPS and streams the result back in realtime. Your server opens no inbound ports and needs nothing installed beyond the agent. See Architecture and The agent.

  • The token expires in an hour. If the one-liner sits unused, generate a fresh one from Add server — an expired token is refused at registration.
  • Outbound HTTPS must be open. The agent needs to reach the control plane on 443 outbound; inbound firewall rules don’t matter, but a box that can’t make outbound TLS connections will never come online.
  • Ubuntu 24.04 only. The installer and the mz engine target Ubuntu 24.04 LTS; other distros aren’t supported yet.
  • Dashboard tour — how the sidebar, servers, and per-site shell fit together.
  • Prefer the terminal? Everything the dashboard does maps to the on-box mz CLI, so you can drive the same engine over SSH.