We are renaming the platform. Hypervisor is becoming VirtConsole, and our home on the web is moving to virtconsole.com. Nothing about the product, your license, your pricing or your running installations changes - this is a name change, done carefully, and this post explains the reasoning and the mechanics.
Why rename at all
When we named the product “Hypervisor”, we picked the most descriptive word in the room. That turned out to be the problem.
- You cannot search for us. “Hypervisor” is the generic term for the entire category of virtualization software. Searching for our product, our docs or reviews of us returns KVM, VMware, Hyper-V and a decade of textbook articles - everything except us. A product that cannot be found by name has no name.
- You cannot even talk about us unambiguously. In our own documentation, “the hypervisor” can mean the product, or the physical KVM host the product manages. We wrote around it in every page; support conversations trip over it weekly.
- A generic word cannot be owned. There is no meaningful trademark, no distinct search presence, and no way to stop the name from meaning something else in every sentence it appears in.
Why VirtConsole
We looked at well over a hundred candidates, from invented words to abstract names, and kept coming back to one requirement: the name should be easy to pronounce, easy to remember, and it should say what the product is - the same qualities that drew us to “Hypervisor” in the first place, minus the genericness.
VirtConsole is exactly that: the console for your virtualization. One glance and you know it is a control panel for virtual infrastructure - KVM, Proxmox, Kubernetes, storage, networking - all driven from one place. It is short, readable, pronounceable in any language our customers speak, and it is distinct enough to be searched, linked and owned.
What changes
- The product name in the panel, installer, documentation and marketing becomes VirtConsole.
- Our website and documentation move to virtconsole.com, with the existing hypervisor.io addresses redirecting.
- Public repositories, packages and container image paths will be republished under the new name over the coming weeks, with the old paths kept working through a generous deprecation window.
What does not change
- Your installation. Panels keep running exactly as they are. Updates arrive through the same in-panel updater.
- Your license. Licenses, terms and pricing are untouched. Licensing and package endpoints on hypervisor.io keep answering for the entire transition and beyond.
- The product and the roadmap. Same codebase, same release cadence, same team building it.
Timeline
The rename rolls out gradually: website and documentation first, then the panel branding in an upcoming release, then repositories and package paths - each with redirects and advance notice in the release notes. There is nothing you need to do.
Thanks for building on the platform with us. Same product, better name - see you at virtconsole.com.