How it works
Your accounts. Your servers. One control panel.
airepeat doesn't host your sites. It connects to the accounts you already have, sets up Coolify on a server you own, and runs everything from there. You pay your providers directly, and keep everything if you leave.
Architecture
Four parts, three of them yours
airepeat holds your keys in an encrypted vault and sends approved operations to the providers and to Coolify on your server.
1 · Yours
Your accounts
- GitHubOne repository per site
- Hetzneror DigitalOcean in testingServers, billed to you
- CloudflareDNS for your domains
- AI model keyClaude; others in testing
2 · Control panel
airepeat
- DashboardPlan, review, launch
- Key vaultAES-256-GCM
- ApprovalsSpending and deletions
- WorkerOperations, backups, checks
3 · Yours
Your server
- CoolifyOpen source; builds and runs containers
- Proxy and HTTPSCertificates for every address
4 · Yours
Your sites and services
- Sites and appsFrom your repositories
- DatabasesPostgres, MySQL, Redis and more
- Services352 open-source, one click each
Step by step
From sign-up to a site that stays up
- 01
Sign up
Create an account and confirm your email. During the beta, new workspaces are approved by hand.
Two-factor sign-in available
- 02
Connect your accounts
Add keys for GitHub, your server provider, Cloudflare and an AI provider. They go into the encrypted vault and are never shown again.
AES-256-GCM
- 03
Launch your stack
Choose a provider, region and size, and approve the provider's price. airepeat creates the server, installs Coolify and connects it. Hetzner today; DigitalOcean in testing
coolify.your-domain
- 04
Create a site or service
Describe a site to the AI planner, start from a template, import a GitHub repository, or pick one of 352 open-source services.
- 05
Review and approve
Check the private preview. A release binds your review to the exact commit, and a site's first public launch waits for an owner.
Owner review
- 06
Keep it running
Deploys, backups, monitoring, alerts and automations run on their own. Every change is in the audit log.
Guarantees in the code
What airepeat never does
These are rules the platform enforces, not settings you have to find.
Never: Spend your money without a yes
Servers, domains and other paid actions wait for an owner's approval of the exact resource and price.
Never: Show a stored key again
Keys are encrypted when you save them and never displayed again, to anyone. The audit log records names, not values.
Never: Put AI changes live unreviewed
AI work becomes a release that someone reviews. A site's first public launch always needs an owner.
Never: Delete in one step
Sites are archived with a backup first. Purging waits 7 days and needs verified backups and its own approval.
Never: Change DNS quietly
Every record change is shown as a plan and approved. Existing records are never overwritten silently.
Never: Keep your work hostage
Code is in your GitHub, servers in your provider account, DNS in your Cloudflare. Leave, and it all stays yours.
Costs
Who pays for what
There is no markup on your providers: they bill you directly.
| What | Paid to | How |
|---|---|---|
| airepeat | Free during the beta | Bring-your-own stays free while it's in beta. We'll give plenty of notice before any change. |
| Servers | Your Hetzner account (DigitalOcean in testing) | Billed by the provider at their prices. airepeat shows the price before you approve a new server. |
| Domains | Your registrar | Yearly price from the registrar, approved exactly before any purchase or renewal. Buying through airepeat is in testing. |
| DNS | Your Cloudflare account | Your Cloudflare plan. airepeat adds and changes records through its API. |
| Code | Your GitHub account | One repository per site, created in your account or organisation. |
| AI usage | Your AI provider | Billed per use by the provider of the model you pick, within your cost limits. A local Ollama model costs nothing per call. |
Prefer not to run servers? Managed hosting is coming soon. See pricing and the docs for the exact permissions each key needs.
Run your next site on servers you own
Free during the beta. Bring your own keys and pay your providers directly.
New accounts are approved by hand during the beta.