One command
Add Hetzner to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.
stack add hetzner
Or describe what you're building and let Claude pick it up via stack recommend:
stack recommend "raw cloud infrastructure for scale"Auth flow
Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.
How-to: Create an API token in Hetzner Cloud Console → Project → Security → API Tokens.
Secret slots
stack add hetzner writes these 1 secret
slot into your Phantom vault:
HETZNER_API_TOKEN
The values never leave Phantom in plaintext. Your .env file references slot
names, and stack exec -- <cmd> swaps them in at process-spawn time via
Phantom's local proxy.
Related providers in Cloud
- AWS — S3, Lambda, RDS. IAM access keys stored in Phantom.
- GCP — Google Cloud Platform. Service-account JSON + project ID stored in Phantom.
- DigitalOcean — Droplets, Kubernetes, managed databases. Personal access token verified via /v2/account.
FAQ
Do I need a Hetzner account to use it with Stack?
Yes — Stack provisions Hetzner on your behalf, but it authenticates as you. Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://console.hetzner.cloud and paste it once.
Where does Stack store my Hetzner credentials?
In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (HETZNER_API_TOKEN) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.
Can I rotate or revoke this integration later?
Yes. Run `stack remove hetzner` to pull the Hetzner service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Hetzner credentials in their dashboard — https://console.hetzner.cloud — and Stack's next `doctor --fix` will pick up the new values.