June 23rd, 2025
New
Refer Webdock to a friend and your friend will earn a 20%discount. There are no limits. Whatever your friends purchase within 3 months you receive 20% immediately from all their purchases in that time period.
It works like this:
You send an invite Send your friends a referral link that they can use when purchasing a server.
They make a purchase You receive 20% as Account Credit within 24 hours. You will be notified by email.
You receive your credits Your earnings can be used to pay your current or future subscriptions.
You receive earnings for 3 months For a full 3 months you receive a commission for any purchases your friend makes in that period.
Get your unique link here when you are a customer.
Any service purchased at Webdock will count towards your reward credit - but only server purchases will be discounted for your friend.
As soon as your friend makes a purchase for any amount, you immediately receive your reward credit to your account.
May 6th, 2025
New
We are thrilled to announce a set of resources designed to provide effortless transition solutions for migrating to Webdock, alongside enhanced attention to detail within our platform!
You can get the comparison overview here.
Migration Guides
Discover our collection of migration instructions to assist you in moving from your current system to Webdock seamlessly:
Access these guides directly through our support documentation and enjoy a hassle-free migration process.
Minor Fixes and Improvements
Resolved a textual error in the message displayed during new server creation, ensuring clearer communication with our users.
We are dedicated to continuously improving your experience with Webdock. Thank you for choosing our services!
May 6th, 2025
New
Introduction
Webdock has always had fast provisioning times, but with the rollout of our new infrastructure in Denmark and after all the changes we had done, we were not happy with provisioning taking up to - in some cases - a full 4-5 minutes. Here we detail how we managed to get provisioning time down to our best-case time of 25 seconds on an Epyc instance.
Analyzing the issue; finding the first minute
When we started working on this, the very first thing we noticed was that when we wrote network configuration we were firstly shutting down the instance, doing some stuff on the host, then starting it and writing network config and lastly doing a final reboot. Doing a shutdown and reboot of instances is an expensive operation, so the first thing we looked at was whether it was possible to apply networking after the very first boot of an instance and not have to restart it twice. With some magic on the host and with cloud-init, we achieved just that.
Once we had optimized that part of the workflow, we shaved off a full minute off provisioning time - now we were down to 2-3 minutes on average. Nice!
Using optimized images
After our launch of the Denmark DC - and rather recently in fact - we switched our Hypervisor from LXD to Incus. Incus is a truly open source (and much better maintained) fork of LXD. Despite this change, for compatibility reasons we were still using LXD images. After speaking with the guys that built our new hypervisor, Incus, we found out that the LXD images were extremely ill-optimized and included all sorts of junk that wasn't really required. This caused boot times to be slower by at least 10-15 seconds per boot.
Switching to Incus native images, which are much better optimized, saved another 20-30 seconds, getting us down to 1.5-2.5 minutes.
Making sure images were cached
The next optimization we looked at was that we noticed that a lot of times images were being downloaded from our image remote and not properly cached on our hosts. An image download could take something like 30-40 seconds, so making sure images were cached on hosts reduced provisioning time even further - we were now down to 1-2 minute provisioning time.
But wait: Why were instances booting twice once spun up the first time?
The next thing we noticed was that whenever a new instance was spun up it was doing a restart after having completed almost the entire boot process, why? After conferring with the people who built our Hypervisor - Incus - we found out that this was due to some race conditions and cloud-init needing to initialize some stuff through templates passed through the hypervisor. We found that we could eliminate this step, ultimately getting us down to our current "record" time of about 25 seconds for a base Noble image on Epyc.
Your results may still vary
Although our current best provisioning time - a base Noble image on an Epyc instance - is about 25 seconds, your results may still vary a bit. Although images are now generally cached, sometimes our system needs to re-download an image, adding about 20-30 seconds. In addition, our LAMP/LEMP stacks are a bit slower to provision as we do a lot of additional configuration steps to set up users for ftp, mysql etc. - also, which profile and platform you provision on impacts provision time - obviously a pico4 profile on Xeon which only has 1 CPU thread to work with will provision slower than a beastly Epyc instance.
With all that said however, you should in real life - most of the time - see sub 1 minute provisioning and worst case 1-2 minute provisioning time.
We are pretty happy with that result :)
Arni Johannesson, CEO Webdock
May 6th, 2025
New
We have now finally completed all of our lengthy shakedown testing and changes to our platform stack required for our new datacenter in Denmark to go live. This project has been a long time coming as some of you may know. We started building our DC more than 1 year ago and the process has been fraught with delays and many challenges.
All of these have now been overcome and we are very happy to announce that you can now create servers in our brand new DC.!
Denmark DC replaces the Finland DC
It is no longer possible to create instances in our old location in Finland. Any new servers must be created in Denmark.
Huge Improvements in hardware and networking
The Denmark DC has a lot of benefits over our old Finland location, namely really good network connectivity and really great hardware. In fact, most of our Xeon users should see up to 30%+ better CPU speeds and now all instances are provisioned on fast NvME drives.
Complete rebuild of our snapshots and backup infrastructure
Not only will your instance run faster in Denmark and have better network (with free DOS protection from Voxility) you can now enjoy almost instant snapshotting and much faster backup operations in general.
Migrations will start happening soon ...
If you are a customer in Finland currently, you have already been informed that we will start migrations this week. If you haven't already booked a time for the migration, feel free to do so now as we will not be accepting further bookings from Monday onwards. Go to this link to book a free time slot for your migration: https://appointments.vps.webdock.cloud/
If you do not book a time, you will be migrated on a first-come first-serve basis at some random time in the coming two weeks.
Do you want to be migrated already now?
We are able to migrate instances already now, so if you want to get up and running quickly in Denmark and don't care about the specific time of migration, simply write Webdock support in our chat providing your server name and we will put you on a priority list.
You can also migrate your server(s) yourself today, if you don't mind getting a new IP address
You can actually go ahead and spin up your server(s) on the new DK infrastructure today, if you want. All you have to do is create a server in Denmark from a snapshot in your account, and your server will be spun up in Denmark. For large servers it may take a while to stream all the data from Finland to Denmark, but your machine will come up on the fast new infrastructure with a new IP address assigned.
Read more on our DK Datacenter here.