The high-assuranceSwedish cloud OS

Run your virtual machines, including Windows Server, alongside containers and Kubernetes, on your own servers or in Velrix Public Cloud.

One licence for the whole installation, priced per core.

  • Data on your servers or in Sweden
  • Swedish and English
  • Built to WCAG 2.2 AA
The Velrix desktop in a web browser, with app icons in two tidy columns down the left and a taskbar along the bottom. The Cockpit window shows three apps, shop, api and docs, as cards with a green heart for healthy and their memory, cores and CPU, and a volume, shop-uploads, linked to shop. In front of it, the shop app’s window is open on its Deployments tab: revision 4 is active and deployed, and the history below it lists the earlier revisions with what each one changed, a variable or the health check.
The Velrix desktop in a browser: the Cockpit gives every app that passes its health check a beating green heart, and every change to an app is a revision you can read back and roll back.

Leaving VMware in three steps

Bring your virtual machines over in planned waves, run them beside containers and clusters, and know the price before you start.

  1. Import from vCenter

    Each VM is mapped to a host pool, size and network, then moved in waves that can roll back to the source.

  2. Run it all side by side

    Windows Server and Linux VMs on Cloud Hypervisor, beside rootless containers and managed Kubernetes.

  3. A predictable price

    One licence for the whole installation, priced per core, with no per-core minimums and no forced bundles.

See how VMware maps to Velrix

What you get

The parts a team moving off VMware asks about first, in one platform.

  • Windows Server in the browser

    Run Windows Server VMs and open each one’s remote desktop in a window, with nothing to install.

  • Live migration

    A running VM moves to another host, disk included, with a pause of about 100 ms in our tests.

  • Backups

    Scheduled, encrypted backups of state, volumes and VM disks, frozen for a consistent copy.

  • Cloud shells

    A shell in the browser, in a container or microVM, with the velrix command signed in as you.

  • OpenTofu and Ansible

    Plan, approve and apply runs in Velrix, with the state kept there and an optional second approver.

  • Updates in your windows

    Signed updates, by hand or in your windows; a module update failing its health check rolls back.

  • Logs with live tail

    What apps, VM consoles and jobs said, kept across deploys, searchable and followed live.

  • Your brand

    Your name, colours, wallpaper and words on the sign-in page, the desk and every window.

See the whole platform

Built to stand while falling apart

A module crashes: the rest keep running while it restarts, and operators are told. Files stops: the desk keeps its app shortcuts, and your files come back with it.

Module status

  • desk

    Desk icons and the start menu’s apps

  • cockpit

    The Cockpit window

  • files

    The files on the desk

  • notices

    The tray

Built for regulated environments

See security and sovereignty
  • Data where you choose

    On your own servers, or in Velrix Public Cloud in Sweden.

  • Post‑quantum

    Hybrid ML‑KEM key exchange and ML‑DSA signatures.

  • WCAG 2.2 AA

    The web client is built to it and scanned in light and dark.

  • GDPR and NIS2 support

    Processing records, disclosure requests and retention rules.

  • Open standards

    OCI images, Terraform and OpenTofu, Ansible and kubectl.

How Velrix compares

What Velrix includes, and where each of the others stands on it, from their own documentation.

Velrix compared with VMware vSphere and VCF, Proxmox VE and OpenStack
FeatureVelrixVMware vSphere and VCFProxmox VEOpenStack
A VM’s screen in the browserIncludedIncludedIncludedIncluded
Invoices to your customersIncluded, with Swedish VAT and OCRChargeback bills, in VCFNot includedRating only (CloudKitty)
Container image registry (OCI)IncludedIncluded (Harbor)Not includedNot included
Management interface in SwedishIncludedNot includedIncludedNot included
Developed inSwedenUnited StatesAustriaUnited States (Linux Foundation)

Checked against each vendor’s and project’s own documentation on 2 October 2026.

Sources

Pricing you can plan around

One licence for the whole installation, priced by its size: per physical core and year on a fixed term, or per vCPU-hour actually run on pay as you go. No per-core minimums, no forced bundles.

For example: a manufacturing company

3 × 24 = 72 cores, Windows Server and ERP, Standard edition, Fixed

€10,080 per year

See pricing and worked examples
  • Standard edition

    For a company’s own platform.

    from€140per physical core and year

  • Provider edition

    For hosting providers and MSPs.

    from€165per physical core and year

  • Public Sector edition

    For councils, regions, agencies.

    from€200per physical core and year

Your workloads keep running. A licence problem never stops or deletes running apps, virtual machines or data. At most, after warnings and a grace period, the platform turns read-only: viewing, exports and paying still work, and a valid receipt unlocks it at once.

All prices in euros (EUR), excluding VAT. List prices: volume, multi-year and public-sector agreements on request.

Questions we are asked

Are Windows Server licences included?

No. Microsoft’s licences are not part of the Velrix licence or its prices. Bring your own licence and activate it with your own KMS host, or, where the operator offers it, as in Velrix Public Cloud, take Microsoft licences billed monthly per core under SPLA.

Do bonded ports and VLANs work?

Yes. The installer groups ports into a bond (LACP, active-backup or adaptive load balancing), adds VLANs on a port or a bond, and gives each connection IPv4, IPv6 or both. You choose the connection that carries management and the traffic between servers.

Read the install guide
How do we move from VMware?

Import from vCenter. A planning report maps every VM to a host pool, size and network with its monthly cost, and VMs move in waves. A wave can roll back to its source VMs, which Velrix never deletes.

See the VMware mapping
What hardware do we need?

x86‑64 servers with hardware virtualisation (Intel VT-x or AMD-V), at least 16 GB of memory, 32 GB to be comfortable, UEFI firmware, and a TPM 2.0 for Secure Boot and diskless boot. Plan three or more servers: platform state is confirmed by a majority of them.

See the ways to run it
What support is included?

Business-hours support is included in every edition. 24/7 support with an SLA is an add-on, priced per installation.

Can it run fully offline?

Yes, on-premises. Licences and updates arrive as signed files on a USB stick, with no outside service reachable. A Fixed licence sends no usage reports at all; pay as you go reports by a signed monthly file instead.

See Velrixon your own terms

We walk through the platform and the architecture, and how Velrix would run in your organisation.

Pilot places are open ahead of general availability.