Skip to Content
🚀 Wiredoor v1.7.3 now available - Ready to expose your private services? Get Started →

Self-Hosted Ingress for
Private Services

Expose HTTP, TCP, and UDP services from private networks through outbound WireGuard tunnels. Keep control of your public endpoint, routing, certificates, and access policies.

wiredoor.net
wiredoor login --url https://wiredoor.example.com
username: admin@example.com
password: ***********

wiredoor http first-app --domain app.example.com --port 3000
Service created: https://app.example.com → http://localhost:3000
- first-app [HTTP] → https://app.example.com
Wiredoor
Kubernetes
Docker
React
Laravel
Next.js
NestJS
ArgoCD
Wordpress

Publish local development tools and self-hosted web apps through an HTTPS domain while the application remains on your private network.

Deploy Wiredoor / Explore the architecture

Control How Private Services Become Reachable

Planet

Dashboard and CLI

Manage nodes, domains, certificates, and exposed services through the dashboard or command line.

Outbound WireGuard Tunnels

Remote nodes connect outward to Wiredoor Server, and forwarded traffic crosses the encrypted tunnel.

HTTP, TCP, and UDP

Route web applications by domain or path and TCP or UDP services by an approved public port.

Certificates for Each Context

Use Let's Encrypt for eligible public domains or self-signed certificates for controlled internal access.

Local, Client, and Gateway Nodes

Reach services on the server itself, one remote host, or an approved private subnet.

OAuth2 and IP Restrictions

Protect HTTP routes with OAuth2 or restrict HTTP, TCP, and UDP access to approved client addresses.

Connect the Networks You Already Operate

Run Wiredoor across private LANs, on-premises servers, Docker environments, and Kubernetes clusters without accepting new inbound connections on the private network.

Wiredoor CLI
wiredoor login --url https://wiredoor.example.com
username: admin@example.com
password: xxxxxxxxxxxx

wiredoor http grafana --domain grafana.example.com --port 3000
Service created: https://grafana.example.com -> http://localhost:3000
A
AliceCan you publish our Grafana dashboard?
BobI'll expose it through Wiredoor with OAuth2.
B
Protected route ready: https://grafana.example.com

Outbound by Design

Client and Gateway Nodes initiate encrypted connections to your public Wiredoor Server from inside the private network.

Fits Your Environment

Use Client Nodes on Linux, Windows, or macOS, and Gateway Nodes on Linux, Docker, or Kubernetes.

Expose What You Choose

Publish selected HTTP, TCP, or UDP services while the rest of the private network remains unreachable.

Keep Your Services Private Until You Choose to Expose Them