Hostmantis acted way too soon. They should have (my opinion) thought about moving to a new control panel instead of raising costs for all existing accounts. It’s difficult to see how they can possibly serve their existing customers on cPanel, particularly as they offer up to triennial billing cycles, meaning that some customers will have up to two years or more pre-paid by the time they get hit by the cPanel change. IMO the only way to keep those customers without going into massive debt is to migrate them to another control panel - even if it’s Plesk (yes Plesk and cPanel are both owned by Oakley Capital, but there’s no reason it can’t be used short-term to mitigate damages). With that said it’s not their fault, they panicked and have tried to act quickly in response to give their customers as much notice as possible … however as I’ve mentioned on WHT I think the better response is to send out notifications this week to customers, and to start planning, but not to act yet.
A lot of hosts are already writing off the option of using Plesk, I think that’s a mistake especially for resellers, probably the best possible solution is to offer reseller customers the choice of Plesk, DirectAdmin, or InterWorx in the short term. Rack911 are doing a security audit of the other panels currently available (CyberPanel, VestaCP, CentOS Web Panel, APNSCP, WiseCP, User/Webmin, ISPConfig, and ClusterCS) which will be done over the next four weeks with the results published for everyone’s consideration. Their present advice is that DirectAdmin and InterWorx are both at a security level similar to Plesk and cPanel and so are safe to use (or at least as safe as Plesk and cPanel, nothing is 100% safe ever).
This security audit is actually great news for everyone thinking of managing their own VPS or for those who already do their own LAMP stack as it will provide very valuable advise as to which of the low-cost and free panels are safest.