Getting started
Requirements & compatibility
Supported virtualization types, operating systems and sizing — what works where, honestly.
Updated Edit this page on GitHub
HipnoType needs a real kernel for nftables, cgroups v2 and Docker. The installer checks this during preflight and refuses environments it cannot support honestly.
Virtualization matrix
| Environment | Install | Notes |
|---|---|---|
| KVM / QEMU | ✔ Full support | The recommended target. All features work. |
| Bare metal, Xen, VMware, Hyper-V | ✔ Full support | Treated as full when the capability checks pass; bare metal asks for HIPNO_ALLOW_BAREMETAL=1. |
| LXC / LXD container | ◐ Feature-gated | Needs security.nesting=true for Docker; some kernel features are skipped with an honest status. |
| Docker / Podman container | ◐ Restricted | Panel + proxy run; nested container workloads are unavailable and reported as such. |
| OpenVZ / Virtuozzo | ✘ Refused | No real kernel — the installer refuses unless forced with --force for a limited panel-only mode. |
Operating systems
| OS | Versions | Arch |
|---|---|---|
| Ubuntu | 22.04, 24.04 | x86_64, arm64 |
| Debian | 12 | x86_64, arm64 |
| AlmaLinux | 9 | x86_64 |
| Rocky Linux | 9 | x86_64 |
Sizing
| Resource | Minimum | Comfortable |
|---|---|---|
| RAM | 1 GB | 2 GB+ (Docker templates) |
| Disk | 10 GB free | 20 GB+ |
| Network | Outbound 443 (relay + releases) | — |
Conflicts
The installer refuses to run alongside aaPanel, CyberPanel, CloudPanel, cPanel, Plesk or Coolify — one control panel per VPS.