The TigerTrust Agent is the only thing you install on a host to bring it under CLM management. It never listens on any port; it dials out to the Collector on 443 and pulls work.
This page mirrors the Agent Setup wizard in the dashboard (/clm/agent-setup). Copy commands from either side — they’re identical.

Prerequisites

RequirementValue
Agent API KeyCreate one in Settings → API Keys → New key with type agent. Shown once.
Collector URLhttps://collector.tigertrust.io (or your self-hosted Collector)
Supported OSDebian/Ubuntu · RHEL/CentOS · Windows Server 2016+ · macOS 12+
Userroot or a service account that owns the paths you plan to manage

Quick install (one script, any Linux)

1

Run the installer

curl -fsSL https://releases.tigertrust.io/tigertrust-agent/scripts/install.sh | sudo bash -s -- \
  --collector-url https://collector.tigertrust.io \
  --api-key YOUR_API_KEY
The script detects your distro, adds the right package repo, installs tigertrust-agent, writes /etc/tigertrust-agent/config.yaml, and enables the systemd service.
2

Verify

sudo systemctl status tigertrust-agent
The host appears in Infrastructure → Agents within 30 seconds of first heartbeat.

Installation methods

Choose the flow that matches your platform. All flows land on the same tigertrust-agent binary and /etc/tigertrust-agent/config.yaml.
1

Add the TigerTrust repository

curl -fsSL https://releases.tigertrust.io/tigertrust-agent/latest/gpg.key \
  | sudo gpg --dearmor -o /usr/share/keyrings/tigertrust-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/tigertrust-archive-keyring.gpg] https://releases.tigertrust.io/tigertrust-agent/latest/apt stable main" \
  | sudo tee /etc/apt/sources.list.d/tigertrust.list
2

Update package list and install

sudo apt update && sudo apt install -y tigertrust-agent
3

Configure the agent

sudo tigertrust-agent configure \
  --collector-url https://collector.tigertrust.io \
  --api-key YOUR_API_KEY
4

Start the service

sudo systemctl enable --now tigertrust-agent

Verify the install

Check service status

sudo systemctl status tigertrust-agent

Tail agent logs

sudo journalctl -u tigertrust-agent -f
Once connected, the host appears in Infrastructure → Agents within a few seconds and starts discovering certificates automatically.

The install.sh script

Every distro-specific flow above is what the single install.sh runs internally. It’s fetched from https://releases.tigertrust.io/tigertrust-agent/scripts/install.sh and:
  1. Detects the platform (/etc/os-release, uname -m).
  2. On Debian/Ubuntu, imports the GPG key and adds the apt source; on RHEL/CentOS, drops the .repo file.
  3. Installs the tigertrust-agent package.
  4. Runs tigertrust-agent configure with the flags you passed on the curl line.
  5. Enables and starts the systemd service.
Supported flags:
--collector-url <url>     (required)
--api-key <key>           (required)
--agent-name <name>       optional; defaults to hostname
--config <path>           optional; use a pre-written config file
--channel <stable|beta>   optional; default: stable

Capabilities

Agents advertise what they support. A discovery-only agent claims different capabilities than a data-center agent that also deploys certs. Edit /etc/tigertrust-agent/config.yaml and restart:
agent:
  capabilities:
    - fs-scan
    - cert-renewal
    - csr-generation
    - cert-deploy
    - network-scan
    - ssh-scan
The control plane only schedules tasks the agent claims to support, so a stripped-down IoT agent (discovery + renewal only) can coexist with full-featured hosts in the same workspace.

Agents and Collector

The pull-based architecture, task types, and enrollment flow.

Discovery

What the filesystem, keystore, and network scans actually look at.

Certificate renewal

End-to-end CSR generation and deployment during renewal.

Troubleshooting

Common enrollment and connectivity issues.