Exclusive Access · Invitation Only
Stratum Compute Status: In development

Virtual machines, networked by Fabric from the first packet.

Stratum Compute is being built. Early access is open to a small number of hosting providers.

Request early access Explore Fabric

Specification · early access

virtualisation KVM (Intel VT-x / AMD-V)
networking Fabric, per VM
addresses Private networks, routed public IPv4
guests Linux cloud images
consoles Serial and graphical
management Same CLI and API

Early-access builds are pre-release: everything on this page can change before release.

Fig.01 — Early access

In the early-access builds.

Compute is designed around one idea: a virtual machine should never be on the network before Fabric is protecting it. These parts are in the pre-release builds early-access customers run.

  1. Virtual machines on your own servers

    KVM virtual machines with hardware virtualisation (Intel VT-x / AMD-V), on the same bare-metal nodes that run Fabric.

  2. Tenant isolation from the first packet

    Each VM’s port is locked to its own addresses and kept apart from other tenants’ VMs before the guest boots. Anti-spoofing, the firewall and bandwidth plans apply as to any Fabric workload.

  3. Set up on first boot

    Linux cloud images get their hostname, SSH keys, static addresses and your own cloud-init user-data when they first start.

  4. Public addresses

    A VM can hold one of the IPv4 addresses your provider routes to the server: reachable directly, never translated, usable only by that VM.

  5. Consoles

    Serial and graphical consoles for every VM, from the node’s command line or its API, with single-use tickets and an audit trail.

  6. One command line and API

    Managed from the same command line and API you use for Fabric.

  7. Designed to outlive restarts

    VMs are designed to keep running while Stratum itself restarts or updates, and to start again after a host reboot once their network is in place.

  8. Per-tenant VM limits

    Cap how many virtual machines each tenant can run on a node.

What each part does, and what it does not do yet, is in the early-access documentation.

Fig.02 — Planned

Still planned.

  1. A console in the browser

    Opening a VM’s console from a web page.

  2. Changing a VM after it is made

    More CPUs or memory, and extra disks, without recreating it.

  3. Volumes, snapshots and backups

    Disks that outlive the VM they are attached to, snapshots of them, and backups you can restore.

  4. Customer self-service

    Letting your own customers manage their VMs.

Fig.03 — Early access

What early access means.

Pre-release builds

You run builds before they are released, on your own hardware, and tell us what breaks.

Direct contact

You talk to the people building Compute, not a ticket queue.

A licence from us

There is no self-service purchase. After we talk, we issue your early-access licence ourselves.

Fig.04 — Requirements

What you will need.

CPUHardware virtualisation
A 64-bit Intel or AMD (x86_64) server with Intel VT-x or AMD-V, switched on in the server’s firmware.
Memory and diskRoom for guests
At least 4 GiB of memory, and at least 10 GiB free for guest disks. The installer checks both before it changes anything.
Operating systemA supported Linux distribution
Debian 12 or newer, or Ubuntu 22.04 or newer; early access is tested on Debian 13 (see the early-access documentation). The list is confirmed at release.
PlatformA Stratum node
Compute will run on a node that already runs Fabric, which will provide every VM’s network.

Want to run Compute early?

Tell us about your servers and the customers you would put on them. Early access is limited, so we will be honest about whether it is a fit.

Request early access