All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Hypervisor is now VirtConsole - same panel, a name you can actually search for (v3.2.0)
Some of you know our panel as Hypervisor - the KVM/Proxmox control panel a few LET providers run their fleets on. We renamed it. Hypervisor is now VirtConsole, and 3.2.0 is the first release carrying the new name.
Why? Honestly: even though LET community did suggest against it, we picked the most generic word in virtualization and paid for it daily. You can't Google the product, reviews of us return VMware docs, and in our own manual "the hypervisor" could mean the product or the KVM host it manages. Full reasoning: https://virtconsole.com/blog/rebranding-to-virtconsole
What does NOT change (before anyone asks):
- Your license, pricing and terms - untouched
- Running installs keep working; updates via the same in-panel updater
- hypervisor.io endpoints keep answering through the whole transition
- Same team, same codebase, same roadmap
What's new in 3.2.0 besides the name:
- Windows SPLA licensing - enter your keys once, Windows guests activate on deploy, keys never reach the guest or the customer
- Managed SSL - account-level certs, SNI multi-cert on managed LBs, Let's Encrypt issue/renew + expiry alerts
- Built-in support desk - SLA tracking, scanned attachments, optional AI triage
- Import Doctor - pull VMs in from other platforms (Windows included); driver/boot issues detected and repaired offline so they boot first try
- System DNS - host public zones, with delegation checks that tell you exactly what's misconfigured
- One installer for Debian 11/12/13, Ubuntu 22.04/24.04/26.04, RHEL-family 9/10
Fresh install (as root - no sudo needed, minimal Debian friendly):
curl -fsSL https://packages.virtconsole.com/master/install.sh | bash
Existing installs move to the new layout with one command per node (hypervisor nodes first, then panel) - VMs, data, license and pricing preserved:
curl -fsSL https://packages.virtconsole.com/virtconsole-migrate.sh | DEPLOY_RELEASE=1 bash
Full feature set on every plan, from $2/hypervisor/month, free trial: https://virtconsole.com
Happy to answer anything here - stack questions, migration from Virtualizor/SolusVM/Proxmox, feature requests.
Comments
i wondered what you were thinking with the original name, good call sir.
https://docs.virtconsole.com/
Our new documentation is live!
LITERALLY THE HOMEPAGE
Why to bother doing tests ?
Is it same with your software as well or just website is handled by AI
Im not seeing that in my mobile chrome, what browser are you using?
I'm seeing it. Chrome, Pixel 10.
Should be fixed
Website is handled by AI
Just like everything else
Thank you for being honest.
What about the panel itself?
If you think AI was here in 2018, then by all means assume the panel was written by AI, v1 was in 2019 with most of the features already present, we are using Coderabbit and Claude for codereviews
Strictly speaking, it was here in 2018, but transformer networks weren't in vogue yet and it kinda sucked.
But I meant the current code. A lot of people nowadays just use their favorite LLM for all new code, even if the original codebase predates AI. It's good to know that you're only using it for code review! That's how it should be done!
It's easier for us to develop because we use Laravel, the kvm functionality etc on the other hand is all wrapped properly in services, jobs, queues pretty straight forward.
Most of the functionality is just a good understanding of how iptables, haproxy, L3/L2 networks and vxlan understanding. We use golang, rust for more resource intensive parts but billing, CRUD layer etc sits on Laravel. Metrics are from Victoriametrics, fetched from digital ocean's opensource agent modified for our usecase.
We just shipped VirtConsole 3.2.2 (plus a small 3.2.2.1 patch, more on that at the end). For anyone who has not seen it before: VirtConsole is a self-hosted control panel for KVM hosting. One master, any number of nodes, customer panel, admin panel, REST API, hourly billing or WHMCS/Blesta/HostBill/Paymenter, VPCs, load balancers, Kubernetes, managed databases, S3. This release adds a new compute type next to all of that.
MicroVMs (Firecracker)
Your customers can now run Firecracker microVMs that boot in seconds and bill per second of vCPU and RAM plus disk per hour. It is one resource with three parts:
E2B-compatible API
The sandbox API speaks the same wire protocol as E2B, so existing E2B code runs against your panel with two environment variables (E2B_API_KEY, E2B_API_URL=https:///api/e2b). The API keys page ships quick starts for Python, JavaScript, the CLI, cURL, Anthropic and OpenAI. If you have been getting asked for "sandboxes for AI agents", this is a way to sell them from hardware you already own.
For the admin side
Enable it per location (hypervisor group), flip the MicroVM engine on a node's card, and a Readiness page tells you what is still missing before customers can use it. Plans carry vCPU, memory, disk and the three prices; plan groups map plans to locations. Admin pages list every customer microVM with the node's live view.
Also in 3.2.2
Links