Getting Started with Reaver

Reaver is a self-hosted backup system with a unified dashboard and poll-only agents. It backs up any directory you choose; WordPress installs can be auto-discovered for self-hosters and agencies.

Architecture

Piece Role
Dashboard Control plane: UI, job queue, schedules, settings, SQLite database
Agent Worker on each host you protect: polls for jobs, runs restic, reports status 
┌─────────────────┐         poll / claim / status         ┌─────────────────┐
│    Dashboard    │ ◄───────────────────────────────────► │  Agent (host)   │
│  Web UI + API   │         (outbound HTTP only)          │  restic + paths │
│  dashboard.sqlite│                                      │  /opt/reaver-agent │
└─────────────────┘                                       └─────────────────┘

There is no inbound HTTP API on the agent and no local job queue on the agent. All job writes go through the dashboard. The optional MCP server is on the dashboard, not on agents.

Quick start

  1. Install the dashboard on a control server — see Installation (CDN installer with --url and --dir, or interactive prompts).
  2. Complete the setup wizard (admin account).
  3. Follow the First Backup Walkthrough (also shown in the dashboard after login):
    1. Install an agent (SSH or manual pair)
    2. Discover WordPress sites and/or add custom paths
    3. Choose storage — local repo on the agent, or configure offsite, then set primary repository
    4. Run the first backup
    5. Create a schedule
  4. Configure SMTP when you want invites and email alerts (recommended, not required for first backup).
  5. Use Restore for snapshot restore or portable archives when you practice recovery.

Core ideas

  • Dashboard = source of truth for jobs, schedules, and fleet state.
  • Agents poll for site-scoped work (backup, restore, export, offsite).
  • Restic powers incremental, deduplicated backups.
  • Client-side restic encryption is optional (off by default); when enabled, local and remote restic passwords are both dashboard-managed (see Security).
  • License for paid tiers is linked to your Reaver website account (email/password), not a free-floating key.
  • Optional MCP server (all paid plans) lets AI clients start the same jobs from chat. Off until you enable it — MCP Server for AI Agents.

Next steps

Docs
Getting Started
Installation
First Backup Walkthrough
Agents & Sites
Backup Jobs
Schedules
Restore & Archives
Cloud Destinations
Offsite Storage & SSH Setup
Configuration
Security
Public API and chat apps
MCP Server for AI Agents
FAQ