Guide
The agent is a small container that runs on your own server and handles the clicks on your links. It takes the request, decides whether this is a live person and sends them where intended; where exactly a given code leads it asks the platform. Because of that your traffic leaves from your own IP address rather than a shared one: the reputation is yours and never depends on other users.
It installs on a clean Ubuntu VPS — we recommend Contabo, because their VPS come with clean IP addresses, and that matters here: with some providers the IP arrives already listed in blacklists. In the Settings section you get the access key and a ready-made config, plus a PDF instruction in three languages: a few commands install Docker, pull the agent archive and bring the container up. You can paste those commands even into your host's web console, with no SSH client. Once it starts, the agent sends a heartbeat — and the cabinet sees its origin IP and shows the connection as active on its own. One-line automatic installation is already in the works.
A few things worth knowing. The order of steps is strict: the agent first, then the domain, then the Cloudflare shield — the origin IP for the shield is taken from the agent's heartbeat, not from anything typed by hand. You do not need to keep the access key yourself: the cabinet already shows it masked — you can see that a key exists, but not the key itself. The full value is only needed at install time; after that it lives in the .env file on your server. If you rotate it, the agent must receive the new value: with a manual install you put it into .env and restart the container, otherwise the platform answers the agent with 401 — and when the platform installs the agent, the new key is written in for you. One account works with one agent: several VPS per account are not supported yet. When we update the agent, the cabinet shows a banner with the "installed / current" versions and the update command.