OrkestraVM: The In-House Virtualization Platform Behind Every MioriticHost VPS

Why We Built Our Own Virtualization Platform

MioriticHost has been providing web hosting since 2011. When we built our VPS offering, we looked at the existing options, and the conclusion was clear: enterprise solutions carry a heavy layer of complexity. A VMware-based setup requires vCenter, ESXi licenses, dedicated management servers, and a long list of components that all need to work together. Container-based platforms like Virtuozzo simplify some things, but they trade away real isolation: every client on the same physical server shares the same kernel. A noisy or problematic neighbor can affect everyone else.

Our answer is OrkestraVM, a KVM virtualization platform written in-house using Go, as a single self-contained application. Development started in 2025 and is ongoing. It is not a product we sell to other companies; it is the engine behind every MioriticHost VPS. Physical servers are managed over plain SSH, with no cluster software or license servers required. Fewer components means fewer failure points and a codebase that is straightforward to audit.

From Order to Running Server: Full Automation

• Automatic provisioning: When you place an order, the WHMCS billing system triggers VPS creation automatically, with no manual intervention from our team. The server receives its IP address and network configuration without any extra steps.
• Available operating systems: Debian 13, Debian 12, Ubuntu 24.04, Ubuntu 22.04, and Rocky Linux 9. You choose at checkout; the platform handles the rest.
• Windows Server support: If you need Windows, you can use your own license. The server is configured automatically, with the password set and Remote Desktop access ready from the first boot, no additional setup required.
• Automated lifecycle operations via WHMCS: Suspension, reactivation, package upgrades (more CPU, RAM, or disk), and service termination all happen automatically, without needing to contact support for routine actions.
• True KVM isolation: Every VPS runs with its own isolated kernel. Unusual resource consumption or a problem on another client's server does not propagate to yours. Allocated resources are dedicated, not silently shared.

What You Can Do from the Client Portal

The OrkestraVM client portal gives you direct control over your VPS without opening a support ticket for basic operations. From the interface you can start, stop, or reboot the server, view usage graphs for CPU, memory, and disk, and retrieve the root password whenever you need it. If the server becomes unreachable over SSH, the VNC graphical console opens directly in your browser with no additional software to install. You can also initiate a restore from backup directly from the portal, without involving the support team for routine recovery scenarios.

Practical tip: Right after you receive access to your VPS, check the usage graphs during the first 24 hours after installing your applications. If CPU or memory consistently reach the limit of your chosen plan, that is the right moment to upgrade, before the server slows down under real traffic.

Secure Backups and Platform Security

• Daily hypervisor-level backups: Stored on external storage, physically separate from the server running your VPS. A virus or ransomware inside the VPS cannot reach the backups, because they are created and managed at the hypervisor level, outside the VPS operating system.
• Database-consistent snapshots: Before each backup, an agent inside the VPS briefly freezes the filesystem so that the copy is consistent for MySQL or PostgreSQL databases, not just a raw disk image taken mid-write. If this mechanism is unavailable, the platform automatically falls back to an alternative backup method.
• Per-VPS encryption: Each backup is encrypted with a unique password for that specific VPS. The backup policy is set separately for each VPS.
• OrkestraVM platform security: Passwords are hashed with Argon2id. Every state-changing request is protected against CSRF attacks. Session cookies are set with the HttpOnly, Secure, and SameSite flags. Physical server access is exclusively through SSH, with no additional open ports. The platform was written from scratch, with no legacy code inherited from older control panels.
• Practical tip: A backup is only useful if you know it can be restored. If you run an active database on your VPS, test a restore in a staging environment at least once before you actually need it in production.

What Is Coming Next and Where to Find VPS Plans

OrkestraVM is under active development. In the near term, we are planning deeper integration with the MioriticHost client area, with more self-service actions available directly from your account. Further down the road, we have plans for automatic scaling and smarter distribution of VPS instances across physical servers for more efficient resource utilization.

One concrete advantage of owning the platform is that the team answering your support tickets is the same team that built and maintains OrkestraVM. There is no external vendor to wait on for a patch or a new feature. If we identify a problem or receive a reasonable request, we can act on it directly.

If you want to learn more about the technology behind the platform, visit orkestravm.com. If you are ready to choose a plan, all VPS options are listed at mioritichost.com/en/vps-servers.