Dashboard tour

Once your first server is online, everything happens in the dashboard at app.mzpanel.com. This page is a map of that dashboard: the sidebar, the two “shells” you drill into, and how URLs are structured — so you always know where you are and where a feature lives. It’s the fastest way to get oriented before reading the per-page guides.

The sidebar

The left sidebar has two groups.

MZPanel — your fleet, across every server:

• Servers — your VPS fleet as cards with live CPU / RAM / disk. Add a server here.
• Sites — every website across all servers in one list, plus a Domain Manager tab.
• Apps — Docker containers and Compose stacks, rolled up fleet-wide.
• Backups — the backup control tower: destinations, jobs, snapshots, restore.
• Uptime — external HTTP / TCP / ping checks and incidents.
• ClaudeCode — run live Claude Code coding sessions on one of your VPS.
• Marketplace — install server extensions and one-click Docker apps.

Account — your workspace:

• Team — members, roles, invitations and the activity log.
• Billing — plan, quota usage, wallet, invoices and add-ons.
• Advanced — an umbrella hub for integrations and less-frequent settings (see below).

Two more entry points live in the top bar, not the sidebar: the Ask AI button (the unified Assistant, where support also lives) and the notifications bell. A Terminal dock sits at the bottom of the screen and expands to a full-screen shell.

The Advanced hub

Advanced (/advanced) is a hub with its own left rail, grouping the things you set up once and revisit rarely:

• Integrations — Git providers, DNS providers, Chat & Alerts channels.
• Infrastructure — Load balancers, Private network (WireGuard), Server templates.
• Developer & tools — Developer (API keys / webhooks), Tools (fleet one-shots), Terminal.
• Account — Settings (profile, email, sessions), Roadmap.

Two nested shells

Most of MZPanel’s depth is inside two “shells” — full management workspaces you drill into from a list.

The server shell — /servers/:id/*

Open any server and you get a persistent three-column layout: a grouped side menu, the active section, and an info panel. The side menu groups the sections:

• Main — Sites, Apps (Docker), Databases
• Web — PHP, DNS & TLS, Mail, Cron jobs
• Tools — Users & SFTP, File Manager
• System (collapsible) — Services, Monitoring, Storage, OS updates, Security, Extensions
• Settings

Each section is a complete management surface: tables with hover-reveal row actions, drawers for create/edit, and live streaming of the agent’s output while a job runs.

The site shell — /sites/:srv/:dom/*

Open a WordPress site and you get a wp-admin-style rail. Its groups:

• Overview — a health cockpit for the site.
• Content — Posts, Pages, Categories, Tags, Media, Menus, SEO, Redirects, Settings.
• Manage — Plugins, Themes, Users.
• Performance — Cache, Optimize.
• AI — AI Studio (in progress).
• Store — Orders, Products, Customers, Coupons, Reports (shown only when the site runs WooCommerce).

MZPanel manages the site through the agent, so you edit content and settings here without logging into wp-admin.

URL structure at a glance

MZPanel URLs are predictable, which makes them easy to bookmark and share:

Pattern	Scope	Example
/<page>	Account-level page	/servers, /sites, /backups
/servers/:id/<section>	A section of one server	/servers/:id/cron
/sites/:srv/:dom/<section>	A section of one WordPress site	/sites/:srv/:dom/plugins
/advanced + sub-routes	The Advanced hub	/connect/git, /load-balancers

For the complete list of routes mapped to features, see the URL map.

How it all works

Every action you take in the dashboard is sent to that server’s agent over its WebSocket link. The agent runs the operation natively on the VPS and streams the result back in realtime — there are no open ports on your server and nothing to install beyond the agent. The control plane stores your account, server metadata and audit log; the live truth of each box is read through its agent. See Architecture and The agent.