Docs

Everything you need to connect a machine and stay in control.

Connect a device

In your dashboard, go to Devices → Add a device to get a one-time code (valid 15 minutes). On the Linux machine you want to connect, run:

curl -fsSL https://bridlehq.com/install.sh | sh -s -- YOUR-CODE

The agent installs as a service, dials out to Bridle (no open ports), and your machine turns green in the dashboard. It starts in read-only mode.

The trust ladder

New devices are read-only: Bridle can look but not touch. When you're ready, switch a device to standardmode on the Policies page to allow writes (still gated by ASK approvals). After you've approved the same action a few times, Bridle suggests setting it to auto-allow — trust you grant gradually, with evidence.

What Bridle can do

Reads default to ALLOW. Writes default to ASK. You change any of it, per device, on the Policies page.

Reads

system.health.read — CPU, memory, load, uptime
storage.inspect — Disk usage per mount
process.list — Running processes by resource use
docker.inspect — Containers, status, restart counts
docker.logs.read — Recent logs from a container
service.inspect — systemd service states
updates.check — Pending OS/package updates
files.search — Find files by name (never reads contents)

Writes (need approval)

docker.restart — Restart a container
service.restart — Restart a systemd service
cache.clear — Clear temp files older than 24h
updates.install — Install updates (never reboots)

Approvals on your phone

Install the free ntfy app, subscribe to a private topic, and enter it in Settings. When the AI proposes a change, you get a push with a dry-run preview and Approve / Decline — from anywhere.

Revoke a device

On the Devices page, remove any machine instantly. Its token is invalidated and the agent can no longer connect. Uninstall the agent on the machine with systemctl disable --now bridle-agent.

More detail lands as Bridle grows. Questions: hello@bridlehq.com