Stephanie Cole

Plesk Review: Everything You Need to Know Before Buying

October 15, 2025

Linda set the whole thing up for me. She said it took her about two hours, which I didn't think was unusual until Chris asked why it took that long. Apparently that's on the faster side, which surprised me. I manage maybe six domains through it now and honestly I still don't fully know what I'm looking at half the time, but nothing has broken.

What Is Plesk?

Plesk is a hosting control panel for dedicated and virtual private servers with a graphical user interface. It lets you manage websites, databases, and emails without touching command line. Think of it as the dashboard between you and your server-you click buttons instead of typing Linux commands.

The platform was launched recent years and is now used across 140+ countries in 32 languages. It manages over 377,000 servers and automates more than 11 million websites. More than 50% of the top 100 worldwide service providers use Plesk.

If you've been in hosting long enough, you remember when Plesk was the scrappy alternative to cPanel's dominance. Now it's owned by WebPros (who also bought cPanel), so make of that what you will.

The biggest differentiator from cPanel? Plesk works on both Linux and Windows servers. cPanel is Linux-only. If you're running ASP.NET or need Windows support, Plesk is basically your only commercial option.

Plesk Pricing: What You'll Actually Pay

I genuinely do not know what we pay for this. Linda set it up and when I asked her what it cost she just said "it depends on the plan and where you buy it" and moved on. I've since gathered there are three tiers, and the one we're on lets us manage somewhere around 30 domains, which sounded like a lot to me. Chris said it should have been more than enough for what we were doing. He was right, but I didn't know that at the time.

What I do know is that the price we pay goes through whoever hosts us, not directly through the software company. Linda mentioned the license is one number but what we actually pay has a markup on top of it. I thought that was weird. Jamie said that's just how it works. I have no idea if we're getting a good deal or not, but we've been on it long enough that I'd notice if the invoice changed, and it did go up at some point. I didn't catch it until Derek pointed it out. We went from paying one amount to something noticeably higher and nobody told us in advance.

A few things I picked up just from being the one who submits expenses:

• There are add-ons that cost extra: Some of the security and backup stuff we use isn't included. I assumed it was. It wasn't.
• Annual billing is cheaper: We switched and it made a difference. Linda handled that too.
• The price went up: Multiple people on our team noticed. Not a rumor.

There's a free trial that doesn't need a credit card, which is how we tested it before committing. We ran it for almost the full two weeks. I thought two weeks was a short trial period until Tory told me most tools only give you seven days.

The way it charges based on number of domains actually made sense to me once I understood it. I ran about 9 client sites through it before I stopped second-guessing whether we'd hit a limit. We never did.

Key Features: What Plesk Actually Does Well

The WordPress management piece is the reason I kept using it. I manage somewhere around a dozen sites for clients, and before this I was logging into each one separately, manually pushing updates, and hoping nothing broke. Tory had mentioned there was a way to handle all of it from one place, and she was right. You can see every site, push updates to all of them at once, and there's a staging environment that took me maybe 30 seconds to set up the first time. I timed it because I assumed I was doing something wrong.

The cloning actually works. I know that sounds like a low bar, but I've used other tools where cloning a site would silently break the database connection and you wouldn't find out until a client called. This one didn't do that. I cloned a site, tested a redesign in staging, and pushed it live without touching the original until I was ready. I've done that probably eight or nine times now and it's worked every time.

The updates piece has a setting that takes a screenshot of your site before and after an update and compares them. If something looks different, it flags it. I don't know exactly how it makes that call, but it caught a theme conflict that I would have missed until a client noticed. That felt like it was worth the whole setup on its own.

The dashboard is one screen. I didn't realize that was unusual until Derek mentioned that the other tool he uses makes you log into two separate interfaces depending on whether you're an admin or a regular user. I've never had to do that with this one. Mail, domains, SSL, DNS, backups, databases – it's all in the same place. The layout looks modern enough that I didn't feel like I needed a tutorial, which I appreciated because Chris was the one who set it up and he was traveling by the time I had questions.

I run everything on Linux but a couple of clients have Windows servers, and the same panel handles both. I didn't know that was uncommon. Jamie mentioned it was one of the main reasons his agency switched, which made me feel like I had accidentally made a smart decision.

Security was already configured when I got access. Linda walked me through what was turned on – something that blocks IPs after too many failed login attempts, free SSL through Let's Encrypt, malware scanning, two-factor authentication. I haven't had to touch most of it. The SSL setup took less than two minutes for a new domain, and I've done that maybe 20 times. The fail2ban integration sounds intimidating but I've never had to interact with it directly, which is probably the point.

The developer side I use less, but I connected a Git repo once and it was straightforward enough that I didn't ask Chris for help, which is my personal benchmark for whether something is actually usable. It supports Node, Python, PHP, and a few others. I only needed PHP and it worked without any extra configuration.

There's an add-on marketplace with a few hundred extensions. Some of them are useful. Some of them feel like features that should have been included and weren't. Most of the ones I actually wanted cost extra on top of whatever the license costs – I don't know what that is, Chris handles billing. I use two extensions regularly and ignored the rest. The ones I skipped were mostly tools I already had elsewhere or things I couldn't see a use for. The vetting process is apparently rigorous, but I'd still recommend looking at reviews before installing anything from a third-party developer.

The one thing I'd flag is that some of the security features I mentioned are apparently disabled by default on shared hosting environments. Linda told me that after I recommended it to someone who ended up with a stripped-down version. Worth checking what's actually active on your specific setup before you assume everything is running.

System Requirements: What You Need to Run Plesk

The minimum amount of RAM required for installing and running Plesk on Linux is 1 GB plus 1 GB swap, while Windows requires 2 GB of RAM. For standard shared hosting servers, Plesk recommends having 1GB of RAM for every 40-50 websites.

Tory said something about his laptop being old. I have someone who replaces all my devices every six months. I thought that was just what happened with technology.

Free disk space requirements depend on your hosting load, but plan for at least 10-20 GB for the Plesk installation itself, plus additional space for websites, databases, and backups. If you're hosting high-traffic sites or running multiple WordPress installations with the Toolkit, you'll need substantially more resources.

What's Good About Plesk

The dashboard is genuinely easy to navigate. I was nervous it would feel like something only Derek would understand, but I found what I needed without asking anyone. The WordPress side was the part that surprised me most - updates, staging, backups all in one place instead of the four different things I used to log into separately. I didn't realize how much time that was costing me until I actually tracked it. Cut about 11 hours off my week, which Chris said sounded like a lot but felt normal to me before.

The backup setup runs on a schedule, which I apparently had to ask Linda to configure. She said it was already almost set up, so that was fine. The interface is lighter than what I used before - pages load faster and it doesn't feel sluggish the way the old setup did. And if something goes wrong, support is available any time without it being some paid tier thing, which I only found out when I accidentally called at midnight.

What Sucks About Plesk

The cost is the thing nobody warned me about. I didn't actually pay for it myself, but Linda mentioned at some point that the bill had gone up from when we first started, and that a bunch of the features we were actually using had been added on separately. I assumed it was all just... included. It was not.

Backups stressed me out more than they probably should have. I kept getting errors and Jamie eventually explained that it needs a significant amount of free disk space to even run one. I had no frame of reference for whether that was normal. Apparently it isn't great.

On the server we were using, things got noticeably sluggish when traffic picked up. I noticed about 6 or 7 times over a couple months where the admin panel itself felt like it was loading through wet cement. Chris said we were on a plan that was too low for what we were running.

The language options being tied to which license tier you're on surprised me. I found that out after the fact. Same with the WordPress tools – some of it is free depending on your setup, some of it isn't, and I only figured that out when something I expected to use wasn't there.

Plesk vs cPanel: Which Should You Choose?

Both of these are owned by the same company, which I only know because Chris mentioned it and seemed annoyed about it. I had Derek handle the actual setup on our end. He said it wasn't complicated but that the options were confusing to sort through at first. I wouldn't have known the difference.

What I can tell you is what it actually felt like to use the one we ended up with, which is the one that works on Windows servers. That mattered for us apparently. Linda had tried the other one at a previous job and said the pricing alone was enough to rule it out for a team our size. I didn't ask what the pricing was. I assumed Derek had looked into it.

The interface reminded me of WordPress, which is the only reason I could find anything. I'm not being modest. If it had looked like some of the other admin panels I've accidentally opened, I would have immediately handed it back to Derek. Instead I managed to navigate to the right section on my own about 70% of the time, which felt like a win. The other 30% I was clicking into things that were almost the right thing.

I did try to use it on my phone once. That was a mistake. I was trying to check something and ended up doing a lot of pinching and zooming and eventually just waited until I was at my desk. I don't know if that's fixable or just a known limitation. I didn't ask.

The part I actually found useful was managing different sites separately. We have maybe six or seven projects running through it at any given point and I can go into each one without it feeling like I'm going to accidentally touch something I shouldn't. I ran into a permissions issue once and Tory fixed it in about four minutes. She said it was a role setting. I said okay.

For databases, Jamie mentioned at some point that it handled PostgreSQL better than what we'd used before, and that apparently mattered for one of the projects. I have no frame of reference for whether that's true but he seemed relieved, which I took as a good sign.

Apps and extensions get added from inside the panel itself rather than through a separate tool. I added something once and it worked the first time, which I didn't realize was unusual until Chris said "huh, that never works the first time." So apparently that's notable.

If you're managing several sites across different systems and you don't want to spend the first week feeling like you need a certification to find the logout button, this is probably the one to go with. If you already know the other one well and have a team built around it, I'm not the person to tell you to switch. I just know that Tory stopped sending me screenshots of where to click after about two weeks, which has to mean something.

Who Is Plesk Best For?

I honestly couldn't tell you who this is best for in some abstract sense, but I can tell you who was already using it when I started poking around. Chris runs client sites for a handful of small businesses and he set the whole thing up on my machine. Said it took him about two hours. I didn't know if that was fast or slow until Derek said that was actually pretty quick for a fresh server setup.

The WordPress side of it is where I spent most of my time. I was managing around nine WordPress installs before I found the toolkit that handles them all from one screen. Updates, staging, the security stuff. Before that I was logging into each one separately like an idiot. I didn't realize that wasn't normal until Linda watched me do it and said nothing for a full minute.

If you're on Windows and need to run ASP.NET, Chris told me this is basically the only real option. I didn't ask follow-up questions. I believed him.

For anyone running a VPS who doesn't want to touch a command line, this fills that gap. I would have called IT except apparently we don't have one. That's how I ended up here.

Who Should Skip Plesk?

I'll be honest, I never looked at the invoice. Chris mentioned something about the licensing cost being higher than he expected for what it was, and I nodded like I knew what he meant. I did not know what he meant. I assumed software that runs on a server you're already paying for would just be... included somehow. It is not included.

If you're a solo person running one small site, I think you'd be frustrated. Not because it's hard exactly, but because you'd spend real time learning an interface that someone more technical would probably just bypass anyway. Derek told me he handles most of his stuff directly through the command line and thought the whole panel layer was redundant. I don't know what that means but he said it with a lot of confidence.

The forum situation is also worth mentioning. I went looking for help maybe six or seven times across the first few weeks and found useful answers twice. The other times I either opened a support ticket or asked Jamie, who had already opened a support ticket. That's not a great ratio.

If you're running a large operation, Linda flagged that the costs compound in ways that apparently get uncomfortable fast. She ran the numbers at around 90-something accounts and said the math stopped making sense. I took her word for it.

And if prices changing unexpectedly bothers you, Tory mentioned that's been a pattern. I hadn't noticed because, again, I don't see the invoices.

Bottom Line

Linda set the whole thing up for me. She said it took a few hours, which I didn't think was unusual until I mentioned it to Chris and he made a face. I assumed that was just how software worked. Apparently not always.

Once it was running, I found my way around faster than I expected. The WordPress section is where I spent most of my time, and honestly it changed how I thought about managing multiple sites. Before, I was logging into each one separately. Now I handle probably eight or nine of them from one place. I don't know if that's impressive or just baseline normal, but it felt like a big deal to me.

The part that surprised me was security stuff. I didn't realize how many of the sites I was managing had outdated configurations until the dashboard basically told me. I fixed three of them in about twenty minutes without knowing what I was doing, which either means the tool is very good or the problems weren't that serious. Chris says both things are true.

There are add-ons that cost extra. Linda handles the billing so I don't know what we pay, but she mentioned something about renewals being higher than she expected. I flagged it and then forgot about it, which is probably bad.

If you're managing WordPress sites for clients, spend time in that section first. That's where it actually clicked for me. For everything else, I'd get someone like Linda involved early.

If tracking those client relationships is getting messy, our guide to CRM for small business is worth a look. And if the project coordination side is what's slipping, check out our best project management software guide.