# How to Bill Hetzner Cloud Backups, Snapshots, Volumes and Setup Work

*Hetzner Cloud · Reseller billing · September 3, 2026 · 7 min read*

A Hetzner Cloud server is rarely the complete client service. Backups, snapshots, storage volumes and hands-on work have different lifecycles. A reseller should make them clear service items rather than hiding them inside a vague VPS package.

## Start with coverage, not the price

Hetzner backups and snapshots copy a server disk. They do not include attached volumes. Do not describe a server backup as a backup of all client data when a separate volume contains application data, databases or uploads.

## Backups: a recurring protection add-on

Hetzner Cloud backups are daily copies of the server disk. There are seven backup slots per server; when all slots are used, the oldest copy is removed as a new one is created. Backups are attached to one server and are deleted when that server is deleted.

For client billing, use a recurring item such as “Daily server backups, seven rotating restore points.” State the coverage accurately: server disk only, not permanent archive storage and not attached-volume protection.

## Snapshots: retained restore points need an offboarding rule

A snapshot is created manually and remains until it is deleted. It is not automatically updated or deleted, and can remain after the original server is removed. It can be useful for a migration fallback, an upgrade checkpoint or a temporary archive.

Set a client-facing rule for it: include retention for a defined period, sell it as a recurring add-on, or charge for it after a migration or cancellation date. At offboarding, explicitly delete it, hand it over, or continue retaining and billing it.

## Volumes: separate storage, separate coverage

Hetzner Volumes are separate network block-storage resources. They are billed hourly with a monthly cap, can be 10 GB to 10 TB, can grow but cannot be reduced, and one volume attaches to one server at a time.

Use a separate recurring storage item for each agreed capacity. Record the capacity and effective date. A server backup or snapshot does not include an attached volume, so agree and describe volume-data protection separately.

## Setup, migration and restore work

Initial setup, firewall work, migration, a manual restore, troubleshooting and special handover work are normally one-off services. A fixed setup fee works for standard onboarding; exceptional work can be added as a separate agreed charge.

| Client-facing item | Billing type | Important terms |
|---|---|---|
| Cloud server | Recurring | Service, plan, cycle, price, renewal date |
| Daily server backups | Recurring | Daily operation, seven slots, disk-only coverage |
| Retained snapshot | Recurring or time-limited | Retention and deletion/hand-over rule |
| Attached volume | Recurring | Capacity, effective date, backup responsibility |
| Setup, migration or manual restore | One-off | Scope, fee and completion date |

## A practical workflow

1. Create the base server service with the client’s recurring price.
2. Add backups, snapshots and volumes as separate services when agreed.
3. Add setup, migration and restore work as one-off charges.
4. Review residual snapshots and volumes before stopping an invoice at cancellation.
5. Keep service terms, client portal and invoice history aligned.

## Where BillOps fits

BillOps manages the client billing layer: recurring and one-off charges, per-client pricing, invoices, payments, reminders and the client portal. Hetzner remains the infrastructure provider and operational control plane. BillOps does not claim default native synchronization of Hetzner resources; integration work is reviewed and scoped separately.

Supplier references: [Hetzner Backups and Snapshots overview](https://docs.hetzner.com/cloud/servers/backups-snapshots/overview/), [Backup and Snapshot FAQ](https://docs.hetzner.com/cloud/servers/backups-snapshots/faq/) and [Volumes overview](https://docs.hetzner.com/cloud/volumes/overview/).

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