A Plesk server, assembled to your order

Plesk is a hosting control panel: a visual dashboard you log into to look after websites, mailboxes, databases, DNS records and SSL certificates without opening a terminal. cPanel answers the same need, but the two feel quite different in the hand. Plesk gathers everything into one modern interface with each site and its settings grouped together, whereas cPanel splits the job across two panels — cPanel for account holders, WHM for whoever administers the server. Plesk also has one advantage cPanel cannot match: it runs on Windows as well as Linux, while cPanel is Linux only. Picking between them usually comes down to habit and to what you are hosting. Anyone working with ASP.NET or MSSQL lands on Plesk under Windows, and the WordPress Toolkit plus the tidy layout make it just as popular for WordPress projects on Linux. On these plans, Plesk is installed and licensed on a VPS that belongs to you, so the panel covers routine work while root access handles the rest.

You do — say the word at checkout and we build it around your answer. Plesk is unusual in running natively on both platforms, which turns the question into a simpler one: what are you hosting? Choose Windows if the project needs ASP.NET, other .NET applications or MSSQL databases, since all of those depend on the Windows stack. Choose Linux for a standard PHP, MySQL and Apache or Nginx environment, which covers most WordPress, WooCommerce, Joomla and Laravel builds and generally runs with less overhead. The panel itself looks and behaves almost identically either way, so anything you learn on one platform transfers straight to the other. Because every plan is a dedicated VPS with root, built for you alone, this is genuinely your decision rather than something shared infrastructure decides on your behalf. If you are torn, describe the software you plan to run and our team will point at one.

Yes. The licence is inside the figure on the price tag, so there is no separate fee to budget for and no key to buy somewhere else. When we assemble the server we install Plesk, apply the licence and configure the panel, then hand over something that works — licensing never becomes your errand. The edition we provision covers the panel, the WordPress Toolkit and the core extensions that a typical build relies on, which is enough to start straight away. If your project wants a higher edition or a particular add-on beyond that, say so and we will lay out the options and the cost before anything changes. Because the licence belongs to the server we look after for you, it stays current for as long as your plan runs, and renewals happen quietly in the background rather than landing on your to-do list.

It does, on every Plesk plan we sell, and it is one of the better arguments for running WordPress on Plesk at all. The Toolkit collects the repetitive WordPress chores onto a single screen: install a fresh site in one click, duplicate an existing one, spin up a staging copy to try a change safely, then push that change live once you are satisfied. It updates core, themes and plugins in bulk across every install at once, and its smart update feature clones a site quietly, applies the update to the clone and inspects the result before anything touches your live pages. One-click hardening is built in as well, closing common security gaps across every install rather than making you work through them individually. If you look after more than a couple of WordPress sites, the Toolkit turns hours of manual maintenance into a few minutes in the panel.

These plans sit deliberately in the middle. We take the parts most people would rather not touch: provisioning the VPS, installing and licensing Plesk, configuring the panel, switching on free SSL and daily backups, keeping the hardware and the KVM layer healthy, and filtering DDoS traffic on the network. What you receive is a server ready to use. From there the panel is built so that everyday work — adding sites, mailboxes, databases and certificates — is a matter of straightforward menus, with no command line required. Root access is still underneath, so nothing is off limits if you or your developer want to go further. Support is staffed around the clock for infrastructure, provisioning and Plesk questions, and will help with resizing a plan or unpicking a problem. Put plainly: we look after the foundation, and the panel keeps routine management something you can do unaided.

Yes, and there is no charge for it. Once you have ordered, raise a ticket with the details of your current host and our team does the work — websites, databases, mailboxes and their messages, DNS zones, and, where the old host also runs Plesk, the subscription configuration too. Plesk includes a migration tool that connects to your previous server and moves accounts over in bulk, which keeps the process tidy and reduces the chance of anything being left behind. We can bring everything across and set it up on the new server first, so you can click through and satisfy yourself that it all works before a single visitor is affected. When you are happy, switch your domain's DNS to the new VPS and turn on free SSL. Because the copy is already sitting there waiting, visitors notice little or nothing. Coming from cPanel or another panel entirely? Still fine — describe the setup and we will map the cleanest route.