Your infra's Ark — back up everything, keep it yours.
Manage backups across all your servers from a single dashboard.
Arkeep is an open-source, self-hosted backup manager built on Restic and Rclone. Run one central server, deploy a lightweight agent on each machine, and manage backup schedules, destinations, notifications and restores from one web interface.
Use it to bring backups for your Docker hosts, databases and directories into one place. Your backup repositories remain standard Restic repositories, accessible even without Arkeep.
Get started: back up and restore your first file
Website · Documentation · Installation options · Discussions
- One policy, many destinations — local disk, S3-compatible storage, SFTP, restic REST server and 40+ Rclone backends, for a real 3-2-1 setup
- Docker-aware — volumes are discovered on their own; databases stream straight into restic with
pg_dump,mysqldumpand friends - Retention and integrity checks — per destination, on their own schedule
- Browse and restore — open any snapshot, download a file or a folder, restore a selection in place or elsewhere
- Know when it fails — email, webhooks (Slack, Discord, n8n…) and Healthchecks.io pings
- Your login, your rules — local accounts with TOTP 2FA, or single sign-on with any OIDC provider
- No lock-in — repositories stay plain restic, readable without Arkeep
More on the website.
The server hosts the web GUI and the REST API (port 8080) and schedules every job. An agent runs on each machine you back up: it dials out to the server over gRPC (port 9090), enrolls on first start and switches to mTLS on its own. Agents never listen on a port, so they work behind NAT and firewalls. State lives in SQLite by default, or PostgreSQL.
Details in Architecture.
Start with the step-by-step quickstart. It runs the server and an agent on the same machine with Docker Compose, backs up a folder to a local destination, and walks you through restoring a file to a separate location.
You need a Linux machine, or Docker Desktop, with Docker and Docker Compose. The guide covers the commands, secrets and filesystem permissions needed for the trial.
By the end, you will have:
- Started the server and connected your first agent.
- Created the admin account and a backup destination.
- Configured a policy and completed your first backup.
- Browsed a snapshot and restored a file.
The local destination is for trying the workflow. For an off-site copy, add an S3, SFTP or Rclone destination.
Once you have tried the workflow, follow the Docker Compose installation guide to deploy the server and add agents on other machines.
Other deployment options: Standalone binary · Agent via systemd · Kubernetes (Helm) · Reverse proxy and TLS.
Container images are available on Docker Hub and GitHub Packages.
Everything else lives at arkeep.io/docs:
| Install | Docker Compose · Binary · Kubernetes (Helm) · Agent via systemd · Reverse proxy and TLS |
| Operate | Upgrading · Backing up Arkeep itself · Health and metrics |
| Use | Destinations · Policies · Databases · Docker volumes · Snapshots and restore · Notifications |
| Reference | Server configuration · Agent configuration · Webhook events · FAQ |
Backups and recovery come first. The next stages build on that foundation:
- v1.0 — Production-ready core: complete automated restore testing and broaden test coverage. Snapshot browsing, file download and restore, the Helm chart and the documentation site are already available.
- v1.x — Inventory: hosts, containers and VMs in one view, with a backup coverage map.
- v2.0 — Update orchestration: Docker, OS and Proxmox updates gated by a recent verified backup, with rollback.
- v2.x — Intelligence: CVE correlation, AI reports, bandwidth throttling and BYOK keys.
See the roadmap for shipped and planned items. The inventory, update orchestration and intelligence stages describe future work.
Arkeep sends an anonymous daily ping (random instance ID, version, OS, number of agents and policies). No
personal data, backup contents, credentials or hostnames. Turn it off with ARKEEP_TELEMETRY=false; see
Telemetry.
Contributions are welcome. Please read CONTRIBUTING.md and the development setup first. Security issues: see SECURITY.md.
Hey 👋 I’m Filippo, the independent maintainer of Arkeep.
Arkeep is built around a simple idea: before touching production, you should know you have a backup you can actually recover from.
If Arkeep saves you time, helps your workflow, or gives you more confidence managing your infrastructure, you can support the work behind it through GitHub Sponsors.
Sponsoring is a bit like buying me a coffee for open source: it helps me spend more time on bug fixes, documentation, releases, restore testing, and the next pieces of the roadmap, from inventory to safer update orchestration.
Thank you to everyone who has sponsored Arkeep, past and present. Your support keeps the project independent and moving forward.
Arkeep is licensed under the Apache License 2.0.
Copyright 2026 Filippo Crotti / Arkeep Contributors