Virtualisation hosts.
You bring the hypervisor.
Proxmox or VMware ESXi, or anything else you can boot from an ISO. We hand over the metal, the console and the addresses; the stack on top of them is yours.
- port
- 1, 10, 25, 40, 100 Gbps
- hypervisor
- yours
- boot
- any iso over ipmi
- locations
- AMS · MEP · IAD · PHX
One machine, many guests, your choices.
A virtualisation host is one physical server that runs many virtual machines. You install a hypervisor such as Proxmox or ESXi and cut the machine into guests, for your own services or for your customers.
We hand over the bare machine: console, addresses, power. The hypervisor, the cluster and the guests are yours to build and run. That is the whole difference from a VPS, where someone else made those choices for you.
How to choose.
- 01 ─ guests
List the guests you plan and how much memory each needs. Memory is the first thing to run out.
- 02 ─ headroom
Leave room for the guests you did not plan and for the host itself.
- 03 ─ addresses
Count addresses. Each machine comes with 2 IPv4 and native IPv6, and every extra IPv4 is $5/mo, so IPv6 is the cheap way to give each guest its own.
- 04 ─ recovery
Plan recovery through IPMI: the console reaches down to BIOS and boot order, so you can reinstall Proxmox or VMware ESXi without opening a ticket.
- 01 ─
Licensing that changed under you
on a meter or a shared hostAfter the Broadcom acquisition VMware moved to subscription bundles sized well past small deployments (public record).
hereProxmox or VMware ESXi, or anything else that boots from an ISO. The choice stays yours.
- 02 ─
SSH is not a console
on a meter or a shared hostMany hosts stop at SSH; the BIOS and boot order stay out of reach.
hereIPMI down to BIOS and boot order. Install and recover without us.
- 03 ─
An address for every guest
on a meter or a shared hostIPv4 is scarce and sold per address.
here2 IPv4 included, $5/mo per extra, and native IPv6 for every guest.
What to look for in the machine.
Guests ask for memory long before they ask for cores.
Every guest's IO lands on the same array.
Size to the guests you plan, with headroom for the ones you did not.
The hypervisor install and every recovery go through it.
The servers that fit this today are marked under the processor on the price list. The shelf changes; what to look for in the machine does not.
What your guests add up to.
Set the guests and their size. Each row is the smallest build option that holds the total, and the addresses are priced below.
- ipv4 included
- 2
- ipv4 extra
- 6
- extra ipv4 / mo
- $30
- ipv6
- native
carries over: memory 128 GB · cores 16c / 32t · storage 2 × 1.92 TB SSD · ipv4 8
Questions to settle before ordering.
- 01 ─
Can I sell VMs to my own customers?
Yes, and you are responsible for them: you must be able to identify them, and the rules you set for them can be no weaker than our acceptable use section (Terms, section 4).
- 02 ─
Can a guest run a VPN or a proxy?
Not as an anonymous proxy or a VPN exit for others: those are not allowed on our network (Terms, section 4). If you are unsure whether a setup fits, ask before you order.
The rest, for every machine: all questions and the terms.
- We do not manage the hypervisor, the cluster or the guests. No templates, no vCenter, no licences from us.[no]
- Addresses come one at a time, not as a block: 2 IPv4 with the machine and $5/mo for each one after that. IPv6 is native, sized with you at deploy time, the cheap way to give every guest an address of its own.[limit]
- Windows we install on request, on the host or as a guest, but the licences are yours: we do not supply or resell them.[limit]
- Anything that is a BIOS toggle is yours to set; the console reaches the whole way down to boot.[limit]
Tell us what it serves.
The workload, the working set, where the users are. We come back with a machine sized to it, a price and a date.
alsounmetered servers · CDN origins · streaming servers · game servers · storage servers · download servers · database & compute · blockchain node servers