A dedicated server is physical hardware assigned to only you, which means ordering one takes longer than a VPS but gives you the entire machine.
Provisioning time is not instant
Unlike a VPS, which provisions on shared virtualization hosts in seconds, a dedicated server is a specific physical machine that has to be racked, imaged and tested before delivery. Delivery windows are shown on the product page and communicated again after checkout, treat that estimate as real when planning a launch date around it.
Choosing the OS at order time
Pick your operating system during checkout, this is what gets imaged onto the physical disk before delivery. Changing OS after delivery means a full reinstall and data loss on that server, choose deliberately rather than defaulting to whatever is first in the list.
What delivery includes
- Root/administrator access credentials, delivered the same way as a VPS, on the service page in the dashboard.
- IPMI or out-of-band access details, for reaching the server's hardware console independent of the OS, see the IPMI guide for what this is actually for.
- The IP range assigned to the server, and any additional IPs you ordered.
First things to check on delivery
Confirm CPU, RAM and disk match what you ordered (a quick check with lscpu, free -h and lsblk on Linux), and run your distribution's update command before installing anything. Catching a hardware mismatch in the first hour is a routine support fix, catching it after weeks of use is a much bigger conversation.
A dedicated server is yours alone the moment it is delivered, there is no neighbor's workload to ever share it with. That isolation is the entire reason to pick dedicated over VPS in the first place.
Can't find something?
Open a ticket and a real engineer will reply, usually inside two minutes.
Open a ticket