Pi-hole and Unbound made it easy to manage a preteen's internet access — right up until Pharos Systems needed real high availability, and Pi-hole had no good answer for that. Technitium did: multi-node HA, split-horizon DNS. The one thing it didn't make easy was Advanced Blocking's own config — a JSON blob meant to be hand-edited once and never touched again. Pharos Advanced Blocking is the TUI built so you can actually touch it: validated before it's written, checked after it's deployed, safe by default the whole way through.
Install it:
$ curl -sSL https://raw.githubusercontent.com/pharos-systems-llc/pharos-advanced-blocking/main/install.sh | bash
Installs the pab binary for Linux (amd64/arm64).Full install options (.deb/.tar.gz downloads, credential setup, the TUI walkthrough) are in the Installation guide and User Guide.
What it does
pab is a single static binary — no Node, no Python, nothing else to install — cross-compiled for Linux amd64 and arm64. It's built for two audiences at once: a rich terminal UI for you, and --json output for scripts and AI agents, not as a marketing claim but because both are real, separate code paths. Every write goes through schema validation first, catching an invalid IP or a malformed subnet before it ever reaches Technitium. And it stays out of your git workflow entirely — edits land on disk; committing and pushing is still yours to do.
Running more than one Technitium node? pab deploys the same local config to every endpoint you give it, and won't silently pick a winner if two nodes disagree — you choose the source of truth. Session credentials live in ~/.config/pab/secrets.json, chmod 600, never touched by anything else.
View first, edit second
That's the real design principle behind it — check before you change anything, the same instinct behind every safety rail above. pab init sets up your config, and never silently overwrites one that's already there (a second run just shows you a structural diff).pab deploy --dry-run shows you exactly what would change before it changes anything. Then:
A real check, from the terminal
Pushing a config isn't the same as confirming it worked. pab verify live-queries the DNS resolver itself — the actual proof, not just that config was sent:
$ pab verify --domain mail.google.com
INCONCLUSIVE: could not confirm blocking for "mail.google.com" against group "Kids" on node "default"
node resolved 142.250.80.17, but group "Kids" has no configured blockingAddresses to compare against (known v1 limitation)The value of infrastructure tooling isn't in what it claims to do. It's in what it lets you check.
Every release is signed with Cosign, so what you install is provably the thing that got built.
Pharos Advanced Blocking is open source under the GNU Affero General Public License.
