Dashboard and CLI
Manage nodes, domains, certificates, and exposed services through the dashboard or command line.
Publish local development tools and self-hosted web apps through an HTTPS domain while the application remains on your private network.

Manage nodes, domains, certificates, and exposed services through the dashboard or command line.
Remote nodes connect outward to Wiredoor Server, and forwarded traffic crosses the encrypted tunnel.
Route web applications by domain or path and TCP or UDP services by an approved public port.
Use Let's Encrypt for eligible public domains or self-signed certificates for controlled internal access.
Reach services on the server itself, one remote host, or an approved private subnet.
Protect HTTP routes with OAuth2 or restrict HTTP, TCP, and UDP access to approved client addresses.
Run Wiredoor across private LANs, on-premises servers, Docker environments, and Kubernetes clusters without accepting new inbound connections on the private network.
Client and Gateway Nodes initiate encrypted connections to your public Wiredoor Server from inside the private network.
Use Client Nodes on Linux, Windows, or macOS, and Gateway Nodes on Linux, Docker, or Kubernetes.
Publish selected HTTP, TCP, or UDP services while the rest of the private network remains unreachable.