VMgenie capability scenarios

Three reference deployments of the VMgenie control panel. Each scenario names the panel features it exercises and the configuration it produces, so you can compare the scenario that matches your environment to your own. Customer names are illustrative; the configuration is what the panel actually produces. If you want to talk to an operator running VMgenie in production, the contact page reaches the team.

Showing all 3 scenarios.

Hosting scenario — reseller panel across multiple physical servers

Scenario: Hosting

What the panel produces

A single VMgenie Pro panel enrolled against a pool of physical servers. Each reseller account in the panel sees only the VMs and IPv6 blocks it owns; per-account limits in the panel's users / limits screen cap how many VMs and dedicated servers each account can create. The panel keeps VM placement distributed across hosts so no single server fills while another sits idle.

Reseller accounts provision their own VMs through the same panel — a deliberate decision to keep your support queue small and to give end users a direct view of what they are using.

Multi-hostphysical-server pool
Per-account VM and server caps
Per-account IPv6 block scoping
DistributedVM placement

Relevant panel screens

The users / limits screen in the panel sets the per-account caps; the physical-servers list and VMs list show what each host and each reseller is currently using.

Software scenario — self-hosted panel on company hardware

Scenario: Software

What the panel produces

A self-hosted VMgenie Business installation running on the company's own rack servers in a single colocation cage. Each server pins a fixed template pool so the right OS templates are present on the right host; the panel delegates the data centre's IPv6 /48 into /64s, one VM at a time, from the panel's networking view.

Engineers provision their own development VMs through the panel. Named accounts match each engineering team's allowed quotas, and the VMs list view in the dashboard shows usage per project without anyone hand-rolling reports.

Self-hostedBusiness installation
Per-servertemplate pools
/48 → /64IPv6 delegation
Per-projectVM quotas

Relevant panel screens

The templates settings screen pins the pool per server; the IPv6 settings screen splits the /48 and assigns blocks to VMs.

IT-consulting scenario — migrating VMs without re-IPing guests

Scenario: IT consulting

What the panel produces

A consultant runs VM workloads for several small-business clients under one VMgenie Pro panel. Migrating ten customer VMs between physical servers is done by changing which host they live on — no guest-side reconfiguration. Because the IPv4 default gateway 169.254.1.1 and the IPv6 block assignments are the same on every server, every VM keeps its original public addresses.

Each small-business customer gets a reseller account in the panel so they only see their own VMs and IPv6 block, even though everything is on the same panel.

LiveVM migration between hosts
169.254.1.1universal IPv4 gateway
No guest-sideIP changes
Per-customerreseller scoping

Relevant panel screens

The VMs list drives the migration; the IPv6 settings and users / limits screens split the new hardware's /48 and keep each customer's view scoped.

Want to see how a deployment like this would look on your hardware? The Get Started page walks through launching a hosted panel or enrolling a self-hosted one, and the requirements page lists what a physical server needs before the agent will enrol. For a worked example of POST /api/v1/vms end-to-end, the quickstart is the shortest path through.