wiredoor

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.

ActiveTypeScriptApache-2.0Self HostedNetworkingProxy
Stars
1.6k
Forks
77
Stars, last 30 days
+2
Last commit
8 days ago
Contributors
7

Our take

Activeregular commits and releases

Health score

54/100

How it is scored
Activity
61
Community
23
Issues
65
Pull requests
68

+2 stars in the last 30 days

Wiredoor is an actively maintained, capable self-hosted ingress option, though its contributor activity is heavily concentrated in one person.

Good fit if

  • You need to expose HTTP, TCP, or UDP services from a private network through WireGuard, and want to control the server and routes.
  • Your services run on supported Client Nodes, Docker networks, or a Kubernetes cluster.
  • You are comfortable operating a self-hosted platform, and Apache-2.0 licensing suits your project.

Look elsewhere if

  • You want a hosted tunneling service rather than managing your own entry point and deployment.
  • Your requirements depend on a platform or gateway model other than the documented Linux, Windows, macOS, Docker, and Kubernetes options.
  • You need a project whose ongoing maintenance is not predominantly dependent on one contributor.
All health signals
Last commit2026-10-07 (8 days ago)
Commits, last 90 days70
Releases, last 12 months6 (latest v1.8.0, 2026-09-22)
Contributors7 (top contributor: 97% of commits)
Issues closed, last 90 days3 (typically closed in 1 day)
Pull requests merged, last 90 days20 (typically merged in 0 days)
Project age19 months

Checked on 2026-10-16 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

1,625

Forks

77

Change since Nov 17, 2026: 0 stars·0 forks

Overview

Wiredoor is a self-hosted ingress platform built on WireGuard tunnels and NGINX. It gives a server you control a public or internal entry point for HTTP, TCP, and UDP services on private networks, so nodes can connect outward without requiring inbound VPN access through NAT or a firewall.

It is aimed at developers and infrastructure operators who want to publish services from home labs, on-premises networks, Docker environments, or private Kubernetes clusters while managing their own routing and operational data. Client nodes run on Linux, Windows, or macOS; gateway options cover Docker networks, Kubernetes clusters, and reachable private subnets.

Key Features

  • Exposes HTTP, TCP, and UDP services through encrypted WireGuard tunnels.
  • Routes traffic through NGINX using domains, paths, and public ports.
  • Supports Client Nodes on Linux, Windows, and macOS, plus Docker and Kubernetes gateways.
  • Can provision Let's Encrypt certificates for eligible public domains and self-signed certificates for internal domains.
  • Offers OAuth2 authentication and IP-based access restrictions.
  • Provides a web dashboard and CLI for managing nodes, domains, and services.
  • Supports WebSockets and optional Prometheus metrics and Grafana dashboards.

Use Cases

  • A home-lab operator can publish a web application without opening inbound connections to the lab network.
  • An infrastructure team can make selected on-premises services reachable through a server it controls.
  • A Docker user can route traffic to containers on a shared network or services reachable from a gateway.
  • A Kubernetes operator can expose approved cluster Services through a Kubernetes Gateway.
  • A developer can remotely access a service running on their Linux, Windows, or macOS workstation using a Client Node.

What you need

Detected in the repository

  • Node.js (from package.json)
  • Automated checks on GitHub Actions

License in plain words

Apache-2.0permissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the license, the NOTICE file and a note of your changes
  • Share your changes: no
  • Includes an explicit patent grant from the contributors:

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

The README's quickstart uses the Docker setup repository to install the server, then the Wiredoor CLI to register a node and expose a service. For the complete steps, see the quickstart.

git clone https://github.com/wiredoor/docker-setup.git
cd docker-setup
cp .env.example .env
# Configure .env, then start the server:
docker compose up -d

Alternatives

  • piko: Piko exposes services through outbound tunnels and supports clustering, rather than connecting client nodes over WireGuard.
  • pgrok: pgrok uses SSH tunnels for HTTP and TCP development services, rather than WireGuard links and HTTP, TCP, and UDP ingress.
  • frpc-desktop: Frpc-Desktop is a GUI for configuring FRP tunnel clients, rather than a self-hosted ingress platform with WireGuard and NGINX.
ProjectLanguageLicenseStarsStatus
WiredoorTypeScriptApache-2.01.6kActive
pikoGoMIT2.2kActive
pgrokGoMIT3.6kQuiet
frpc-desktopTypeScriptMIT6.9kActive

Considerations

  • Wiredoor requires operating a reachable server and configuring network access for HTTP/HTTPS and the WireGuard port. Gateway routing relies on Linux iptables; Windows and macOS CLI installations support Client Node mode, while local gateway use on those systems is through Docker.
  • The project is active, with regular recent commits and releases, but the measured contributor share indicates that most of the code comes from one person. Recent issue closure and pull-request merge times are short, though the measured volume of closed issues is limited.
  • The supplied project requirements identify Node.js and CI, but no test suite. Teams should assess their own testing and deployment needs before adopting it.
  • The README notes that versions before 1.5.1 used the MIT License; version 1.5.1 and later use Apache-2.0. Check the applicable license for the version you deploy.

Found this useful?

Share it with someone who would like Wiredoor.

Comparisons