Virtual private servers
Instances with the oversubscription stated
Dedicated vCPU, dedicated memory, NVMe on the host. The table says what you get and the section under it says what is shared, which is the question a buyer of virtual machines actually has.
two
Instance sizes
same working day
Provisioning
no contention on dedicated hardware
vCPU to core, dedicated range
NVMe
Storage, every size
The instances
| Instance | vCPU | Memory | NVMe | Transfer | IPv4 | Per month |
|---|---|---|---|---|---|---|
| V1 | 1 shared | 2 GB | 40 GB | 2 TB | 1 | 4.50 |
| V2 | 2 shared | 4 GB | 80 GB | 4 TB | 1 | 8.00 |
| V3 | 4 shared | 8 GB | 160 GB | 8 TB | 1 | 15.00 |
| D1 | 2 dedicated | 8 GB | 80 GB | 8 TB | 1 | 24.00 |
| D2 | 4 dedicated | 16 GB | 160 GB | 16 TB | 1 | 45.00 |
| D3 | 8 dedicated | 32 GB | 240 GB | 24 TB | 1 | 88.00 |
What is shared, and what is not
Published because almost nobody publishes it, and because it is the only way to compare two instances honestly.
Never shared
- Your memory. The host does not overcommit RAM, so there is no ballooning and no swap on the host.
- Your storage. The NVMe capacity in the table is reserved, not thin-provisioned.
- Your addresses, your VLAN and your firewall rules.
Shared, and by how much
- Shared range, cores
Up to 4 vCPU per physical core - Dedicated range, cores
One vCPU per physical core, pinned - Host uplink
25 Gbit, shared, measured not sold twice - Storage bandwidth
Shared, per-instance limit published on request
What the extras cost
Published, so you do not have to ask. Everything on this card is optional and nothing is added to an order you did not place.
| Item | Unit | Rate |
|---|---|---|
| Additional uplink, 10 Gbit | per month | 45.00 |
| Additional uplink, 25 Gbit | per month | 120.00 |
| Transfer beyond the included allowance | per TB | 1.20 |
| Additional IPv4, /29 | per month | 8.00 |
| Additional IPv4, /28 | per month | 15.00 |
| IPv6, /48 | per month | 0.00 |
| Remote hands | per 15 minutes | 20.00 |
| Off-site backup | per TB per month | 4.00 |
| Private VLAN between machines | per month | 0.00 |
Questions we are asked
What is the difference between the shared and dedicated ranges?
The shared range puts several virtual cores on one physical core, up to four. The dedicated range pins one virtual core to one physical core and nothing else runs on it. Shared is cheaper; dedicated is predictable.
Can I move between sizes?
Memory and storage go up without rebuilding. Going down needs a rebuild, and we will say so rather than quietly migrate you.
Is there a snapshot facility?
Yes, and it is charged on the rate card by the terabyte rather than per snapshot, so taking ten small ones costs what one of the same size costs.
What hypervisor is it?
KVM on our own machines, with no overcommit of memory.
Do you charge for traffic in?
No. Inbound is free, outbound comes out of the allowance in the table, and over the allowance the rate card applies.
Next step
Start with an instance, move to metal when it stops fitting
The two live on the same network and the same private VLAN, so a database on bare metal with its application on a pair of instances is one order rather than two suppliers.