Documentation

Guides

Each guide covers one task, with controls named exactly as they appear in the dashboard.

Start a Free TrialWhat the 7-day free trial includes, where to see the days and allowances left, and what happens when you choose a plan or it ends.5 steps Connect a ServerConnect a Linux server you already run, from any provider, as root or a user with sudo, and check what the platform detects about it.5 steps Run a PlaybookUpdate packages, install software, harden SSH or free disk space on one or many servers, with a dry run and a preflight check on each server.5 steps Run a CommandRun one shell command on the servers you choose, follow each server’s output as it arrives, and review every exit code afterwards.5 steps Use a Server TemplatePrepare a WordPress, Laravel, Node.js or Python server, an Nginx reverse proxy with Let’s Encrypt, or a CI runner host in one run.5 steps Harden a ServerTurn on Fail2Ban, a firewall and safer SSH settings with one playbook, starting with a dry run, without losing SSH access to the server.6 steps Manage a RunReview each server’s results, continue after the canary server, cancel a run, or retry only the servers that did not succeed.5 steps Create a MonitorSet up website, port, SSL, DNS, domain and server health checks that run from outside your network, try a safe fix first, and alert you if it does not work.6 steps Set Up BackupsChoose what to back up, where the copies go and how often, then run a first backup. Archives go straight to your storage, never to the platform.5 steps Test a BackupReview the weekly restore tests, test any backup on demand, and understand what passed, failed and could not run each mean for a backup.4 steps Invite Your TeamGive colleagues their own login to the same servers, automation, monitors and backups, without sharing a password, and remove their access in one step.5 steps

Getting started

Follow these steps in order. Each one depends on the step before it.

Connect your servers

Connect any Linux server you can reach over SSH, from any provider, as root or a user with sudo. The platform detects the distribution, package manager, root access, CPU, memory and disk, and pins the host key on the first connection.

You need: A server, and a password or SSH key for an account on it.

Server management

Run your first playbook

Run a playbook such as Update Packages on a few servers. Dry run it first, keep "Try one server first" on, review the canary server’s output, then continue. Every server is checked before anything changes.

You need: A connected server running a distribution the playbook supports.

Linux server playbooks

Set up monitoring

Add monitors for your sites, ports, certificates and domains, and a server health check for each server. Attach the server so Auto-Fix can try a safe repair before alerting you, and choose where alerts go.

You need: A public address to check, or a connected server.

Auto-Fix

Set up backups

Add a source (a directory, a database or both), storage you own and a schedule. Each source’s newest backup is restore-tested every week, so a backup that would not restore is found before you need it.

You need: A connected server, and an S3-compatible bucket or space on the server.

Server backups

Feature reference

Detailed explanations of how each part of the platform works.

Start free trial

Guides

Getting started

Connect your servers

Run your first playbook

Set up monitoring

Set up backups

Feature reference

Playbook reference

Template reference

Common errors

Command runner

Server templates

Security hardening

Run history

Safe rollouts

Backup verification

Monitoring guides

Team access