Introduction
Hetzner is one of the leading European hosting providers, offering dedicated servers, cloud VPS, and object storage at prices often 30–40% below the market average. However, infrastructure administration—even with ready-made panels—takes hours of routine: creating servers for each project, monitoring CPU and memory usage, setting up notifications when limits are exceeded, and scaling during peak loads. Integrating ASI Biont with Hetzner turns these processes into automated scenarios managed through dialogue with an AI agent.
Imagine: you type in the chat "create a server with 4 vCPU and 8 GB RAM on Ubuntu 22.04, open ports 80 and 443, add my SSH key"—and the AI does it in seconds, without manual login to the panel. Or "if the server load exceeds 80% for 10 minutes, create another replica and add it to the load balancer." All of this—without a single line of code from you.
How Does the AI Agent Connect to Hetzner?
ASI Biont uses a unique approach to integrations: instead of pre-installed modules or "add integration" buttons, the AI itself writes code for any service's API. To connect Hetzner, you only need to:
1. Go to the Hetzner Cloud control panel (https://console.hetzner.cloud).
2. Create an API token with read and write permissions (section "API Tokens").
3. Copy the token and send it to the ASI Biont AI agent chat.
After that, the AI analyzes the Hetzner API documentation (available at docs.hetzner.cloud) and creates a set of functions to interact with your servers. All logic—from authentication to error handling—is generated automatically. You don't write code, configure webhooks, or wait for updates from developers.
What Does the Integration Automate?
With the Hetzner API connected, the AI agent can perform over 20 different operations. Here are the key scenarios:
| Scenario | AI Action | Result |
|---|---|---|
| Server creation | Forms a POST request to /servers with server type, image, and key parameters |
Server ready in 30–60 seconds |
| Server deletion | Sends a DELETE request with the server ID | Resource release without manual search in the panel |
| Load monitoring | Periodically calls /servers/{id}/metrics and analyzes CPU, RAM, disk metrics |
Reports in chat and automatic actions when exceeded |
| Scaling | Creates an additional server and adds it to the load balancer | Horizontal scaling without engineer involvement |
| Notifications | Checks server status and sends a message to the chat | Alerts about overheating, service failure, or low free space |
Examples of Real Scenarios
Scenario 1: Automatic Deployment of a Test Environment
Suppose your developer asks to set up an environment for testing a new version of the application. Instead of logging into the Hetzner Console, selecting a configuration, waiting, and manually configuring the network, you type in the ASI Biont chat:
"Create a CX22 server on Ubuntu 24.04 with 40 GB SSD, install Docker, and clone the repository git@github.com:company/app.git"
The AI executes the sequence:
1. Creates a server via the Hetzner API.
2. Waits for the server to reach the "running" status.
3. Gets its IP address.
4. Connects via SSH and executes installation commands.
5. Reports the IP and readiness status.
Execution time: about 2 minutes. Manually—15–20 minutes including waiting.
Scenario 2: Monitoring and Notifications on Overload
You set up continuous monitoring:
"Check the CPU load on server web-01 every 5 minutes. If it exceeds 90% for three consecutive checks, create a new server with the same configuration and add it to the load balancer hetzner-lb-01"
The AI agent creates a background process that requests metrics via the Hetzner API every 5 minutes. When anomalies are detected, it automatically scales the infrastructure. You receive a notification in the chat:
"On server web-01 (IP: 116.203.x.x), CPU load reached 95%. Created server web-02 (IP: 116.203.x.y). Added to load balancer hetzner-lb-01"
Scenario 3: Saving on Unused Resources
If you have several projects or test environments, you can set up automatic server deletion:
"Every evening at 23:00, delete all servers with the tag 'dev' whose CPU load has been less than 5% over the last hour"
The AI checks metrics, identifies unused servers, and deletes them, saving money. According to Hetzner itself, the average user spends up to 20% of their budget on idle resources—such a scenario pays off within a week.
Why Is This Beneficial?
-
Time savings: automating server creation, deletion, and monitoring reduces routine operations time by 80–90%. If a DevOps engineer spends 2 hours a day managing servers, integration with ASI Biont frees up almost 40 hours per month.
-
Error reduction: manual server creation is prone to typos in configurations, forgotten SSH keys, or unopened ports. The AI acts strictly according to specified parameters and can double-check each step.
-
Flexibility without code: you are not limited to pre-installed templates. Want the server to reboot on a certain event and a notification to go to Telegram? Just describe the scenario in words—the AI implements it via the API.
-
Scalability: the integration works with any number of servers. You can manage both a single VPS and a cluster of 100 machines—the AI processes each request at the same speed.
Conclusion
The integration of ASI Biont with Hetzner is not just another connection of two services. It is an opportunity to turn an AI agent into a full-fledged DevOps assistant that understands your infrastructure and acts on your behalf. Server creation, monitoring, scaling, notifications—all of this is now done through a simple chat dialogue, without control panels and long scripts.
Try it yourself: go to asibiont.com, create an API token in Hetzner, and send it to the AI agent. You'll see how cloud management becomes a matter of a few words.
Comments