Blocky vs Pi-hole

Editor take

Choose Blocky for encrypted DNS upstreams set in its config. Choose Pi-hole for a web dashboard and an optional DHCP server.

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.

Blocky

Where Blocky is stronger

  • Encrypted upstreams in the configSets DNS-over-HTTPS, DNS-over-TLS and DNS-over-QUIC resolvers in YAML; Pi-hole forwards plain DNS unless you run cloudflared or dnscrypt-proxy beside it.1
  • Prometheus metrics for dashboardsServes an optional Prometheus metrics endpoint and ships Grafana dashboards; Pi-hole's docs cover its web dashboard but list no metrics endpoint.2

Pi-hole

Where Pi-hole is stronger

  • Web dashboard to view and controlShips a browser dashboard to view and control the filter; Blocky has no web interface, so you edit YAML and use its API or CLI.3
  • DHCP server on the same boxIts optional DHCP server, once switched on, hands out addresses and the DNS setting together, so it takes over leasing from the router; Blocky leaves leases to the router.4

Blocky vs Pi-hole: 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
LicenceApache-2.0EUPL
Web UINoYes
DockerYesYes
Linux packageYesYes
Tech stackGoC / Shell
Docker Containers1 (app only)1 (app only)
DatabasenoneSQLite
Minimum hardwareNot stated512 MB RAM · 2 GB
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Blocky docs and Pi-hole docs.

Updated