wiredoor/wiredoor

Health v2 · maintenance only

Adoption not part of the score

1620 stars · 77 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Wiredoor is a self-hosted ingress-as-a-service platform that exposes services running in private or local networks to the internet via reverse VPN tunnels powered by WireGuard and an NGINX reverse proxy. It includes a web UI, CLI client, automatic SSL via Let's Encrypt, OAuth2 authentication, and Docker/Kubernetes gateway integrations.

Use cases

• expose a local web app to the internet without opening firewall ports
• share an internal dashboard like Grafana or a k8s dashboard with external users
• self-hosted alternative to ngrok or Cloudflare Tunnel
• expose services from a private Kubernetes cluster via a Helm gateway
• tunnel HTTP or TCP services from Docker containers or IoT devices
• add OAuth2 login and SSL to internally hosted apps

When to choose

• you want full control and self-hosting of your ingress without cloud vendor lock-in
• you need low-latency WireGuard tunnels instead of HTTP-based tunnels
• you expose services from air-gapped, on-prem, or hybrid environments
• you want automatic Let's Encrypt SSL, OAuth2 protection, and a management UI in one platform

When to avoid

• you only need a quick throwaway tunnel and prefer a zero-setup hosted service
• you cannot run a publicly reachable server with ports 80/443 and UDP 51820 open
• you need a managed solution with no infrastructure to maintain

Facets

application · maturity active

proxy networking security http-server monitoring networking self-hosted security infrastructure-as-code self-hosted cli wireguard nginx reverse-proxy tunneling ingress vpn lets-encrypt oauth2 crowdsec ngrok-alternative devops containers linux docker kubernetes

Member repositories

For agents

markdown · JSON · MCP: product_card(name="wiredoor/wiredoor")