# Billing Software for Hetzner Cloud and Robot Resellers

*Hetzner · Billing workflow · September 3, 2026 · 8 min read*

Hetzner Cloud and Robot help a reseller operate infrastructure. A separate billing layer helps the reseller sell that infrastructure to clients with custom prices, recurring invoices, payment tracking and renewals.

## Cloud and Robot are supplier-management tools

Cloud manages cloud-server resources and Cloud API workflows. Robot covers the dedicated-server management workflow. Both concern the reseller’s relationship with Hetzner. They are not a branded B2B billing portal for the reseller’s own clients.

When a reseller sells those services, two relationships exist:

1. Hetzner bills the reseller for infrastructure.
2. The reseller bills its client for the agreed service.

The client-side workflow needs client records, service terms, custom prices, recurring and one-off invoices, payment confirmation, overdue follow-up and invoice history.

## Manual provisioning does not require manual billing

Manual provisioning can be the correct model when a reseller reviews an order, chooses a location, configures security, performs migration work or combines cloud and dedicated resources. The reseller can provision manually while invoices, payment status, renewals and client access are handled consistently in a billing workflow.

## Bill the client-facing service, not the supplier invoice

The client buys the reseller’s package, which may include infrastructure plus setup, monitoring, backups, migration or support. Define a client-facing service with its own price, billing cycle, discount and renewal date. A supplier invoice should not become the client’s invoice.

## Do you need a full automation platform?

WHMCS and similar platforms are appropriate when a business needs domains, a large self-service catalogue and automated provisioning modules. A small team manually reselling Hetzner Cloud and Robot services may instead need a narrower managed billing layer: client records, custom pricing, recurring invoices, payments, reminders and a portal.

## How BillOps fits

BillOps manages the client-side billing workflow: services, standard and per-client prices, recurring and one-off charges, payments, renewals and the client portal. Standard plans run on managed EU infrastructure. On Managed and higher plans, BillOps can assist with client import, service and payment setup, templates, updates, backups and small workflow changes.

BillOps does not claim a default native Hetzner Cloud or Robot integration here. Supplier integration, automated synchronization and custom deployment are separately reviewed and scoped.

## A practical start

1. Export active clients and list Cloud and Robot services you resell.
2. Define the client-facing service name, cycle and price.
3. Record custom discounts, setup fees and support commitments.
4. Configure payment methods and run one billing cycle in parallel.
5. Give clients portal access when the service and invoice records are correct.

You can improve billing without automating every supplier action. Start with reliable invoices, payments and renewals; add integrations where they solve a repeatable operational problem.

Official supplier references: [Hetzner Cloud API documentation](https://docs.hetzner.com/cloud/api/getting-started/generating-api-token/) and [Robot Webservice documentation](https://robot.hetzner.com/doc/webservice/en.html).

[See BillOps pricing](/#pricing) or [book a 30-minute demo](mailto:info@billops.app).