Prerequisite: Web Host Edition. The Web Admin Edition included with the vServer has no reseller management and covers 10 domains — service plans and end-customer accounts only come with the upgrade to Plesk Web Host (bookable in the customer center mein.xaweho.de, extra charge on the product page).
With Web Host you get Plesk’s full reseller management. Here are the basics, and when you need your own service plans.
The basics in Plesk
Service plans define what an end customer gets (storage, domains, mail, permissions); end-customer accounts get their own Plesk logins within your plan. Both run directly in the Plesk interface under Service Plans and Customers — the dialogs walk you through all the fields. Questions about a specific setup: open a ticket, we’ll look at it together.
vServer-specific differences
Quotas can be more generous
On the shared reseller plan you’re bound to the plan quota. Example: Reseller Plus has a 500 GB pool — if you offer 25 plans at 50 GB each, it’s fully allocated.
On the vServer, the whole server is yours. The quota is only limited by hardware:
- Solo (100 GB): 5–10 plans at 10–20 GB each makes sense
- Studio (250 GB): 10–25 plans at 10–25 GB each
- Werkstatt (500 GB): 20–50 plans
- Agentur (1 TB): 50–100+ plans
You can also offer unlimited quotas — only actual usage counts, and we send you a quota warning when the server fills up.
Per-plan performance guarantees
On the shared reseller plan: all end customers share the server load. You can’t say “I guarantee this customer more CPU”.
On the vServer: same limitation, but the whole server is yours. If you promise a premium customer more performance, it’s in your hands to pause other customers during maintenance phases or to identify resource-hungry sites.
Recommended plan strategy for the vServer
3-plan setup for mid-size vServers (Studio/Werkstatt)
1. Small (for hobby customers, club sites)
- 5 GB disk space, 5 DBs, 10 mailboxes
- Standard permissions
- ~€5/month end-customer price
2. Standard (small businesses, a single WordPress site)
- 20 GB disk space, 25 DBs, 50 mailboxes
- DNS management, backup restore
- ~€10/month end-customer price
3. Premium (multiple sites, a shop)
- 100 GB disk space, unlimited DBs/mail
- SSH, cron, all features
- ~€25/month end-customer price
Single-plan setup (if you only host your own sites)
If you have no end customers:
- Skip the Web Host upgrade — the included Web Admin Edition (10 domains) or Web Pro (30 domains) is enough
- Don’t create service plans
- Add domains directly in Plesk
- You work with the full server resources
Resource monitoring of end customers
Unlike the shared reseller plan, the vServer gives you a better view of actual resource usage:
- Plesk statistics: disk/traffic usage per end customer
- Server CPU load: in Plesk → Tools → Server Performance
- Disk IO per end customer: identifiable for very active sites
More in Performance monitoring.
Migrating end customers from a shared reseller plan
If you want to bring your end customers from the shared reseller plan over to the vServer:
- Open a ticket — we migrate internally
- End-customer logins, service plans, domains and data come over 1:1
- DNS stays the same
- No noticeable downtime for end customers
Our recommendation: migrate all end customers at once, not piecemeal — otherwise you end up managing two Plesk areas.
Migrating end customers from an external provider
With the Plesk Migrator on the vServer, you can pull end customers from another Plesk server on your own:
- Open the Plesk Migrator
- Enter the source server login
- Select the end customers to migrate
- The migration runs
More in Using the Plesk Migrator.
Bulk actions across end customers
Same as on the shared reseller plan:
- WP Toolkit for mass updates of all WordPress sites
- Mass suspension (e.g. during maintenance)
- Mass notifications
The workflow runs entirely in the WP Toolkit — select sites, choose the action, run it.
The end-customer view — what do they see?
The end-customer Plesk view is standard customer Plesk:
- Their own domains, mail, DBs
- WP Toolkit (if the service plan allows it)
- Backup restore (if allowed)
- File Manager
- Statistics
They do not see:
- Other end customers
- Reseller settings
- Server OS functions
Frequently asked questions
Can I change service plans later? Yes, affecting all assigned customers — Plesk syncs plan changes to existing subscriptions.
How many end customers fit on a Studio vServer (8 vCPU, 16 GB)? Realistically: 25–50 active end customers with a mix of static sites and WordPress. With many high-traffic sites: fewer.
My reseller plan is overloaded — does switching to a vServer make sense? Yes. With noticeable performance problems or >25 active end customers, the switch pays off. We migrate internally, no effort on your side.
Can end customers have their own service plans (sub-resellers)? Plesk Web Host technically allows it. In practice it’s rare on vServer setups. If you really want sub-resellers, write to us — we’ll configure accordingly.
What happens to end customers if the server fails? RAID10 protects against disk failure. On a complete server failure: VM migration to another host. Plus daily backups (every 6h, in fact) — worst case, 6h of data lost.
Can I move an end customer to another vServer (including my own)? The Plesk Migrator does that. Open a ticket if you need help.
Syncing service plans across multiple vServers — possible? Plesk doesn’t have that directly. Workaround: create the plans identically on each server by hand. If needed, we build an API integration on request.
What’s next
First login to the Plesk vServer
What you get after ordering, what the Plesk admin login looks like, which edition is installed and who's allowed to do what.
Using the Plesk Migrator
Clean server-to-server migration with the Plesk Migrator. Point it at the source server, the data comes over. Single site or bulk migration.
Requesting changes via ticket
What we do on the vServer for you: custom services, custom config, OS changes, exotic PHP extensions. And how to write the ticket.
Performance monitoring on the vServer
What statistics Plesk shows, when to scale, how to find bottlenecks. Plus: what server monitoring we run in the background.