OpenHosting includes 27 server-provisioning integrations. Enable one under Admin → Extensions, then attach it to a product (product edit page → Server extension) and fill in the per-product settings. On payment the module creates the server; the billing lifecycle then suspends, unsuspends and terminates it automatically.
Config options with env keys (e.g. MEMORY, CORES, DISK, DOMAIN) let
customers pick sizes at checkout — see Products → config options.
Panel URL + application API key. Per-product egg, nest, location and resource limits. Config options map to egg variables.
The Pterodactyl successor fork; API-compatible, same configuration.
Hosted Pterodactyl fork for game hosts; API-compatible.
Game-server panel. TCAdmin URL + API key; per-product package, game and slots.
API URL + API token. Per-product node, guest type (QEMU template clone or LXC),
storage and resources. Customer overrides via CORES/MEMORY/DISK options.
Master URL + API key/hash. Per-product virtualization type, node group, plan and template.
Panel URL + application API key; per-product node, template and resource limits.
Panel URL + API token; per-product package, hypervisor group and OS template.
Panel URL + admin API key/pass; per-product virtualization type, node, plan and OS.
API token; per-product server type, image and location. Suspend = power off.
API token; per-product droplet size, image and region.
API key; per-product plan, OS and region.
API token; per-product instance type, image and region.
Keystone auth URL + credentials + project; per-product flavor, image and network. Suspend/resume via Nova server actions.
OpenStack-compatible Hybrid Infrastructure. Same shape as OpenStack.
Control panel URL + API user email + key; per-product template, hypervisor group and resources.
vCloud URL + org credentials; per-product vDC, vApp template and network.
WHM URL + username + API token; per-product package. Add a DOMAIN config
option for the customer's domain.
Panel URL + admin username + login key; per-product package and IP.
Plesk URL + API key (or admin credentials); per-product service plan and IP.
API URL + org ID + access token; per-product plan.
Panel URL + access/secret keys (or admin credentials); per-product package.
Panel URL + admin credentials; per-product package and PHP version.
Server URL + API key; per-product package and server IP.
NodeWorx URL + API key; per-product SiteWorx plan and IP.
Panel URL + remote API credentials; per-product server ID and IP.
Webmin URL + credentials; per-product plan, template and feature set. Add a
DOMAIN config option.
Every server module implements four hooks the billing engine calls:
create, suspend, unsuspend, terminate. Provisioning failures are
recorded in the audit log without blocking billing. Add your own in ~130 lines —
see Writing an extension.
Note: the driver implementations follow each vendor's documented API. As with any provisioning integration, validate against your actual panel version in staging before relying on it in production.