Hetzner Integration
Hetzner Cloud support in Devpilot is coming soon. This page describes what the integration will offer at launch.
Hetzner Integration
Coming soon. Hetzner Cloud appears on the Devpilot Integrations page as a planned provider. You cannot currently connect a Hetzner API token or provision Hetzner Cloud servers from Devpilot. If you already run servers on Hetzner today, add them via Connect an Existing Server in the meantime.
When the Hetzner integration becomes available, it will connect a Hetzner Cloud project to your Devpilot workspace using an API token. Once connected, Devpilot will provision Hetzner Cloud servers, install the Devpilot agent on them, and manage their lifecycle.
Prerequisites (at launch)
- A Hetzner Cloud project with billing enabled
- An active Devpilot workspace
Required Credentials
Devpilot stores the following fields for a Hetzner integration:
| Field | Description |
|---|---|
| Access Key | A descriptive label for the token (used as the integration's display key). |
| Secret Key | A Hetzner Cloud API token with read and write permission for the project. |
Hetzner Cloud uses a single API token to authenticate calls. Devpilot keeps a two-field form for consistency — the Secret Key field holds your token, and Access Key acts as a label.
Creating a Hetzner Cloud API Token
Open the Hetzner Cloud Console
Sign in to Hetzner Cloud and open the project you want Devpilot to use.
Generate an API Token
Navigate to Security > API tokens > Generate API Token. Enter a description such as devpilot-integration, select Read and Write permission, and create the token.
Copy the Token
Copy the token value immediately — Hetzner displays it only once.
Connect Hetzner in Devpilot
Go to Workspace Settings > Integrations and select Connect on the Hetzner card. Enter a label in the Access Key field and paste the API token into the Secret Key field.
Validate and Save
Devpilot validates the token against the Hetzner Cloud API before saving. If validation fails, confirm the token was created with read and write access.
What Devpilot Does on Hetzner
When you provision a server, Devpilot:
- Creates a Hetzner Cloud server in the chosen location and server type
- Adds an SSH key to the server
- Configures firewall rules for the ports the deployment requires
- Tags the server with Devpilot workspace metadata
- Installs the Devpilot agent
Hetzner API tokens are scoped to a single project. If you need Devpilot to provision across multiple Hetzner projects, add a separate integration for each project.
Testing and Rotating Credentials
Open the integration and select Test Credentials to re-run validation. To rotate, generate a new token in Hetzner, update the Secret Key in Devpilot, and delete the old token from Security > API tokens.
Troubleshooting
Credential Validation Fails
- Confirm the token still exists in the Hetzner project's Security > API tokens page.
- Verify it has Read and Write permission — read-only tokens cannot create servers.
Server Provisioning Fails
- Check your project's server limit and consumed resources on the Hetzner project dashboard.
- Some server types and locations occasionally sell out — try a different location or a different server type.
Disconnecting Hetzner
Open the Hetzner integration and select Remove. Stored credentials are deleted from Devpilot. Hetzner servers already provisioned through Devpilot remain in your project — manage them from the Hetzner Cloud Console if you no longer need them.