We use analytics cookies and anonymised session recordings to improve the product. Do you accept?

Hetzner Coverage

Inventory and cost visibility for Hetzner Cloud Servers, volumes, Object Storage, Load Balancers, Primary IPs, Firewalls, Networks and Robot dedicated servers.

2 min read

How it works

Inventory and cost estimation run today; metrics-based optimization is on the roadmap. Dedicated costs are catalog estimates — the Robot Webservice exposes no invoice API.

Inventory
Discovers and syncs resources from your Hetzner Cloud project (and Robot account) into the database, on a schedule or on-demand.
Cost estimation
Prices Servers, volumes, Load Balancers and Primary IPs from Hetzner's /pricing endpoint, and dedicated servers from the Robot order catalog — a real monthly cost estimate for every resource.
Optimization
Flags stopped servers still being billed, unattached volumes, idle Load Balancers and unassigned Primary IPs. Firewalls and Networks are free — inventoried for completeness and hygiene.

Coverage by service

One card per service. Each card lists its resource types and the capabilities they support.

Inventory Metrics Optimization Drift detection
Network
4 resource types
  • Firewalls
  • Networks
  • Primary IPs
  • Load Balancers
Compute
2 resource types
  • Cloud Servers
  • Dedicated Servers
Storage
2 resource types
  • Volumes
  • Object Storage

API token

Covers Servers, volumes, Load Balancers, Primary IPs, Firewalls and Networks.

  1. In the Hetzner Cloud Console, go to Security → API Tokens and generate a new token with read-only permissions — nothing this app does ever needs write access.

  2. Cloud API tokens are project-scoped: if you have several projects, generate one token for each and add them as separate cloud accounts.

  3. Go to Organization → Integrations → Cloud Accounts → Add Account, pick Hetzner, paste the token and select the locations to monitor.

Object Storage credentials (optional)

S3-compatible, generated independently of the API token above.

  1. In the Hetzner Cloud Console, go to Security → S3 keys and generate a new key pair.

  2. Add them to the same cloud account under S3 Access Key / S3 Secret Key. Buckets are discovered at every Object Storage location (fsn1, nbg1, hel1, ash) automatically.

Robot — Dedicated Servers (optional)

Bare-metal servers, via the Robot Webservice (separate user).

  1. In Hetzner Robot, go to Settings → Web service and app settings and create a new webservice user.

  2. Add the user and password to the same cloud account under Robot Webservice User / Robot Webservice Password — dedicated servers appear under Audit → Hetzner → Compute → Dedicated, priced from the Robot order catalog when the product is still orderable.

  3. Note: the Robot Webservice exposes no invoice API — dedicated costs are catalog-based estimates, not imported invoices.

First sync

Once the account is saved, inventory runs on the next hourly cycle — or trigger it immediately from the account's detail page. Discovered Servers, volumes, buckets and networking appear under Audit → Hetzner.