YAPD: a self-hosted multi-instance dashboard for Pi-hole v6+

General
1

Hi everyone :waving_hand:,

I have been working on YAPD - Yet Another Pi-hole Dashboard :puzzle_piece:, a self-hosted dashboard for people who run more than one Pi-hole instance and want a clearer way to operate them from one place.

YAPD is an independent third-party project :warning:. It is not affiliated with, endorsed by, or sponsored by Pi-hole, LLC; "Pi-hole" is referenced only to identify compatibility with Pi-hole installations.

The project is still in active development :construction:, but it is already useful for homelab and small-network setups where a single Pi-hole admin panel is not enough anymore.

Why I built it :light_bulb:

Running one Pi-hole is simple. Running several Pi-hole instances across a home lab, VLAN setup, family network, or small office can get harder:

  • :gear: settings can drift between instances;

  • :magnifying_glass_tilted_right: query activity is split across different admin panels;

  • :repeat_button: manual syncs can become risky;

  • :bell: operational failures are easy to miss;

  • :receipt: important changes need a visible history.

YAPD tries to solve that by giving you one operational surface for your Pi-hole environment :desktop_computer:.

What it does today :sparkles:

  • :compass: Manage and monitor multiple Pi-hole v6+ instances from one dashboard.

  • :bar_chart: Inspect recent DNS activity and imported historical query data.

  • :brick: Compare groups, clients, domains, ad-lists, and configuration across instances.

  • :test_tube: Detect drift before syncing selected changes.

  • :bell: Track operational failures and Pi-hole messages in a notification area.

  • :locked_with_key: Store Pi-hole credentials encrypted in the backend.

  • :package: Support LAN/VPN-oriented deployments with Docker Compose.

  • :globe_showing_americas: Provide English and Brazilian Portuguese UI/documentation.

What I am looking for :person_raising_hand:

I would like feedback from real Pi-hole users, especially people who:

  • :puzzle_piece: run more than one Pi-hole instance;

  • :package: use Pi-hole in Docker;

  • :globe_with_meridians: maintain separate networks, VLANs, or family devices;

  • :shield: care about safer sync, drift detection, and query visibility;

  • :test_tube: are willing to test an early project and report rough edges.

I am especially interested in feedback about:

  • :toolbox: setup experience;

  • :compass: whether the multi-instance model makes sense;

  • :computer_mouse: confusing UI flows;

  • :electric_plug: edge cases with Pi-hole v6+ API behavior;

  • :globe_showing_europe_africa: Docker Compose and reverse proxy deployment issues.

Links :link:

Safety note :shield:

YAPD can read and change real Pi-hole state. Please test it in a controlled environment first, keep Pi-hole backups/Teleporter exports, and review sync actions before applying them to production instances.

I have not tested YAPD in IPv6 environments yet :globe_with_meridians:, so feedback from IPv6 users would be especially useful.

If you try it, I would really appreciate bug reports, screenshots of confusing flows, deployment notes, and suggestions for what would make it more useful for multi-instance Pi-hole setups :folded_hands:.

:open_mailbox_with_raised_flag: Note to the Pi-hole team and moderators:

If this post or project violates any community rule, trademark guideline, or other expectation, please email me at leufrasiojunior@gmail.com and I will remove it immediately.

2

Interesting...
I had 12 piholes running a while back with DNSDist in proxmox.