Install KLYRN VM beside what you have.
One command for the controller, on its own server or a spare one. Nothing on your hypervisors yet.
For providers running SolusVM 2 today
Change your panel. Not your customers' uptime.
KLYRN VM installs on the hosts SolusVM 2 already runs on, reads the estate without changing it, and takes each host over without restarting a guest. On 28 September 2026 a production estate moved this way with every running guest pinged once a second from outside: 0 packets lost.
Reading an estate costs nothing: a host in observe mode is not a licensed node.
What stays exactly as it is
Your guests do not notice.
- Every machine keeps running. A guest is not restarted to be read or to be taken over.
- Every address stays. Nothing is re-addressed, and the switch rules and routes on the host are left as they were.
- Every customer keeps their account. Each gets a one-time link to choose a password; the old one is never copied.
- Backup schedules are carried over and run to a backup server from then on.
- Windows guests come across too, consoles included.
What changes
Your customers get a better hour.
- The panel they sign in to. One sentence first, every action a word beside its icon, and it works on a phone.
- Who connects to whom. The node dials the controller. Nothing dials your hypervisors.
- The price. The first compute node is free, each one after it is $5 a month, with no fee per machine.
- Updates. Signed, checked before they are switched to, and applied to a node without touching a guest.
- What a licence can do. It can refuse a new node. It cannot stop a machine.
The order it happens in
Five steps, and you can stop after any of them.
Connect it to your SolusVM 2 panel, and let it read.
Servers, customers, plans and schedules are read into KLYRN's own tables. Nothing is written to the source.
Put an observing agent on each host.
Observe mode is read-only by construction: commands, hypervisor calls and file writes pass a guard that fails closed. 0 of 21 host artefacts differed around an observe install.
Take over one host, under a hold.
Every guest is checked against a baseline taken before, and one is driven through KLYRN as the canary. Until the hold is released, handing the host back is one click.
Invite your customers in.
Each gets a link, chooses a password, and finds their machines where they left them. If you bill through WHMCS, the module links each service to the machine already running.
Before you plan a date
What will stop a host, and what waits.
- A VLAN tag on a guest blocks that host. KLYRN VM creates no VLAN interfaces in this version, and refuses a host it could not carry correctly.
- Unusual guests block it too. A machine type outside q35 and i440fx, a disk that is not qcow2 or raw, a network disk or a macvtap interface.
- OpenVZ and Virtuozzo are out of scope. A container host is named and never counted as adoptable.
- Some actions wait on an adopted guest. Firewall groups, reinstalling and restoring wait until that guest's network is moved to KLYRN, which is not released yet. Power, console and backups do not wait, and a guest is resized in place while it is shut off.
Read your estate this afternoon.
Install it beside SolusVM 2 and look at what it finds. Nothing on the source changes, and it costs nothing to look.