What Velrix is
Velrix is a cloud platform. You use it to run virtual machines, including Windows Server, alongside containers and Kubernetes. It runs on your own servers, in your own environment operated by us, or in Velrix Public Cloud in Sweden.
You work in it from a browser. Velrix opens as a desktop with windowed apps: Apps, Machines, Volumes, Files, a Terminal and more. Everything you can do there, you can also do from the HTTP API, OpenTofu or Terraform, Ansible, or an AI agent over MCP.
What you can run
- Virtual machines, Linux and Windows Server, on Cloud Hypervisor. You open a machine’s console or its desktop in a browser window.
- Containers, as apps. Each app runs rootless, keeps the size you gave it, and is rolled back on its own when a new revision fails its health check. Where operators require it, an app runs sandboxed: the same image in a microVM with its own kernel.
- Kubernetes: managed RKE2 or k3s clusters on your machines, and a Kubernetes-compatible API for
kubectl. - Build jobs, in microVMs by default.
- Stacks: OpenTofu and Ansible runs with plan, approval and apply, with their state kept in Velrix.
Around them you get volumes with enforced sizes, project networks with security groups, hostnames with certificates for your apps, an image registry, metrics, and a desktop in your own brand and language. Every screen is in Swedish and English.
Who uses it
- People sign in and run things: apps, machines, volumes, stacks. Their work belongs to them or to an organisation they are a member of.
- Organisations group people, with roles that say who may do what, and projects that keep work apart.
- Operators run the installation itself: its servers, updates, licence, look, and who may sign up. They work in the Manager.
The words you will meet
| Word | Meaning |
|---|---|
| Realm | One Velrix installation: everything that trusts the same realm key. |
| Instance | One server of a realm. Instances are named a, b, c and so on. |
| Module | One part of the platform, such as apps, machines or sign-in. Each is a small program in its own container. |
| Organisation | A group of people with roles, who own resources together. |
| Project | A part of an organisation’s (or your own) resources, with its own network. |
| Catalogue | The sizes and blueprints your operator offers: what you can make, and how big. |
Concepts explains each of these in more depth.
How it is built
Velrix is a set of modules that find each other on their own and talk directly, with no central control plane between them. When one module stops, the others keep running while it is restarted, and operators are told. You choose which modules an installation runs, so a small installation stays small.
Every connection between modules uses post-quantum key exchange, and every module proves who it is with an identity signed by your realm key. Security and compliance has the details.