AdGuard Home vs Blocky

Editor take

Choose AdGuard Home for a web dashboard and a DHCP server you switch on. Choose Blocky for a single binary that runs on an OpenWrt router.

Editor

Where they differ

Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.

AdGuard Home

Where AdGuard Home is stronger

  • Web dashboard with a query logShips a browser dashboard for settings, a query log and stats; Blocky has no web interface, just a YAML file, a REST API and a CLI.1
  • DHCP server on the same boxIts DHCP server, once switched on, hands out addresses and the DNS setting together, so devices use the filter after the router's own DHCP goes off; Blocky has none.2

Blocky

Where Blocky is stronger

  • A single binary for a routerShips one binary for x86-64, ARM and MIPS and names Raspberry Pi and OpenWrt routers as targets; AdGuard Home reaches OpenWrt through a third-party LUCI app.3
  • Prometheus metrics for dashboardsServes an optional Prometheus metrics endpoint and ships Grafana dashboards; AdGuard Home's docs list no metrics endpoint.4

AdGuard Home vs Blocky: specs side by side

Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.

Spec
PriceFreeFree
LicenceGPL-3.0Apache-2.0
Web UIYesNo
DockerYesYes
Linux packageYesYes
WindowsYes–
macOSYes–
Tech stackGoGo
Docker Containers1 (app only)1 (app only)
Databasefile onlynone
Architecturex86 + ARMx86 + ARM

Common questions

Sources: AdGuard Home docs and Blocky docs.

Updated