Hetzner Cloud Provisioning in WHMCS: The Auto-Sync Setup Guide

Hetzner Cloud has quietly become one of the most price-competitive cloud providers in the world. A 4 vCPU / 8 GB RAM Helsinki instance runs at €5.83/month with native IPv6, a free 7-day backup tier, and an honest hourly billing model. If you sell hosting through WHMCS, reselling Hetzner Cloud is one of the highest-margin moves you can make in 2026 - but only if you wire the integration up correctly.

This guide walks through the full setup: API token, product mapping, auto-sync rules, and the client-area features your customers will actually use.

Why Hetzner Cloud is a smart resell

Three structural advantages make Hetzner Cloud uniquely good for reselling:

• Wholesale prices are aggressive. A Hetzner CX22 (2 vCPU, 4 GB, 40 GB SSD) costs you €3.85/month. Customers will happily pay $8–10 for the same spec branded under your hosting company.
• Honest hourly billing. Hetzner bills by the hour, capped at the monthly price. Your customers get the same flexibility - no surprise overage charges, no commitment lock-in.
• Six regions, more coming. Falkenstein, Nuremberg, Helsinki, Ashburn, Hillsboro, Singapore. Your customers pick their region at checkout and you get global coverage for free.

Step 1 - Create a Hetzner Cloud project + API token

Sign in to your Hetzner Cloud Console and create a project dedicated to reselling (don't mix it with your internal infrastructure). Under Security → API Tokens, generate a new token with Read & Write scope. Copy it - Hetzner only shows the token once.

The token is the single piece of credential your WHMCS install needs. There is no separate API user or shared secret. Hetzner uses bearer-token auth over plain HTTPS, with rate limits at 3,600 requests per hour per token (more than enough for any sensible WHMCS workload).

Step 2 - Install the provisioning module

Drop the module folder into /modules/servers/hetznercloud/ and visit System Settings → Products/Services → Servers. Add a new server, choose Hetzner Cloud as the type, paste the API token, click Test Connection. You should see a green check and the list of regions your token can reach.

Step 3 - Map server types to products

This is where most setups get the design choice wrong. You have two options:

Option A - One WHMCS product per Hetzner plan. CX22 becomes "Starter Cloud", CX32 becomes "Pro Cloud", and so on. Easier to market, but you have to keep your prices in sync manually if Hetzner adjusts their catalogue.

Option B - One product, customer-picks-the-plan. A single "Hetzner Cloud" product with a configurable option that lists every server type. You set a percentage markup (e.g. +35%) once and your prices auto-track Hetzner's catalogue forever.

Option B scales better. Hetzner adjusted their pricing twice in 2025; resellers on Option B had updated prices live within an hour of the catalogue change. Resellers on Option A spent hours hand-editing dozens of products.

Step 4 - Expose the right client-area features

The default WHMCS client area is basic. To compete with Hetzner Cloud's own console, you want at minimum:

• Power controls (start, stop, reboot, hard-reset)
• VNC / web console access
• Snapshot create / restore / delete
• Native Hetzner backup toggle (their 7-day rolling backup, billed at +20%)
• Reverse DNS editing for IPv4 and IPv6
• Bandwidth and CPU usage graphs

Advanced features that unlock enterprise customers:

• Private network creation + subnet management
• Firewall rules editor
• Volume attach / detach / resize
• Floating IP assignment

If you can give customers parity with Hetzner Cloud's own UI, they have no reason to bypass you and buy direct.

Step 5 - Set up the upgrade flow

Customers will eventually outgrow their plan. Hetzner supports live resizing (CPU/RAM and disk, with a brief reboot). Your WHMCS integration should:

1. Show the customer an "Upgrade" button with the next-tier option pre-selected
2. Generate a prorated invoice for the remainder of the billing period at the new rate
3. Collect payment
4. Call the Hetzner API to resize the instance
5. Notify the customer when the reboot is complete

This is the "auto price switch" feature that separates a good integration from a frustrating one. Doing this by hand for every upgrade is the single most common reason small VPS resellers stop scaling.

Step 6 - Monitor your wholesale costs

Hetzner doesn't bill you per-customer - they bill you for total project resource usage. As your customer base grows, build a simple sanity check that compares your total WHMCS recurring revenue against your monthly Hetzner invoice. The healthy ratio is roughly 1.4× to 1.7× - your revenue should be at least 40% above wholesale cost to cover support, payment processing, taxes and your time.

If you drop below 1.3×, either your markup is too low or one of your customers is doing something unusual (running spot workloads that hammer CPU, for example, which can trip Hetzner's fair-use throttling). Catch this early and either reprice or migrate that customer to a dedicated plan.

Common pitfalls

Forgetting reverse DNS. Customer-set rDNS is critical for mail deliverability. If you don't expose it, every customer running a mail server complains within a week.

Hard-coding regions. Hetzner adds regions occasionally. Your integration should pull the region list from the API, not from a static config file. Singapore launched in 2024; many old integrations still don't show it.

Not handling out-of-inventory. Some regions occasionally run out of a specific server type. If the customer orders during such a window, the API returns a clear error. Make sure your WHMCS surface translates that to a friendly "try a different region or plan" message instead of a generic 500.

Wrap-up

Hetzner Cloud is one of the few wholesale providers in 2026 where the unit economics genuinely work for small VPS resellers. The integration is straightforward, the API is honest, and customer self-service through WHMCS is achievable in days, not months.

If you want to skip the build phase entirely and start selling this week, our Hetzner Cloud Module ships with everything in this guide pre-wired - auto-sync, prorated upgrades, full client-area feature parity. Paste your API token and you're done.