Connect your accounts
GitHub, Hetzner, DigitalOcean (in testing), Cloudflare, Coolify and AI keys, with the exact permissions each key needs.
In the dashboard, open Integrations and add a key for each provider. Keys are encrypted as soon as you save them and are never shown again; to change one, replace it. Give each key the smallest access that works. These are the permissions airepeat uses today.
GitHubLink to this section: GitHub
A fine-grained personal access token for the account or organisation that will own your sites' repositories, with access to all repositories (new ones are created as you go):
| Permission | Why |
|---|---|
| Administration: read and write | Create, archive and unarchive repositories |
| Contents: read and write | Write site code and template files |
| Metadata: read | Required by GitHub for every token |
| Webhooks: read and write | Hear about pushes so deploys stay in sync |
Each workspace gets its own webhook address and secret, so pushes to your repositories are recognised as yours.
Hetzner CloudLink to this section: Hetzner Cloud
In the Hetzner Cloud console, open the project you want to use, then Security → API tokens and create a token with Read & Write access. Tokens are per project, so use a project just for airepeat if you run other servers.
DigitalOceanLink to this section: DigitalOcean
A personal access token with custom scopes:
| Scope | Why |
|---|---|
| droplet: create, read, update, delete | Create and manage your servers |
| ssh_key: create, read | Register your workspace's SSH key |
| regions, sizes, image: read | Show locations, sizes and prices |
| actions: read | Follow server creation |
CloudflareLink to this section: Cloudflare
An API token (not the global API key), limited to the zones you want to use:
| Permission | Why |
|---|---|
| Zone: Zone: Read | List your domains |
| Zone: DNS: Edit | Point records at your sites and services |
CoolifyLink to this section: Coolify
Launch your stack creates this token for you. To connect a Coolify you already run, enable the API under Settings and create a token under Keys & Tokens with read, write and deploy. Add read:sensitive only if you want deploy logs in airepeat.
AI model keysLink to this section: AI model keys
Add a key for each AI provider you want to use. Usage is billed to you by the provider, so set a monthly spending limit in its console. airepeat also lets you set a monthly AI budget per workspace.
- Built in: Anthropic's Claude, OpenAI and Google Gemini models.
- Added by name: DeepSeek, Kimi, OpenRouter and Ollama models. OpenRouter models must support tool use.
- Ollama runs models on a server you choose. Its address must be public: airepeat refuses private, loopback and link-local addresses.
Every model picker shows only the models whose provider you've set up.
Replacing a keyLink to this section: Replacing a key
Keys can't be read back, only replaced. If you think a key has leaked, revoke it at the provider first, then save the new one in airepeat. See Security and keys.