A self-hosted front door for apps that live on home labs, office LANs, and private clusters, Wiredoor publishes them to the internet without opening a single inbound port on the private side. The Wiredoor CLI on each remote machine dials out to the server over an encrypted WireGuard tunnel. Web apps and APIs are routed by domain and path, WebSocket traffic included, while TCP and UDP services such as SSH or Redis get a public port of their own. Public domains receive Let's Encrypt certificates, internal names fall back to self-signed ones, and Cloudflare or GoDaddy credentials let the server create DNS records itself. Any web route can demand OAuth2 sign-in with an email allow list and a few open paths, and every protocol accepts IP allow lists. Gateway nodes stretch one tunnel across a Docker network, Kubernetes cluster, or private subnet, so a single link serves many backends. Services can be switched off or given an expiry such as 30 minutes, 2 hours, or 1 day. The dashboard shows which nodes are connected and whether their services are enabled, while the CLI creates, enables, and disables services from a terminal. Optional Prometheus and Grafana views chart traffic and tunnel peers, and CrowdSec can block abusive addresses. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Combining Docker container labels with a live web control plane, DockFlare automates Cloudflare Tunnel ingress routing, multi-zone DNS records, and Zero Trust Access policies across self-hosted infrastructure. DevOps engineers and homelab operators can attach simple container labels to expose HTTP, HTTPS, TCP, SSH, and RDP services publicly in seconds without clicking through external cloud dashboards. For non-containerized workloads such as bare-metal hypervisors or network appliances, administrators can define manual ingress rules, path-based routes, custom TLS SNI headers, and origin certificate bypass flags directly in the web interface. Security teams use reusable Access Groups and wildcard zone policies to enforce Google, GitHub, Azure AD, or custom OIDC authentication across every subdomain from a single policy definition. Distributed deployments connect lightweight remote agents back to the primary controller using Zero Trust service tokens so multi-host clusters share one unified routing view. When containers stop or restart, configurable grace-period timers prevent accidental route churn before cleaning up stale DNS entries, while encrypted state backups protect your entire ingress configuration. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.