Spend and abuse protection
In preview
A traffic spike or an attacker should not turn into a bill. What the panel buys or does on its own has a cap, an alert and one stop button.
Built and lab-tested
- A monthly spending limit over cloud servers, recorded volumes and balancers, and AI credits. Alerts at 50, 80 and 100 percent, and a daily report. At 100 percent the panel refuses anything that adds cost and never touches running sites.
- Under-attack mode per site: it starts by itself when requests jump to more than ten times the site's normal level for two minutes, or when errors flood in. It sets a strict rate limit per address and turns on the bot challenge, then reverts after a calm period. You can also switch it on or off by hand, and the previous settings are put back exactly.
- Autoscaling does not chase an attack: scale out is frozen while a site is under attack, and a scale group has its own budget and limit of servers added per hour.
- Bandwidth limits per account and per site: at 100 percent the site is slowed down, never billed. Hetzner traffic quotas are read, with notices at 80 and 100 percent.
- Abuse detection: known mining programs, unfamiliar programs that hold the CPU for ten minutes, and cron jobs that run over two hours. The policy is off, alert, throttle or suspend.
- Daily credit caps for the AI assistant, per account and per person.
- Emergency stop: one button or command (respirecloudctl protection emergency stop) pauses spending and puts every site in under-attack mode. Resume restores exactly the sites it changed.
Not there yet
- The Cloudflare under-attack setting does not follow the panel's attack mode yet.
- Provider traffic quotas are read only for Hetzner.
Every action in this area is in the panel, one keystroke away in the command palette (Ctrl K), on the command line and in the API, and most changes can be previewed as a plan first. Built and tested in our lab; RespireCloud is not released yet.