Ways to run Velrix
Velrix is the same platform wherever it runs. What changes is whose hardware it runs on, and who operates it.
| Where it runs | Who operates it | You need | |
|---|---|---|---|
| Installed | Your servers, from their own disks | Your team | Servers and the installer USB stick |
| Diskless | Your servers, booted over your network | Your team | At least one installed server to boot from |
| Managed | Your environment: your infrastructure or your cloud | Velrix | A place for it to run |
| Velrix Public Cloud | Datacentres in Sweden | Velrix | An account |
Installed on your servers
You install Velrix OS to each server’s own disk from a verified USB installer, then a guided setup in the browser takes you to a running installation. Updates come online or on a USB stick, so an installation with no internet connection is fully supported.
Choose this for your first servers, and for any server that holds data.
Diskless on your servers
A diskless server has no operating system disk. It boots over your own network from your Velrix installation, every time, and runs from memory. Its data comes back from the other servers after it boots.
- A new server joins only after an operator approves it.
- A server with a TPM gets its key sealed to that chip, so it reboots without asking again.
- Diskless servers depend on an installed server to boot from. Never run an installation of only diskless servers: if they all restart together, there is nothing to boot from.
Choose this for extra compute capacity, and for servers without reliable disks. You can mix both kinds in one installation, server by server.
Managed
Velrix runs in your own environment, on your infrastructure or in your cloud, and Velrix operates it for you. Your data stays in your environment. Talk to us to plan it.
Velrix Public Cloud
A public Velrix installation in datacentres in Sweden, operated by Velrix and outside the US CLOUD Act. There is no hardware to buy. Everything in these docs for users applies to it too. The operator guides are ours to follow, not yours.
Moving between them
Your apps, machines and stacks are described the same way everywhere, through the same API, OpenTofu provider and Ansible collection. An installation on your servers can also link to Velrix Public Cloud, so your people may work there too. See Federation.