Plesk Reviews

I used the product for tailored web application and WordPress hosting.

Initially, the integrated licensing was convenient. However, when I cancelled the subscription to transition to our own infrastructure, the subscription continued to bill us. The servers were kept online to allow a transition period and to ensure everything was functioning smoothly before removing the existing servers. During this time, I expected the licensing to automatically expire with the cancellation of the subscription. I later found out that billing would continue, and when I reached out to Amazon Web Services (AWS), I was told this is expected. The only way to stop it is to terminate the server. In other words, why allow the subscription to be cancelled if billing continues? When cancelling licenses purchased directly via Plesk, a cancellation will expire regardless of the server’s status.

The integrated design has been a benefit.

When a subscription is cancelled, the license should not continue regardless of the server state. If continued access is needed, users should purchase a monthly or alternative option directly via Plesk or another provider.

I used the solution for almost two years.

I did not use any previous solutions.

Make sure it's a good fit, and make sure to plan on terminating servers in tandem with subscriptions to avoid additional billing.

I have used alternate solutions.

What began as a pleasant experience has become frustrating due to extended billing and no responsibility taken to correct or prevent this from happening again. Responsibility is placed on the end user, with complexity between reaching out to AWS and Plesk. Even sharing this experience is met with the response that it is expected. If it is expected, then why allow the subscription to be cancelled? As we scale up, this is certainly not a good solution, which is why we have moved away from AWS. Flexibility was a key benefit; however, the experience has been poor overall, and the performance has degraded.