How are you using Wiredoor? Share your use case!

[dmesad]

Hey everyone!

We’d love to hear how you’re using Wiredoor in your environment.

• Are you running it in a homelab, production, staging, or somewhere else?
• What kind of services or applications are you exposing?
• What made you choose Wiredoor?
• What’s working well for you, and what could be improved?

Your experience might inspire others and help us better understand how Wiredoor is being used in the real world.

Drop your story below — we’re excited to hear from you!

[dmesad]

I'll go first!

I'm using Wiredoor in my homelab setup in a few different ways:

• I run a Proxmox server hosting several VMs for development and self-hosted services — including websites and GitLab instances. Wiredoor makes it easy to expose only what I need.
• I have a Raspberry Pi running Grafana, and thanks to Wiredoor, I can access it remotely to check metrics when I'm away from home.
• I also have a legacy video surveillance system that doesn’t support secure remote access. With Wiredoor, I was able to safely expose its RTSP stream and monitor the cameras from anywhere.
• Finally, I use a private Kubernetes cluster for automated deployments with ArgoCD. Wiredoor lets my teammates access the ArgoCD dashboard securely over the internet.

It's become an essential part of my infrastructure, helping me keep services private by default while still being accessible when needed.

[acollazo25]

🏆 It works really great mate, I'm running some games from my childhood on docker and have shared them to my friends.
Good job :)

[valerauko]

I would love to use Wiredoor to expose my HomeAssistant. I have a publicly accessible k3s cluster where I'd want to run the Wiredoor server, but I can't seem to find an existing way to do that (my use case's kinda the reverse of the k8s gateway Helm chart).

I don't mind writing my own manifests for this, I just want to make sure there isn't prior art out there first... Anything?

[dmesad]

Running the Wiredoor server inside a public cluster is a valid idea, but the main challenge is properly exposing the WireGuard port (51820/UDP) from within the cluster. Most Kubernetes setups make it tricky to expose UDP ports, especially when using a cloud load balancer or ingress controller which typically only handle TCP/HTTP.

That said, it would be possible if:

• Your K3s nodes have public IPs and you can use a hostPort or NodePort for UDP 51820.
• Or you expose the UDP port using something like MetalLB with a LoadBalancer service.

There’s no official Helm chart for deploying wiredoor server on Kubernetes yet, but if you’re comfortable writing your own manifests, you can absolutely get it working. I’d be happy to help if you decide to go that route.

Also, if your goal is to expose Home Assistant, we’ve released an official Wiredoor Addon for home assistant that takes care of the tunnel connection automatically, it might simplify your setup depending on your architecture.

[valerauko]

That should be fine. I'm already exposing UDP (though at this point only for HTTP/3) so that should be proven to work. Once I have some manifests working I'll be sure to share.

[sanbroz]

First of all, great job on this project!
I’ve explored various alternatives such as Cloudflare Tunnels, Pangolin, raw WireGuard setups, and FRP. While each has its merits, most fall short when it comes to robust TCP/UDP proxying. I’ve been actively looking for a tool with comprehensive support for both protocols, and WireDoor is proving to be a strong candidate.

I’m currently using a cloud-based VPS to proxy traffic to my home lab, where all my websites and applications are hosted. In today’s market, affordable residential internet plans rarely offer static IPs, and most low-cost ISPs operate behind CGNAT, making traditional self-hosting very challenging.

One feature that would significantly enhance usability is support for port range forwarding. For instance, I host AzuraCast, which requires a large number of open ports. Similarly, VoIP applications also demand forwarding of broad port ranges. If port range support could be implemented, it would make WireDoor an even more powerful and flexible solution for users with complex self-hosting scenarios.

Thanks again for this excellent tool and your continued development efforts!

[dmesad]

Thank you so much for the kind words and for sharing your experience!

Wiredoor currently allows exposing any number of ports, but each service is limited to a single port. That said, your use case makes a strong case for supporting port ranges, and we’ll definitely review your recommendation to evaluate whether it’s feasible to implement in a safe and practical way.

Thanks again for the thoughtful feedback and for being part of the community!