If you run more than a handful of Plesk servers, logging into each one to check a license renewal date or a disk-space alert doesn't scale. Plesk 360 (platform360.io) is Plesk's hosted dashboard for exactly that problem: one place to see every server you manage, renew or upgrade licenses without hunting through email receipts, and get paged when a site or server goes down. It's separate from the older Plesk Multi Server extension, which does something different — active load balancing and failover across a cluster — and the two get confused constantly on the Plesk forums.
This is for hosts and agencies managing 3+ Plesk servers who are tired of bookmarking each panel's login page separately.
Plesk 360 vs Plesk Multi Server: pick the right tool
These solve different problems and you can run both:
- Plesk 360 is an oversight layer. It doesn't touch your hosting stack — it just talks to each server's API to pull license, health, and monitoring data into one screen. No architectural changes to your servers required.
- Plesk Multi Server is an actual cluster topology: a management node plus service nodes, with configuration sync, load balancing, and failover between nodes. It changes how traffic is routed and requires two license keys per node (a Plesk license plus the Multi Server extension license).
If you just want a single dashboard across independently-run client or reseller servers, you want 360. If you're building an HA web-hosting cluster, you want Multi Server. Most hosting businesses only need the former.
Create a 360 account and add your first server
- Go to platform360.io and sign up with the email address you use for your Plesk licenses — this is the account 360 will look for existing licenses under.
- From the dashboard, click the + button in Server Inventory.
- Enter the server's hostname and the Plesk panel port, e.g.
server1.example.com:8443. - Plesk 360 redirects you to that server's own Plesk login screen. Log in once and click Confirm to authorize the connection.
- 360 generates a server-scoped API token behind the scenes — it does not store your panel password, and future requests from 360 to that server use the token, not credentials.
Repeat for each server. There's no practical limit on how many servers you can add to Server Inventory itself — the limits only apply to the paid monitoring tiers, covered below.
Adding servers by CLI or API
If you're scripting server provisioning (e.g. spinning up a new Plesk box from an image and want it registered in 360 automatically), generate a personal API token first: click your email in the top-right corner → API tokens → name it → Generate. Use that token to authenticate 360 API calls instead of a login/password pair, and script the add-server call as part of your provisioning pipeline. This is the same pattern cPanel admins will recognize from WHM API tokens — a scoped, revocable credential instead of a shared login.
Manage licenses from one screen
The Licenses tab lists every license tied to your account: type, activation code, subscription cost, status, and next billing date. From there you can:
- Renew a license before it lapses
- Upgrade or downgrade the underlying product (e.g. Web Host → Web Pro) where supported — this opens a sidebar showing the price delta
- Add extensions to a license (WordPress Toolkit tiers, Advanced Backup, etc.) with per-month or per-year pricing shown up front
- View full details — creation date, activation code, billing history, which server it's bound to, and installed panel version
If you've bought licenses from panellicense across multiple email addresses — common when a reseller account was set up before a company standardized on one billing inbox — use Bind existing licenses to pull licenses purchased under a different email into your main 360 account, or add that address under Linked Emails to manage them centrally without merging accounts. Note that 360 doesn't surface partner-purchased licenses, perpetual licenses, or licenses tied purely to feature extensions rather than the base product — those you'll still confirm via the license status check on the server itself.
Add 360 Monitoring for uptime and resource alerts
Monitoring is a separate opt-in layer with its own pricing, since it runs a lightweight agent per server rather than just reading API state:
| Tier | Price | Servers | Sites | Check interval | Alerting |
|---|---|---|---|---|---|
| Lite | Free | 1 | 5 | 10 min | Email only |
| Pro | $4.99/mo | 1 | 20 | 60 sec | Multi-channel, custom metrics |
| Business | $24.99/mo | 10 | 200 | 60 sec | Multi-channel, scheduled site crawls |
| Enterprise | $99.99/mo | 100 | 2,000 | 60 sec | Multi-channel, 5-crawl queue, deepest crawl depth |
Pro tier add-ons run $1.19/month per extra server and $0.19/month per extra site if you're just over the included count. The Lite tier requires no credit card, so there's no reason not to enable it on every server as a baseline — the jump to Pro is really about check-interval granularity (60 seconds vs. 10 minutes) and getting alerts into Slack or PagerDuty instead of just email.
To enable it: 360 → Monitoring → Servers → Add server, which hands you a one-line installer script to run on the target box.
Next steps
- Plesk reseller accounts and plans — if you're deciding between Multi Server clustering and per-client standalone servers
- Plesk license tiers explained — what Web Host vs Web Pro actually unlocks before you upgrade from the 360 Licenses tab
- Check hosting license status from the command line — for licenses 360 doesn't surface (partner-purchased, perpetual)
Buying or renewing Plesk licenses to connect to 360? Compare tiers on /plesk-license or talk to us via /contact for volume pricing across a multi-server fleet.