Third Party Control Panels
Last updated: October 20th 2021
Webdock works well with third party control panels such as Runcloud, GridPane, Laravel Forge and Ploi. We have tested Webdock with all these services and they work very well. On this page we describe these services and go through any quirks each service may have with regards to Webdock.
Runcloud is very fully featured and has some management tools Webdock still doesn't have, such as Supervisord, switching PHP CLI versions on the fly, Beanstalkd, controlling your firewall and extended Git integration. Runcloud may need a bit of maturing before it's ready for enterprise deployment, according to some of our users.
To get started with Runcloud, create an account with them and then in Webdock provision a clean Ubuntu OS server. SSH in to your server and paste a command Runcloud gives you and off you go.
You would then manage snapshots and other server specific features in Webdock and the rest in Runcloud.
GridPane has now been around for a few years and is off to a great start. Their control panel is fully compatible with Webdock and has a lot of great features well suited for managing multiple Wordpress sites on a single server. If you are in need of a shared-host type setup then GridPane is one to check out.
GridPane has a wide range of integrations and we can't wait to see where they take their product - we like their panel a lot, although at this stage it might need a little bit more UI polish before it's perfect.
To get started with GridPane, you'd basically follow the same steps as with Runcloud: Create a clean Ubuntu OS server with Webdock, SSH to your server and paste a command GridPane provides you.
Ploi is a very fully featured control panel with lots of integrations. We really like the look of Ploi and it is worth a look if their featureset is what you are looking for.
Ploi is (as of 2020) fully compatible with Webdock and we had no problems testing most common features and functionality.
To get started with Ploi, you'd basically follow the same steps as the other panels: Create a clean Ubuntu OS server with Webdock, SSH to your server and paste a command Ploi provides you.
SpinupWP is a modern cloud-based server control panel Designed for WordPress to help you implement best practices for every server you spin up.
SpinupWP (as of testing late 2020) totally works with Webdock.
The method we tested with SpinupWP was using their public key authentication, we provisioned an Ubuntu 20.04 server, added a shell user named "admin" and added the SpinupWP public key to it. Furthermore we enabled Passwordless Sudo for the server, after which the installation of SpinupWP completed without a hitch.
Laravel Forge is the grand old man in 3rd party control panels, but does not seem to have been expanded much in a long time. When we started building Webdock one of our main objectives was that we wanted to clone all the functionality of Laravel Forge in order to provide a good featureset for web developers. In short: Webdock does everything Laravel Forge does and some things we do better.
Case in point is the stack that Laravel Forge configures: It is not very optimized and suffers from numerous subtle bugs.
You should only use Laravel Forge if you are aware of all its quirks and are committed to this platform and workflow. As is the case with Runcloud and GridPane, to get started with Laravel Forge just create an account with them and then in Webdock provision a clean Ubuntu OS server. SSH in to your server and paste a command Forge gives you and off you go.
You would then manage snapshots and other server specific features in Webdock and the rest in Forge.
Cyberpanel is a control panel that uses OpenLiteSpeed as the web server and is a fully featured control panel with a lot of nice bells and whistles. A the time of writing their installer will not install on our LXC backed VPS servers as they have had some incompatibility issues with this virtualization in the past. However, we tested this internally and simply by removing the incompatibility check from their installer, we were able to install Cyberpanel just fine and all basic functionality we tested was functioning as expected.
For this reason we have posted a ticket with them here: https://github.com/usmannasir/cyberpanel/issues/589
And hopefully they will soon start to "officially" support our virtualization, or at least not have such a hard block on Cyberpanel installation. Please see the ticket above if you want to try the workaround we found to install Cyberpanel on LXC yourself.
Plesk now supports Ubuntu Focal - see the full OS compatibility here:
So will run on Webdock. Webdock does not provide any Plesk licenses at this time, nor do we pre-install Plesk for customers. You need to obtain a Plesk license and install it yourself.
Directadmin (https://www.directadmin.com) is in use by several of our customers so we know for a fact it works on Webdock. We have not installed it ourselves however so we cannot give any specific recommendations or hints to succesful setup.
Hestia is another control panel which has been reported as working with Webdock by our users. Webdock staff has not tried to install it so we cannot give specific hints or advice for succesful setup.
Since we launched the ability to install Alma Linux on Webdock then cPanel can now be installed and will work on Webdock. Please see our installation guide for cPanel for instructions.
Control Panels that do not work with Webdock
The following is a list of control panels which for some reason or another do not work with Webdock.
Serverpilot does not want to support running on a system backed by a container hypervisor such as LXD which Webdock uses. Given that other similar panels work on our servers we can imagine they could work on Webdock if they wanted to, but as of now we have no indication they want to move in that direction. If you really love Serverpilot and want to use it with Webdock, you can consider reaching out to their team and indiciating your interest to them. If you hear something positive from them, or if Serverpilot starts working on Webdock, please let us know so we can get this information updated.
Cloudron uses Docker to deploy their images and they want their Docker install to use overlay2 as the filesystem driver. This is not supported in our LXD backed servers at this time. If overlay2 support makes it downstream in the future, we will make sure to re-test Cloudron and update this section.