Billing Software for Hetzner Cloud and Robot Resellers

Hetzner Cloud and Robot help you operate infrastructure. A separate billing layer helps you sell that infrastructure to your own clients without running invoices, custom prices and renewals from a spreadsheet.

Many small European hosting resellers run both Hetzner Cloud and Robot. Cloud covers virtual servers and related cloud resources; Robot is the management environment associated with Hetzner’s dedicated-server workflow. Both are supplier tools: they show your resources and your relationship with Hetzner.

The moment you resell those services, you create a second relationship. Hetzner bills you for infrastructure. You need to bill your own client for the service, its agreed price, its renewal date and any support or setup work around it. These are different workflows and should not be forced into one panel.

Cloud and Robot are not client billing portals

Hetzner Cloud exposes cloud-server management and an API for programmatic cloud workflows. Robot exposes management and web-service functions for the dedicated-server side. They are useful for provisioning and operations, but neither is designed as a branded B2B billing portal for a reseller’s end customers.

A reseller still needs a place to manage:

• the client’s company and billing contact;
• the service sold to that client, rather than just the supplier resource;
• the resale price, custom discount and billing cycle;
• recurring and one-off invoices;
• payment status, bank-transfer confirmation and overdue follow-up;
• a client-facing history of services and invoice PDFs.

Manual provisioning is still a real reseller workflow

Not every reseller needs an automatic “customer pays, server appears” flow. You may review an order, select a location, configure a firewall, move a workload, add monitoring or combine a Cloud server with a Robot dedicated server. That is manual provisioning, and it can be the right service model.

The problem begins when manual provisioning is confused with manual billing. A service can be provisioned by a person while invoices, renewals, payment status and client access are handled consistently by a billing workflow.

What should be billed as a reseller service

The client does not necessarily buy “one Hetzner resource at supplier cost.” They buy your service package. That may include a server, a managed operating-system setup, backups, monitoring, migration work, a service-level commitment or a custom support arrangement.

For that reason, define your own service record and price. Do not rely on a supplier invoice to be the client’s invoice.

Do you need a full provisioning platform?

WHMCS and similar systems are capable hosting automation platforms. They make sense when you need domains, a large self-service catalogue, automatic provisioning modules and a wide hosting ecosystem.

For a small team manually reselling Cloud and Robot services, the decision is different. If the essential need is client records, custom pricing, recurring invoices, payments, reminders and a portal, a managed billing layer can be a better operational fit than deploying and maintaining a large provisioning stack.

How BillOps fits a Hetzner reseller

BillOps is a managed billing layer for the client side of this workflow. It lets you define the services you resell, set standard or per-client prices, create recurring and one-off charges, track payments and give clients a portal for invoices and services.

On Managed and higher plans, BillOps can assist with client import, service and payment setup, templates, updates, backups and small workflow changes. Standard plans run on managed EU infrastructure. You retain control of Hetzner provisioning and the relationship with Hetzner.

BillOps does not claim a default native Hetzner Cloud or Robot integration on this page. If supplier integration, automated synchronization or custom deployment is required, it should be reviewed and scoped separately.

A practical starting point

1. Export active clients and list the Cloud and Robot services you resell.
2. Define the client-facing name, billing cycle and price for each service.
3. Mark any custom discounts, setup fees or support commitments.
4. Set up payment methods and run one billing cycle in parallel with the existing process.
5. Give clients portal access once invoices and service records match the agreed terms.

You do not need to automate every supplier action before improving the commercial workflow. Start by making invoices, payments and renewals reliable; add integrations only where they solve a recurring operational problem.

For supplier documentation, see Hetzner’s Cloud API documentation and Robot Webservice documentation.