5 highly effective Proxmox alternate options you’ve got in all probability by no means heard of
Proxmox has develop into the go-to distro among the many self-hosting group as a result of it’s simple to make use of, feature-rich, and dependable.
That doesn’t suggest it’s for everybody, although. In many circumstances, it’s a bit extra than you may want. Or perhaps you simply do not just like the subscription-gated repo.
Whatever the case, listed here are 5 Proxmox replacements, starting from full hypervisors to a easy container stack, you could strive.
XCP-ng is the closest to Proxmox
A Xen-based hypervisor with its personal internet console
XCP-ng is an open supply model of XenServer (previously Citrix XenServer). Like Proxmox, it’s a type-1 hypervisor, however there are some essential variations.
Proxmox is constructed on Debian, whereas XCP-ng is constructed on a tiny microkernel, which hundreds a separate administration VM known as dom0. In principle, that makes VMs on the XCP-ng setup a bit much less liable to crashes, for the reason that dom0 VM can crash with out taking all the different VMs with it.
If your Proxmox distro crashes, your VMs and containers are going with it.
Critically, XCP-ng would not assist LXC containers like Proxmox does, successfully proscribing you to VMs until you launch one other VM to particularly home your containers—not a deal-breaker, however one thing to concentrate on.
Beyond that, XCP-ng has most of the similar fundamental options as Proxmox. You can create useful resource swimming pools, clusters, backups, and extra.
Cockpit provides VM and container administration to any Linux system
An internet dashboard that works with any Linux distro
If you need a tidy dashboard with out going by the difficulty of establishing a devoted hypervisor OS, you might use Cockpit. Cockpit is a browser-based admin panel that offers you a handy method to handle KVM-based virtual machines and Podman containers.
Cockpit is largely only a dashboard you should use to deal with storage, networking, and logs. Consequently, it is vitally gentle, even in comparison with one thing like Proxmox.
Its simplicity additionally comes with a number of large limitations. It would not have a built-in backup supervisor. It can also’t deal with clustering, which is critical you probably have a number of PCs you need to pool collectively.
A Podman stack skips the hypervisor
Run all the things in a container
If you do not want the devoted options that include a hypervisor or digital machines, you might simply run quite a few Podman containers as a substitute.
By default, Podman is rootless and integrates with systemd, which makes it each safe and simple to handle. If you need a person interface, you should use Cockpit or Podman Desktop.
By working Podman containers immediately on the host, you take away a little bit of overhead, which could possibly be important when you’re using a mini PC or a Raspberry Pi.
Most self-hosted companies can be found as containers as of late anyway, so the dearth of VMs in all probability will not be a big drawback.
Incus manages containers and VMs and helps clustering
If you need one thing that maintains Proxmox’s skill to deal with VMs, containers, and clusters with out as a lot additional, Incus is an inexpensive alternative.
Incus LTS gives 5 years of assist, which implies you do not have to undergo the improve course of as incessantly as you do with Proxmox. Proxmox roughly follows the assist window of the mainline Debian release.
Incus is pretty command-line heavy in comparison with Proxmox. It does have an online interface, however it’s pretty minimalist.
Harvester brings enterprise
When you want an enormous cluster at dwelling
If you must mix a number of totally different PCs into one unified system, Harvester is an effective alternative.
Proxmox is totally able to clustering, nevertheless it entails a good quantity of setup. You have to configure Ceph for shared storage, you must account for availability, and it’s a must to arrange some form of sync.
Harvester combines Kubernetes, VM assist, and distributed storage all into one neat package deal. Of course, all of this comes with a draw back: the {hardware} necessities.
Harvester requires at the least 32GB of RAM per node within the cluster, which makes it wasteful when you solely have one or two PCs. It additionally makes it a poor match for any low-power system you are making an attempt to show into a house server. Kubernetes additionally introduces some complexities of its personal which might be solely price it when you can truly use it.
Pick based mostly on what you truly run
Ultimately, your {hardware} will make loads of these selections for you. A low-power system signifies that Cockpit, Podman, or XCP-ng are your greatest choices, since they’re comparatively gentle. If you will have a number of machines and need a fancy cluster setup with out messing with Ceph, then you need to look into Incus and Harvester. Both are fairly succesful, however Harvester is designed for very succesful PCs. Don’t strive constructing a Pi cluster with it.
