Plesk license tiers explained: Web Admin, Pro, and Host

Plesk's three editions — Web Admin, Web Pro, and Web Host — look superficially similar to cPanel's tiers, but the unit of count is different. Plesk caps domains, not cPanel-style accounts. A single Plesk subscription can host one domain or thirty; what matters for licensing is the total domain count across all subscriptions on the server.

This article covers what each edition limits, what the Power Pack add-on actually adds, how hyperscaler-bundled licences differ from standalone purchases, and the two edge-case features (reseller management and the Developer Pack) that change which tier you actually need.

The three editions at a glance

A few specifics worth pinning down before you choose:

• Web Admin is the entry tier — 10 domains, single administrator, no resellers, no customer accounts. It's the Plesk equivalent of cPanel Solo plus a handful of extra domains. Useful for an in-house dev box or a single-tenant SaaS where you want Plesk's UI without paying for multi-tenancy.
• Web Pro is the agency tier. 30 domains, unlimited subscriptions, unlimited customer-tier logins, but no reseller hierarchy. If you want to give a customer the ability to onboard their own customers, you need Web Host.
• Web Host is unlimited domains plus the reseller layer. This is what every shared-hosting operator and white-label reseller buys.

The domain count includes addon domains, subdomains, parked domains, and alias domains. On a shared server with 200 customers, you might cross the Web Pro cap with the first 10 customers — domain inflation is faster than account inflation.

What counts as a "domain"

Plesk's licence enforcement is stricter than cPanel's. Every entry in dom in the Plesk database counts, including:

• The primary domain on each subscription
• Subdomains (blog.example.com, shop.example.com)
• Addon domains (a second TLD on the same subscription)
• Aliases (with the exception of one or two recent build numbers where redirect-only aliases are excluded — check plesk version against the Plesk release notes).

System-generated domains do not count: the panel hostname, the auto-generated *.plesk.page preview domains, and the licence server's own check-in domain. Mail-only domains (no web service) do count.

This catches Web Pro customers around the 22-25 domain mark. They have 12 subscriptions but 28 domains because half their customers have one or two subdomains. Plan for 1.5× the subscription count when estimating headroom.

Plus, Premium, and the Power Pack

Layered on top of the three editions are paid add-ons. The ones that matter:

• Power Pack — adds WordPress Toolkit Premium (cloning, staging, smart updates), Plesk Email Security, and a handful of premium modules. On Web Admin and Web Pro, the base edition includes WordPress Toolkit but without the Premium features.
• Developer Pack — adds Git deployment, the staging environment, and the Docker extension. Free with Web Host, paid add-on for Web Pro, not available on Web Admin.
• Premium Antivirus — Plesk Email Security with Dr.Web or Kaspersky scanning. Paid per-server, not per-domain.

For a Web Pro server, the question to ask is whether the Power Pack's WordPress Toolkit Premium pays for itself in time saved on clones and updates. For a server hosting more than 20 WordPress sites, it typically does within the first quarter.

Hyperscaler editions vs standalone

Plesk sells two parallel SKU families:

• Standalone licences — bought from a reseller like us, keyed to a server IP. Works on any infrastructure (bare metal, VPS, on-prem hypervisor, hyperscaler instance).
• Hyperscaler-bundled licences — bought through AWS Marketplace, Azure Marketplace, or DigitalOcean. Billed hourly through the hyperscaler, tied to the running instance.

Pricing differs significantly. Standalone monthly Plesk Web Host on a paid yearly plan typically lands 30-50% below the hyperscaler-bundled hourly equivalent at full utilisation. For a server that runs 24/7, standalone wins. For ephemeral boxes spun up for under a week per month, hyperscaler hourly billing wins.

Worked examples

Boutique agency, 8 client sites with staging

8 production domains, 8 staging subdomains, plus 4 of those clients have a www. alias. That's 20 domains total. Web Pro at 30 has 10 domains of headroom. Choose Web Pro plus the Developer Pack for the staging features. Skip Web Host — you don't need resellers.

White-label reseller, 80 customers

Average customer has 1 primary domain and 1.5 subdomains. 80 customers × 2.5 domains = 200 domains. Add reseller hierarchy because you're white-labelling. Choose Web Host with the Power Pack — the WordPress Toolkit Premium pays for itself on the volume.

Single-tenant SaaS box

One application, one production domain, one staging subdomain, one dashboard subdomain. Three domains total. Web Admin at 10 has plenty of room and costs less than half of Web Pro. Choose Web Admin.

When to upgrade

Upgrade Web Admin → Web Pro when:

• You cross 8 domains (Web Admin's 10-domain cap blocks new subdomain creation; you want the headroom before deploying customer #9).
• You need customer-tier logins (Web Admin doesn't support them; the workaround of giving customers admin access is a security mistake).

Upgrade Web Pro → Web Host when:

• You cross 25 domains and growth is steady — the 30-domain wall arrives faster than intuition suggests.
• You sign a reseller customer. Don't try to fake it with subscription nesting — the reseller hierarchy is the only supported model.

Mid-cycle upgrades are prorated; see how prorated licence billing actually works for the exact math. For the current per-tier monthly rates, check our pricing page. Volume buyers running more than five Plesk servers should contact sales for partner rates.

Next steps

• Pick an edition and activate a Plesk licence, or compare the panel to the alternative in cPanel vs Plesk in 2026.
• Moving an existing server? See migrating from cPanel to Plesk for the practical steps.
• Setting up a fresh Plesk server first? Walk through installing Plesk on Ubuntu 24.04.