Hetzner

A Hetzner API token belongs to exactly one project and sees nothing outside it. An account with three projects therefore becomes three integrations in Provibr, each with its own token and its own request budget.

One field, and that is the whole credential. Create it in the Hetzner Cloud Console under Security → API tokens, inside the project you want Provibr to manage.

• Choose Read & Write. A read-only token connects fine and the connection test goes green, because that test only reads; it fails at the first button that changes something.
• A read-write token is all or nothing: no scopes, no expiry date, no IP restriction. Whoever holds it can delete every server in that project.
• Paste the token exactly as shown. A token with a stray space is refused, and Hetzner reports that the same way as a wrong token.

Provibr ignores every server it has not been told about, so a fresh integration shows an empty list. Open the integration, run the import, and tick the servers you want in the panel.

Start, stop, a graceful shutdown, removal and a rebuild onto another image. Removal really removes: the machine is gone and the billing stops. A rebuild keeps both the IPv4 address and the IPv6 block.

Hetzner bills a server for as long as it exists, whether it runs or not. Powering one off therefore costs your customer exactly the same and gains them nothing, so Provibr does not offer it and the licence enforcement will not do it either.

Volumes, firewalls and primary IPs are separate objects at Hetzner, with their own lifetime and their own price. That is why there is no hardware tab, no firewall rules and no address assignment here. There is no pause either: Hetzner has no suspend of its own, so a machine that goes over your capacity is powered off instead.