AdguardTeam/AdGuardHome

Prefer upstream unless you specifically need this older snapshot; this fork adds no visible capabilities and is materially behind on maintenance.

Choose this fork only if you specifically need its customizations and are willing to own maintenance. For most adopters, upstream is the safer choice because this fork is stale and materially behind current development.

Choose this fork if you value its custom tracker-data and workflow/UI changes more than upstream compatibility. Avoid it if you want the easiest path to current AdGuard Home releases, because the branch is already significantly behind and far enough ahead to imply real divergence.

Choose this fork only if Windows 7 support or the bundled Windows launcher matters more than staying close to upstream. For most users, upstream is the safer default because this fork is materially behind and appears to strip documentation.

Prefer upstream AdGuardHome unless you need this exact older snapshot. This fork does not add meaningful capabilities and is materially behind current upstream, so it is a poor choice for adopters seeking improvements or extra workflows.

Choose this fork if alert-only monitoring is the main feature you want. Choose upstream if you want current maintenance, broad compatibility, and the lowest operational risk.

Choose this fork only if its downstream behavior is exactly what you need and you are prepared to own future maintenance. For most adopters, upstream is the safer default because this fork is stale and materially behind.

Prefer upstream unless you specifically need this older customized baseline. This fork is best for legacy or bespoke deployments, not for users who want current fixes, active maintenance, or low-risk adoption.

Choose this fork only if you specifically need its old customized state. For most adopters, upstream AdGuardHome is the better default because this fork is very stale and far behind current development.