Wiredoor

Wiredoor is a self-hosted ingress platform that exposes private HTTP, TCP, and UDP services through outbound WireGuard tunnels so remote users can access…

  • Network Services
Wiredoor is a self-hosted ingress platform that exposes private HTTP, TCP, and UDP services through outbound WireGuard tunnels so remote users can access local applications without opening inbound ports.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

73/100 Good

Maintained
98last commit 2 days ago
Popular
641,626 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
82no serious findings, 3 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
1,626
Open issues
9
Last commit
2026-11-19
Latest release
v1.8.1
License
Apache-2.0
Activity
steady

Checked today - source: GitHub (wiredoor/wiredoor)

Resources & Compatibility

Requirements not published yet.

Checked today - source: Docker Hub image tags and published docs

First-install notes

  • Fill in .env and open server ports After copying .env.example to .env, set the admin username/password, public hostname/IP, VPN port, and VPN subnet, then make sure TCP ports 80 and 443 and the UDP VPN port, usually 51820, are open before running docker compose up -d. If any of these are missing or blocked, the server can start but your devices cannot reach it or build the private tunnel. source
  • Install the client CLI on each device Use the matching PowerShell, Linux, or macOS Homebrew command from the quickstart to install the Wiredoor CLI before you try to connect a device. It is the command-line app used to connect your computer to the server, so a device without it cannot join your network. source
  • Log in each device to the server After the server is running, run wiredoor login --url https://your-server-address on each device, replacing the example with your real domain or IP. Then run wiredoor status to confirm the device can connect; if it fails, go back to the server address, ports, or firewall. source

Fetched today - each note links to its source

Alternatives (6)

  • Bobarr
  • defguard - defguard is an SSO & VPN Server based on OpenID and WireGuard VPN with unique secure & private architecture for building secure and…
  • frp - A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.
  • netgoat
  • pangolin - Pangolin is an open-source, self-hostable zero-trust remote access platform built on WireGuard that combines a secure VPN, an identity-awar…
  • wg easy - WG Easy is a self-hosted web interface that lets home-server users run and manage WireGuard virtual private network (VPN) clients, includin…

Checked today - source: AlternativeTo

Common questions

What server ports need to be open before running Wiredoor?

Open TCP ports 80 and 443 and the UDP VPN port, usually 51820. The server can start even if these are missing or blocked, but devices cannot reach it or build the private tunnel.

Do I need to install a client on every machine that should connect to Wiredoor?

Yes, use the matching PowerShell, Linux, or macOS Homebrew command to install the Wiredoor CLI before connecting a device. A device without it cannot join the network.

Can Wiredoor automatically handle HTTPS certificates for public web services?

Yes, it can use automatic Let's Encrypt certificates for eligible public domains. It also provides self-signed certificates for local and internal domains.

Can I require authentication or restrict an exposed service to specific IPs?

Yes, Wiredoor supports OAuth2 authentication and IP-based access restrictions.

How can I expose services that are not running directly on the node's operating system?

Use a Gateway Node to provide access to approved services in a Docker network, Kubernetes cluster, or private subnet. A Client Node exposes a service running on the same computer.

Answers sourced from github.com, github.com, github.com

Community

Collected today - public community threads