Hetzner Reseller Billing Software: How to Invoice Your Own VPS Clients

Hetzner is one of the most popular infrastructure providers for small server resellers in Europe. The pricing is competitive, the hardware is reliable, and the API is solid. But Hetzner's own tooling — Cloud Console, Robot panel — is built for you, not for your clients.

When you resell Hetzner VPS or dedicated servers, you have two separate billing relationships: Hetzner bills you, and you bill your clients. Hetzner's platform handles the first part perfectly. It does nothing for the second.

This guide is about closing that gap — setting up a billing layer between you and your clients, without overengineering it.

What Hetzner gives you (and what it doesn't)

Hetzner Cloud gives you a clean console: create servers, manage networks, view your own invoices. The Robot panel handles dedicated servers and root servers. Both are well-designed tools for infrastructure management.

What you won't find in either:

• A way to create and send invoices to your own clients
• A client portal where clients can see their services and pay
• Automatic renewal reminders for end clients
• Per-client pricing rules (you charge €45/mo for a server that costs you €29)
• VAT handling for B2B clients in different EU countries
• Any kind of payment integration (Stripe, bank transfer) on your end

Hetzner doesn't offer any of this because it's not their business. They sell infrastructure to you. Billing your clients is your problem to solve.

The spreadsheet problem — and when it breaks

Most small Hetzner resellers start the same way: a spreadsheet with client names, server specs, monthly prices, and renewal dates. It works at 5 clients. It still works at 15, with some discipline.

The problems start accumulating quietly:

• Renewal dates drift — a client renews late, you forget to update the sheet
• You invoice manually, one by one, each month — 30 clients means 30 manual invoices
• A client disputes a charge and you spend 20 minutes reconstructing the history
• You add a discount for one client and three months later can't remember what you agreed
• You have no record of which invoices were actually paid vs. just sent

What you actually need to bill Hetzner reseller clients

The core requirements for a Hetzner reseller billing setup are not complicated. You need:

1. Client records — company name, contact, billing address, VAT number
2. Service catalog — your server packages with your prices (not Hetzner's)
3. Recurring invoices — generated automatically each billing cycle
4. Payment collection — Stripe card payments or bank transfer with tracking
5. Client portal — a place clients can log in, view invoices, download PDFs
6. Renewal reminders — automated emails when a service is coming up for renewal
7. EU VAT handling — correct tax rates based on client country and VAT status

That's it. Everything else — advanced reporting, API integrations, reseller tiers — comes later, if ever.

Your options: WHMCS, self-built, or managed self-hosted

Option 1: WHMCS

WHMCS is the industry-standard billing platform for web hosting companies. It's feature-rich, battle-tested, and has a large ecosystem of plugins and integrations.

For a Hetzner VPS reseller, WHMCS has a few friction points worth knowing upfront:

• It's designed for shared hosting and domain resellers — the product catalog model assumes you're provisioning from a control panel (cPanel, Plesk). Bare metal servers or cloud VMs don't map cleanly to this model without custom work.
• Licensing starts at around €15–20/month for small installs, and goes up as you grow.
• Setup and configuration takes significant time. The interface is dense, and getting it to match your actual workflow requires either hours of your time or a WHMCS developer.

WHMCS is a good choice if you're planning to offer a large catalog of automated hosting products. For a reseller managing 30–120 server clients with custom pricing and manual provisioning, it's more system than you need.

Option 2: Build something yourself

Some technical resellers consider building a custom billing system. It's tempting — full control, exactly what you need, no license fees.

The real cost is ongoing maintenance. You're not building a billing system once; you're maintaining it forever. Every Stripe API change, every EU VAT rule update, every browser-side quirk in the client portal becomes your problem. Most resellers who go this route eventually replace their custom solution within 2–3 years.

Option 3: Managed self-hosted billing

A third option is a billing system that runs on your own server (or our infrastructure), deployed and maintained for you, and set up to match your specific Hetzner reseller workflow.

The key difference from WHMCS: you're not buying software and then configuring it yourself. The system is deployed and configured as part of a monthly service — with dev hours included for ongoing adjustments.

Criteria	WHMCS	Self-built	Managed self-hosted
Setup time	Days–weeks	Months	Days
Fits manual server billing	With workarounds	Yes, if built right	Yes, configured for it
Data stays yours	Self-hosted version	Yes	Yes
Ongoing maintenance	Yours to manage	Fully yours	Included
Monthly cost (30–80 clients)	€15–60+	Dev time	From €19–99
Custom client pricing	Yes	Yes	Yes
EU VAT handling	Yes	You build it	Yes

What "self-hosted" actually means — and what it doesn't

Self-hosted billing means the application runs on a server you (or we) control — not on a SaaS vendor's infrastructure. Your client data, invoice history, and payment records live in a database on that server. No vendor can lock you out, change their pricing, or shut down and take your data with them.

That's a real advantage for a billing system handling your clients' financial records. But it comes with a clear trade-off: the server it runs on is infrastructure, and infrastructure has operational responsibilities.

What stays your responsibility

When you run a self-hosted billing system, certain layers of the stack are outside the scope of the billing software itself:

• Server uptime. If the server goes down, the billing portal goes down with it. Monitoring and uptime are your (or your hosting provider's) concern.
• Backups. The billing system doesn't back itself up. You need a regular database backup strategy — daily snapshots, off-server storage.
• Mail delivery. Invoices and renewal reminders are sent via email. Transactional mail (SMTP setup, SPF/DKIM records, delivery monitoring) needs to be configured and working.
• Cron jobs. Recurring invoice generation, reminder scheduling, and subscription renewals run via scheduled tasks on the server. These need to be set up correctly and occasionally verified.

What BillOps covers

BillOps is not a server management service — it's a billing application service. Here's what's included:

• The billing application — deployed, configured for your workflow, and running
• Application updates — new features and compatibility updates applied without you touching the server
• Bug fixes — any issues with the billing logic, PDF generation, payment status, or client portal are fixed as part of the service
• Paid support — configuration changes, custom invoice templates, workflow adjustments, and integrations at an hourly rate (included hours depend on your plan)

The server layer — uptime, backups, SMTP — is either yours to manage, or something you can add on separately. On the Lite plan you handle this yourself. On Early and above, basic setup includes help getting mail and cron working correctly from the start.

What to actually look for in billing software for Hetzner resellers

When evaluating any billing system for your Hetzner reseller setup, prioritize these criteria:

Flexible product catalog. You need to define your own packages — "Hetzner CX22 resold at €18/mo", "Dedicated AX41 resold at €120/mo" — with your markup baked in. The system shouldn't assume Hetzner's pricing or force you into a shared hosting model.

Manual and auto invoicing. Some of your clients may be on fixed monthly billing; others may need custom invoices after configuration changes. You need both — automatic recurring invoices for standard services and the ability to issue one-off invoices for setup fees, migrations, or extra work.

Stripe and bank transfer support. European B2B clients still use bank transfers more than cards. You need both options, with payment confirmation tracking that works for SEPA transfers — not just automatic Stripe webhook callbacks.

Client portal with invoice history. Clients should be able to log in, see their active services, download PDF invoices, and track payment status without emailing you. This alone eliminates a big category of support requests.

Self-hosted or at minimum, data portability. For a billing system handling client financial data, vendor lock-in is a real risk. Prefer a system where you can export all data at any time, or better, where the system runs on infrastructure you control.

Getting started without overcomplicating it

If you have 20–80 Hetzner reseller clients and you're still invoicing manually, the practical path forward is:

1. Export your current client list and service details (even a rough CSV from your spreadsheet)
2. Pick a billing system that can import this or where setup is handled for you
3. Set up your Stripe account if you don't have one — EU resellers should have Stripe EU or Stripe Poland/DE/etc.
4. Configure your service catalog and pricing
5. Run one billing cycle manually through the new system while keeping the old one as backup
6. Migrate clients one cohort at a time

The migration itself doesn't have to be painful. Most clients won't notice the change — they just start receiving better-looking invoices and a portal login.

Why BillOps for Hetzner resellers

BillOps is a managed billing system built specifically for small hosting and cloud resellers — the kind who run 20 to 200 B2B clients on Hetzner, OVH, or their own hardware, and whose billing workflow doesn't fit neatly into WHMCS or generic SaaS invoicing tools.

The core idea: you get a self-hosted billing system on your infrastructure, deployed and configured for your workflow, with application updates and bug fixes included as part of the monthly service. You own the data and the installation. We handle the application layer.

Here's what makes it a practical fit for Hetzner resellers specifically:

• No shared hosting assumptions. The product catalog is built for manual server billing — fixed monthly prices, custom per-client rates, one-off charges for setup or config work. No cPanel provisioning modules required.
• Stripe and bank transfer out of the box. Both payment methods are first-class. SEPA bank transfers are tracked manually with confirmation support, not treated as an afterthought.
• Client portal included. Your clients get a login where they see active services, invoices, and payment status. Reduces "did you receive my payment?" emails to near zero.
• EU VAT handled correctly. B2B reverse charge, domestic VAT, VAT-exempt clients — configured for your country and client mix from day one.
• Your data stays yours. The system runs on a server you control. Full database export at any time, no vendor lock-in, no subscription that takes your data if you cancel.
• A developer on call, not a ticket queue. Dev hours are included in every paid plan. Small adjustments, custom invoice templates, workflow changes — handled without a separate project or quote.

If you're a Hetzner reseller currently invoicing manually or maintaining a spreadsheet that's starting to show cracks — this is the path out without overbuilding it.