pgrok vs Wiredoor
Self-hosted tunneling and ingress projects compared
pgrok shares local development services through SSH tunnels, stable subdomains, and OIDC sign-in. Wiredoor uses WireGuard and NGINX to route HTTP, TCP, and UDP services from private networks, with support for client nodes and Docker and Kubernetes gateways.
pgrok: Share Local Services Through SSH Tunnels
pgrok is a self-hosted reverse-tunnel service for small teams that need to expose local development services through stable subdomains. It uses SSH port forwarding and OIDC sign-in, with support for HTTP and raw TCP traffic.
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.
| pgrok | Wiredoor | |
|---|---|---|
| Language | Go | TypeScript |
| License | MIT | Apache-2.0 |
| Stars | 3.6k | 1.6k |
| Forks | 132 | 77 |
| Last analyzed | Oct 3, 2026 | Oct 16, 2026 |
Key differences
- pgrok focuses on small-team development tunnels, while Wiredoor covers ingress for home labs, on-premises networks, Docker, and Kubernetes.
- pgrok uses SSH port forwarding and requires PostgreSQL; Wiredoor uses WireGuard tunnels and NGINX routing.
- pgrok supports HTTP and raw TCP traffic; Wiredoor supports HTTP, TCP, and UDP.
- pgrok is written in Go and uses the MIT license; Wiredoor is written in TypeScript and uses Apache-2.0.
- pgrok can be deployed as a binary, Docker container, or Docker Compose setup; Wiredoor offers client nodes and Docker and Kubernetes gateway options.
- pgrok warns against production systems with availability requirements; Wiredoor's supplied requirements identify no test suite, so teams should assess their testing and deployment needs.
Choose pgrok if you…
- need stable subdomains and OIDC-gated SSH tunnels for a small development team.
- want to route selected HTTP paths to alternate local services or forward raw TCP traffic.
- can operate the required public server, domain, DNS, OIDC integration, and PostgreSQL database.
Choose Wiredoor if you…
- want to expose private-network services through WireGuard and NGINX, including UDP services.
- need client nodes for Linux, Windows, or macOS, or gateways for Docker or Kubernetes.
- want a dashboard and CLI for managing nodes, domains, and services, with options for certificates and access restrictions.
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.