Service line

Compute that somebody is actually watching

Rent a virtual machine anywhere and you own the patching, the monitoring, and the 3am reboot. Our compute tiers come with an operator attached: we run the hypervisor and the cluster, we keep the base images current, and we answer when something stops.

How we approach it

Two runtimes, one operating discipline. Container workloads run on our Kubernetes tier with declarative manifests held in Git, which means a workload can be rebuilt from source of truth rather than reconstructed from memory. Virtual servers run on Proxmox with scheduled snapshots and backup targets on separate storage.

The distinction that matters to you is state. Containers are the right answer when your workload is stateless or keeps its state in a managed database. A virtual server is the right answer when you need a filesystem, a kernel module, root access, or software that assumes it owns the machine. We will tell you which one your workload actually is before you buy, including when the answer is that you do not need us for it.

Who this is for, and what is included

Who this is for

  • Teams with a Dockerfile who want it running without building a cluster
  • Businesses running line-of-business software that needs a real server
  • Developers who need a build agent, a bot, or a background worker with an owner
  • Anyone consolidating a pile of home lab boxes onto something maintained

Included across every tier

  • Host-level patching, monitoring, and capacity management by us
  • Scheduled snapshots with off-host backup copies
  • Private networking between your workloads and our managed data tier
  • Resource limits published up front, and enforced, so neighbours stay quiet
  • Egress through our edge with the same TLS and routing policy as our sites
  • Console or shell access appropriate to the tier, with credentials you control

Tiers in this service line

Every tier is operator-provisioned and every specification below is what we build to.

Comparison of Managed compute and containers tiers
Tier Monthly Annual Best for Details
Container Workload Entry $14 $140 −17% Your image, running on our cluster, described in a repository. Details
Managed Virtual Server Most common $32 $320 −17% A real machine with root, and somebody else responsible for the host. Details
Performance Virtual Server $72 $720 −17% More cores, more memory, and dedicated CPU rather than burst. Details
Scheduled Jobs and Workers $9 $90 −17% Cron that somebody notices when it stops. Details

Your image, running on our cluster, described in a repository.

$14 /mo

  • Declarative manifest held in Git, not clicked into a panel
  • Public hostname with managed TLS, or internal only
  • Restart policy, resource limits, and log access included

View details

A real machine with root, and somebody else responsible for the host.

$32 /mo

  • Root access on a real virtual machine, not a container
  • Scheduled snapshots with off-host backup copies
  • Hypervisor, storage, and network operated by us

View details

More cores, more memory, and dedicated CPU rather than burst.

$72 /mo

  • Dedicated CPU allocation rather than burst credits
  • 8 GB memory and 200 GB storage
  • Priority on capacity when we schedule host maintenance

View details

Cron that somebody notices when it stops.

$9 /mo

  • Execution history and exit codes, not silent failure
  • Alert on failure or on a missed run
  • Runs on maintained infrastructure, not somebody's desktop

View details

Relevant reading

Other service lines