Solutions

Run your servers on Proxmox, with backups we restore in front of you

We install it, cluster it so the estate keeps running when a node dies, and put Proxmox Backup Server behind it. Then we restore one of your machines and boot it while you watch, because a backup job that reports success has proved nothing. On your hardware or ours.

Why run it yourself

Virtualisation licensing is sold per socket, per core or per host, and the number changes when the vendor decides it should. Proxmox removes that conversation.

What replaces it is your own responsibility for the thing underneath everything else you run. That is a fair trade if the cluster survives losing a node and the backups have been restored at least once.

Most have not been. A backup job that reports success every night proves that a job ran, and nothing else.

How it goes, step by step

Every step is a fixed price with its own deadline. You can stop after any of them and owe nothing further.

  1. 1

    Get the first machines running

    A virtual machine or a container built to a standard shape, with its resources, network, storage and access set the same way every time.

  2. 2

    Make it survive losing a node

    Nodes joined into a cluster with a quorum that holds, shared storage, and live migration proved by moving a running machine between hosts in front of you.

  3. 3

    Back it up and restore it

    Proxmox Backup Server installed, retention set, and a whole guest restored from the archive while you watch. The restore is the deliverable, not the schedule.

  4. 4

    Shut the front door

    The management interface restricted, its own protections switched on, and a way back in proved before we hand over so a hardening pass cannot lock you out of your own estate.

  5. 5

    Find out what you inherited

    If you want it

    For an estate somebody else built: what is running, what is exposed, what is not backed up, and what will break next, written down with severities.

  6. 6

    Stamp out machines from a template

    If you want it

    A cloud-init template so a new machine arrives configured rather than built by hand, which is what makes the fiftieth one as cheap as the second.

The steps above that are not marked optional come to US$636 before any per-person or per-machine work, which is priced per unit and shown on each task page.

Where this stops

Prices stay fixed because the edges are drawn before you book, not after.

  • We do not supply hardware. Sizing advice, yes. Ordering, no.
  • The migrations move guests using the tooling Proxmox ships for reading them. We are not a VMware or Hyper-V consultancy and do not hold ourselves out as one.
  • A backup we configure is watched by nobody here afterwards. The alerts go to you.
  • High availability is a cluster property, not a promise about your applications. A machine that fails over still restarts.

Questions people ask first

Tell us what you are running

Describe your situation and we will tell you which of these steps you need and which you can skip.

Support Resort assistant
Enter to send · Shift + Enter for a new line