caddy-docker-proxy vs Wiredoor
Docker-based routing and private-network ingress compared
caddy-docker-proxy generates and updates Caddy routing configuration from Docker labels. wiredoor provides a self-hosted server that routes traffic to private services through WireGuard tunnels, so the main difference is Docker-driven proxy configuration versus tunneled access across private networks.
caddy-docker-proxy: Route Docker Traffic Through Caddy
caddy-docker-proxy turns Docker labels into Caddy reverse-proxy configuration and updates it as containers or services change. It suits Docker users who want dynamic routing and automatic HTTPS without maintaining site configuration by hand.
Wiredoor: Self-Host Ingress over WireGuard
Wiredoor is a self-hosted ingress platform built on WireGuard and NGINX for exposing HTTP, TCP, and UDP services on private networks. It connects Linux, Windows, and macOS client nodes, plus Docker and Kubernetes gateways, to a server you control.
| caddy-docker-proxy | Wiredoor | |
|---|---|---|
| Language | Go | TypeScript |
| License | MIT | Apache-2.0 |
| Stars | 4.7k | 1.6k |
| Forks | 224 | 77 |
| Last analyzed | Oct 3, 2026 | Oct 16, 2026 |
Key differences
- caddy-docker-proxy builds Caddy routes from container or service labels; wiredoor routes HTTP, TCP, and UDP traffic through node-initiated WireGuard tunnels.
- caddy-docker-proxy focuses on Docker containers and Swarm services, while wiredoor also supports access to services across private networks and Kubernetes.
- caddy-docker-proxy is written in Go and licensed under MIT; wiredoor is written in TypeScript and licensed under Apache-2.0.
- caddy-docker-proxy can run as a standalone proxy or split controller and server roles; wiredoor uses a central server with Client Nodes or Gateway Nodes.
- caddy-docker-proxy suits Docker users seeking dynamic Caddy configuration; wiredoor suits operators managing their own ingress to private services, including home labs and restricted networks.
- caddy-docker-proxy has 4.7k stars and 224 forks; wiredoor has 1.6k stars and 78 forks.
Choose caddy-docker-proxy if you…
- need Caddy routes to update from Docker labels as containers or services change.
- want to use Caddy directives and snippets alongside Docker-managed routing.
- run Docker or Swarm and prefer a standalone proxy or separate controller and server roles.
Choose Wiredoor if you…
- need to expose HTTP, TCP, or UDP services on private networks through WireGuard tunnels.
- want a self-hosted ingress point with a dashboard, CLI management, and optional monitoring.
- need Client Node or Gateway Node access for services across private networks, Docker, or Kubernetes.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.