gibil auth
Manage authentication and API tokens
Configure your provider token (Hetzner or Vultr) and optional Gibil API key. A provider token is required for VM operations; the Gibil platform account is optional. For new setups, prefer gibil init — it picks a provider, validates the token, and saves it under providers.<name> in ~/.gibil/config.json.
Usage
gibil auth <subcommand>Subcommands
gibil auth setup --token <token>
Save a provider API token locally. Defaults to Hetzner; pass --provider to target Vultr (or use gibil init --provider <name> --token <token>).
gibil auth setup --token hc_xxxxxxxxxxxx
# ✓ Hetzner token saved to ~/.gibil/config.json
gibil auth setup --provider vultr --token V1AB2C...
# ✓ Vultr token saved to ~/.gibil/config.jsongibil auth login --key <key>
Log in with a Gibil API key (for paid plans with metering).
gibil auth login --key pk_live_xxxxx
# ✓ Logged in as alex@example.com (dev plan)gibil auth status
Check current authentication status.
gibil auth statusgibil auth logout
Remove stored credentials.
gibil auth logoutThe Gibil platform account is optional. Without a Gibil API key, the CLI works the same — you just provide your own provider token (Hetzner or Vultr) and pay the cloud directly.
Next steps
- Quick Start — forge your first server
- Provider Setup — get an API token
- gibil usage — check plan limits