Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Ur
Self-host UrBackup
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A client/server backup system for whole fleets of machines: install the UrBackup client on Windows or Linux computers and the server pulls incremental file backups and full or incremental disk-image backups from them on a schedule, over the LAN or the internet. The web interface shows each client's status, browses and restores files, and manages retention, quotas, alerts and user accounts. The server initiates the backups, so clients need no scheduler of their own.
Pick UrBackup when you need to back up a fleet of ordinary computers, including whole-disk images of Windows machines, to one server on your network. You install a small client on each Windows or Linux machine and the server pulls incremental file backups and full or incremental image backups on a schedule, then shows every client's status and lets you browse and restore files from the web interface. The server is AGPL-3.0 C++. Our snippet runs the official `uroni/urbackup-server` image at 2.5.38, released 2026-08-30, with host networking as the image's README prescribes, so the server's UDP discovery broadcasts reach your LAN, and the web interface on port 55414. We did not find an upstream RAM minimum, so our 512 MB floor is an estimate. Unlike restic, Kopia, Backrest, borgmatic and Zerobyte, which back up folders (or, for Zerobyte, mounted network shares) from the machine that runs them to a repository, UrBackup is client-driven by the server and covers disk images; Duplicati is the other tool with a browser interface, but it runs on each machine it protects.
What you need
Any VPS with at least 512 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# UrBackup Server — pinned to 2.5.38 (the image's 2.5.x tag, pinned by digest because upstream publishes no exact-version tag)mkdir -p urbackup/database urbackup/backupscat > docker-compose.yml <<'EOF'services: urbackup: image: uroni/urbackup-server:2.5.x@sha256:fd218c45192fad0d7df7989da2c991264eec0a37a85e33499db419b203e9745f container_name: urbackup restart: unless-stopped network_mode: host environment: - PUID=1000 - PGID=1000 - TZ=UTC volumes: - ./urbackup/database:/var/urbackup - ./urbackup/backups:/backupsEOFdocker compose up -dtimeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:55414/; do sleep 3; done'# → http://SERVER_IP:55414 — no login yet: open Settings → Users and create an admin account first, or anyone who can reach the port can browse every client's backups. Clients then connect over the LAN (or port 55415 for internet clients)
UrBackup's administration manual and the Docker image's README flag these before you rely on it:
non-negotiableA fresh server has no user accounts. The manual says that until you add an admin account in the settings, everybody who can reach the web interface can see every backed-up file, so create the admin before you install any clients and keep port 55414 off the internet.
non-negotiableThe image has moving tags such as latest, 2.5.x, 2.5.x-btrfs and 2.5.x-zfs, and exact tags exist only for old 2.4 releases; there is no exact 2.5 tag. We pin the 2.5.x tag by its sha256 digest (it was pushed on 2026-08-30, the day of the 2.5.38 release), so a plain docker compose pull will not move it, and upgrading means picking a new digest.
non-negotiableThe image runs with network_mode: host, so it binds ports 55413 (FastCGI), 55414 (web) and 55415 (internet clients) directly on the host, plus UDP discovery. Clients on the LAN find the server by broadcast; clients elsewhere need the server's internet name or IP set and port 55415 forwarded.
non-negotiableBackups land in ./urbackup/backups and the server's database in ./urbackup/database; back both up. The manual recommends storage that can be extended (RAID, LVM, btrfs or ZFS), and btrfs or ZFS snapshot modes need the image's -btrfs or -zfs tags plus SYS_ADMIN or /dev/zfs, which our snippet does not enable.
UrBackup used 14 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 512 MB.
Is the UrBackup install snippet verified?
The UrBackup install snippet is marked verified on Ubuntu 26.04 (Nov 2026).