Quick start
Install the InfraFence agent on a Linux server with one command and a single-use install token, and see the server in the dashboard within a minute.
Last updated:
You need a Linux server on x86-64 or ARM64, root access, and an InfraFence account. A new account starts with 14 days of AutoMode free, with no card; then Starter, free for one server, unless you choose a plan. Sign up with a permanent email address: temporary (disposable) inboxes cannot create an account.
1. Create an install token
In the dashboard, open Servers and choose Add server, then Generate the token and see the code. Only owners and admins of the organization can create tokens.
The token starts with IF-. It is single-use and valid for one hour: if nobody uses it within the hour it expires, and you generate a new one. Tokens you created are listed under Settings › Install tokens, where you can also revoke one.
2. Run the install command
On the server, as root:
curl -fsSL https://github.com/infrafence/infrafence-agent/releases/latest/download/install.sh | sudo bash -s -- --token <YOUR_TOKEN>The installer first checks the server read-only, then downloads the agent, installs it as a service and registers it with your token. What the installer does lists every step.
Prefer to see the plan before anything changes? Add --dry-run: the installer downloads the agent, runs the read-only check, prints what a real run would do and changes nothing. It needs no token.
curl -fsSL https://github.com/infrafence/infrafence-agent/releases/latest/download/install.sh | sudo bash -s -- --dry-run3. Wait for the first check-in
The Add server page shows Waiting for agent to check in… and then Agent connected. The agent reports to the dashboard every 60 seconds, so the server appears within a minute.
On the server you can check the service:
systemctl status infrafence-agent
journalctl -u infrafence-agent -fBefore you use AutoMode or approve fixes: turn on two-factor authentication. Approving or rejecting what AutoMode asks, and applying a risky fix yourself, need an owner or admin of the organization signed in with two-factor authentication. Without it nobody can approve: the requests wait on Approvals and expire after 24 hours. While an owner or admin has no 2FA, the security score of every server also loses 5 points. Turn it on under Settings › Security: it takes a minute.
Next
- First steps in the dashboard: what to look at and what to set first.
- Want to watch before blocking? Turn on monitor mode: InfraFence then detects everything and blocks nothing. See Configuration.
