AdGuardHome Sync

AdGuardHome Sync is a lightweight tool for homelab users that keeps multiple AdGuard Home instances consistent without manual reconfiguration by replicating…

  • Backup
  • Network Services
  • Tools & Utilities
AdGuardHome Sync is a lightweight tool for homelab users that keeps multiple AdGuard Home instances consistent without manual reconfiguration by replicating general settings, filters, rewrites, services, clients, DNS (Domain Name System) and DHCP (Dynamic Host Configuration Protocol) configuration, and themes from a primary instance to replicas.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

84/100 Excellent

Maintained
100last commit 19 days ago
Popular
651,868 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
10020 MB minimum RAM, runs on ARM
Security check
90no serious findings, CI, tests, OpenSSF Scorecard 7.6/10

Availability: platform listings confirmed today, links checked 51 days ago

GitHub stars
1,868
Open issues
2
Last commit
2026-11-01
Latest release
v0.9.6
License
Apache-2.0
Activity
steady

Checked 19 days ago - source: GitHub (bakito/adguardhome-sync)

Resources & Compatibility

Minimum requirements: 20 MB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Initial setup Before syncing, replica AdGuard Home instances must first be created as replicas of the primary instance. The project wiki covers initial setup, FAQ, and deprecated features. source
  • Setup of initial instances Configure one primary and one or more replica AdGuard Home instances before running AdGuardHome Sync. source
  • Sync feature defaults Check the sync configuration after first start: all listed features are enabled by default and can be disabled individually. source

Fetched 17 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which Docker network should I use for adguardhome-sync and the AdGuardHome instances?

Put the sync container and the AdGuardHome instances on a dedicated bridge Docker network.

Do I need to complete the AdGuardHome setup wizard on every instance before the first sync?

Yes. Both the origin instance and the replicas must be initially set up with AdGuardHome via the AdGuardHome installation wizard.

How do I keep the sync running if one instance returns an error?

Set CONTINUE_ON_ERROR to true. This tells adguardhome-sync to continue sync on errors.

Answers sourced from github.com, www.reddit.com

Community

Collected 53 days ago - public community threads