flowchart LR
client([Client]) -- DNS --> pihole[Pi-hole]
pihole -- upstream --> unbound[unbound<br/>DNS over TLS]
client -- HTTPS --> zoraxy[Zoraxy<br/>reverse proxy]
remote([Remote device]) -- WireGuard --> tailscale[Tailscale<br/>subnet router] --> zoraxy
zoraxy --> apps[Nextcloud · Vaultwarden<br/>Actual · Homepage]
zoraxy --> ops[Beszel · Uptime Kuma]
ops -. OIDC .-> pocketid[Pocket ID<br/>passkeys]
- Every service has its own hostname under a local domain. Pi-hole resolves the wildcard to the reverse proxy, and Zoraxy terminates TLS.
- Services sit on a shared Docker network behind the proxy and do not publish ports unless they have to.
- Pocket ID provides passkey sign-in over OIDC.
| Name | Role | |
|---|---|---|
| Docker Compose | One stack per service | |
| Zoraxy | Reverse proxy and TLS | |
| Pi-hole | DNS and ad blocking | |
| unbound | Upstream resolver, DNS over TLS | |
| Tailscale | Remote access | |
| Pocket ID | OIDC provider with passkeys | |
| Nextcloud | Files, with MariaDB and Redis | |
| Vaultwarden | Password manager | |
| Actual | Budgeting | |
| Homepage | Start page | |
| Beszel | Resource monitoring and alerts | |
| Uptime Kuma | Uptime checks | |
| Diun | Image update notifications | |
| Speedtest Tracker | Connection history |
stacks/
└── <service>/
├── docker-compose.yml
└── .env.example
cd stacks/<service>
cp .env.example .env # fill in the values
docker compose up -dStart zoraxy first. It creates the network zoraxy_default that the stacks behind the proxy join.