websavers
Regular Pleskian
Hey Plesk folks...
A few months back, Plesk nearly doubled their partner licensing fees, making a Web Host License actually *more* costly than a cPanel license. OK, I can (barely) stomach that.
But now, even new functionality which should have existed for years -- the ability to allow clients to backup on a schedule to cloud services like Amazon S3 -- cost us extra? We're already paying a premium for having a web host license and yet you want us to pay even more for features that should be baked in? I can't say I'm pleased about that. What's the point of upgrading to new releases if *all* the great new features are going to cost us more money?
Additionally, with earlier releases of the Dropbox plugin customers could set schedules for their backups. The plugin was horribly broken in many ways and needed to be fixed, but you've left us with two options:
1) Pay more to get the same functionality we had before, or
2) Remove scheduled backup to Dropbox functionality
Neither of which are great.
The reality is as follows, and I think the Plesk team should pay serious attention to this as it affects your long-term revenues. I highly doubt we're the only ones thinking along these lines. Our previous server strategy was to use larger numbers of less powerful machines so as to distribute the load with better precision and reduce the impact of outages as they would be contained to individual machines. This also happened to benefit Plesk because we'd be buying new licenses regularly.
However in order to ensure our growth plan is economically feasible when we have to deal with *both* Plesk core licensing increases *and* regular money grabs like "Backup to cloud Pro", we now have no choice but to revise our server strategy. We will be changing to using bigger servers that require less overall licenses and therefore our regular purchasing of licenses will decrease overall thanks to these pricing changes.
Also keep in mind that in the next two years, a large number of hosting providers are going to be forced to migrate their massive quantities of CentOS 6 machines to CentOS 7 (because there's no upgrade path), and in that process, I'm willing to bet that *many* of them are going to be considering merging machines simply to get their licensing fees back to what they were in 2017, prior to the license fee changes.
Setting your pricing model in a manner that encourages your customers to buy less from you does not seem like a good idea to me. Is this really the kind of change you want?
A few months back, Plesk nearly doubled their partner licensing fees, making a Web Host License actually *more* costly than a cPanel license. OK, I can (barely) stomach that.
But now, even new functionality which should have existed for years -- the ability to allow clients to backup on a schedule to cloud services like Amazon S3 -- cost us extra? We're already paying a premium for having a web host license and yet you want us to pay even more for features that should be baked in? I can't say I'm pleased about that. What's the point of upgrading to new releases if *all* the great new features are going to cost us more money?
Additionally, with earlier releases of the Dropbox plugin customers could set schedules for their backups. The plugin was horribly broken in many ways and needed to be fixed, but you've left us with two options:
1) Pay more to get the same functionality we had before, or
2) Remove scheduled backup to Dropbox functionality
Neither of which are great.
The reality is as follows, and I think the Plesk team should pay serious attention to this as it affects your long-term revenues. I highly doubt we're the only ones thinking along these lines. Our previous server strategy was to use larger numbers of less powerful machines so as to distribute the load with better precision and reduce the impact of outages as they would be contained to individual machines. This also happened to benefit Plesk because we'd be buying new licenses regularly.
However in order to ensure our growth plan is economically feasible when we have to deal with *both* Plesk core licensing increases *and* regular money grabs like "Backup to cloud Pro", we now have no choice but to revise our server strategy. We will be changing to using bigger servers that require less overall licenses and therefore our regular purchasing of licenses will decrease overall thanks to these pricing changes.
Also keep in mind that in the next two years, a large number of hosting providers are going to be forced to migrate their massive quantities of CentOS 6 machines to CentOS 7 (because there's no upgrade path), and in that process, I'm willing to bet that *many* of them are going to be considering merging machines simply to get their licensing fees back to what they were in 2017, prior to the license fee changes.
Setting your pricing model in a manner that encourages your customers to buy less from you does not seem like a good idea to me. Is this really the kind of change you want?