We at CloudLinux strive to provide our partners and customers with the most valuable and dependable solutions available. Unfortunately, at this time, we have decided to end sales and support for one of our products, KuberDock. After an extensive research, speaking with our customers, and re-evaluating the technology and the market, we have decided that additional investment into KuberDock's development is not viable.
The decision to discontinue KuberDock did not come lightly and was based on several factors. Docker technologies still show significant momentum, but despite this high potential, its adoption in the hosting industry was considerably lower than expected. Prepackaged Docker applications have not proven to be easily understood and consumed by the typical end-user. We have seen this across all of our KuberDock customers - marketing new applications to their customers proved to be a much more difficult task given the state of this mature and competitive industry. We understand that you have invested resources in offering KuberDock-based solutions, and we apologize for this inconvenience.
In order to help you manage the end-of-life transition, we will continue full 24x7 support of KuberDock until January 31st, 2017. After that date, and for the next three months until April 30th, we will provide limited support with response times of up to 2 business days.
As of Thursday, January 26th 2017, KuberDock will no longer be offered for sale. The ability to try and/or purchase it will be removed from our website and the CLN shortly.
We are stopping the development of the KuberDock platform effective immediately. The product is now free for the current KuberDock customers and can be used indefinitely (without support beyond the next 3 months). We are tentatively planning to make the platform available on GitHub as an Open Source solution sometime in February. All our KuberDock developers will be transitioned to various teams to continue improvement of our flagship products, CloudLinux OS and KernelCare, as well as rapidly expand the development of the new Imunify360.
Again, we apologize for any inconvenience that this may have caused you, but we hope you understand why we had to come to this difficult but necessary decision. Please feel free to contact us at sales [at] cloudlinux.com with any questions you may have.
Did you planning to convert this panel for general VPS (LXC, KVM, etc) panel? Maybe thats a bigger market.
Hi, Did you planning to convert this panel for general VPS (LXC, KVM, etc) panel? Maybe thats a bigger market.
That's a shame really i was going to try it but was put of by the price of it, you should keep it going but drop the price right down. That way people will take it up.
We had enough direct customers. The problem was that our customers couldn't attract customers to use the platform. We did evaluate the possibility to change pricing, but we didn't think it would change aforementioned problem.
This is really an shame. I selected KuberDock for us simply because I had outstanding support from you guys earlier with CloudLinux.
As I understood you're going to make KuberDock open source which means that we might be able to continue with it. However, if any one has any ideas of similar platforms for hosting providers, I would be more than eager to know. Having commercial support behind product is big plus.
In mind of new business ideas like Docker hosting, we're always very patient. Nothing good ever happens in a snap.
This is really an shame. I selected KuberDock for us simply because I had outstanding support from you guys earlier with CloudLinux. As I understood you're going to make KuberDock open source which means that we might be able to continue with it. However, if any one has any ideas of similar platforms for hosting providers, I would be more than eager to know. Having commercial support behind product is big plus. In mind of new business ideas like Docker hosting, we're always very patient. Nothing good ever happens in a snap.
We decided to stop KuberDock because we felt that our customers cannot gain their own customer. There was just no traction - and we felt we don't want to get more and more hosts down the road where they will face it.
Our product wasn't that well positioned for pure docker hosting. Docker, Amazon, Google, etc... all much better positioned for that.
Even OnApp platform, in my opinion, is better positioned for pure docker or pure kubernetes hosting. They recently rolled out support for k8s & docker which is much more native then what we were doing.
We wanted to target packaged applications hosting using docker ... and we realized there is no market for that.
We decided to stop KuberDock because we felt that our customers cannot gain their own customer. There was just no traction - and we felt we don't want to get more and more hosts down the road where they will face it. Our product wasn't that well positioned for pure docker hosting. Docker, Amazon, Google, etc... all much better positioned for that. Even OnApp platform, in my opinion, is better positioned for pure docker or pure kubernetes hosting. They recently rolled out support for k8s & docker which is much more native then what we were doing. We wanted to target packaged applications hosting using docker ... and we realized there is no market for that.
Igor, my hat rises for you honesty.
Any plans to release the code as open source?
Yes, we are planning to rip out license checking code and release it to github as GPL2 or GPL3.
This should be done within next two weeks.
Yes, we are planning to rip out license checking code and release it to github as GPL2 or GPL3. This should be done within next two weeks.
That's actually very cool. Appreciate your decision.