With over 34,000 GitHub stars and backing from a well-funded engineering team, Tailscale has fundamentally simplified how developers and system administrators think about secure networking. The client daemon establishes WireGuard tunnels directly between devices using sophisticated NAT traversal techniques, achieving direct peer-to-peer connections in the vast majority of network configurations without requiring port forwarding, firewall rules, or VPN concentrators. When direct connections prove impossible due to restrictive network environments, DERP relay servers provide encrypted fallback paths. MagicDNS assigns human-readable hostnames to every device on the network, eliminating the need to remember IP addresses across a tailnet. Subnet routing allows nodes to advertise access to entire local networks, enabling remote access to office resources, home labs, or cloud VPCs through a single gateway node. Exit node functionality routes all internet traffic through a designated device for privacy protection or geographic flexibility. Access control lists define granular policies for which devices and users can communicate with which services, enforced cryptographically at the network layer. The authentication layer integrates with identity providers including Google, Microsoft, GitHub, Apple, and OIDC-compliant systems for single sign-on access. Taildrop enables direct encrypted file transfers between devices without cloud intermediaries. The tailscale CLI provides complete network management from the terminal including status monitoring, route advertisement, and node configuration. Running Tailscale on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console provides a permanent, always-on node in your mesh network. BSD-3-Clause licensed with an active open-source community.

Scatter a few cheap VPS boxes, a home server, and one bare metal machine across three different providers, and Uncloud still treats them as a single place to run your applications. You describe services in ordinary Docker Compose files, deploy them with the uc command line tool, and publish any container port as a public HTTPS endpoint in a single command. Every machine joins an encrypted WireGuard mesh with its own container IP addresses, so services on different continents reach each other directly without VPN configuration or exposed ports. A built-in DNS server resolves service names to container IPs, and the integrated Caddy reverse proxy provisions and renews Let's Encrypt certificates automatically, sharing them across the cluster. Rolling updates replace containers with zero downtime, persistent Docker volumes keep stateful services safe, and the Unregistry integration pushes image layers straight to your machines when no registry is available. There is no control plane to babysit: each machine keeps a synchronised copy of the cluster state, and SSH access to any single node is enough to manage the whole fleet. 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.

Wag is an authentication gateway for WireGuard that lets each device reach only the routes it should, and asks for a second factor before the sensitive ones open. Admins write access policies for everyone, groups, or single users, marking subnets, hosts, ports, and protocols as MFA-required, always allowed, or denied, and the most specific prefix wins, so one allowed address can sit inside a protected range. Devices join with a registration token, and the public endpoint answers with a finished WireGuard profile. Users then confirm a TOTP code, a WebAuthn security key, an OIDC single sign-on login that maps identity provider groups into Wag groups, or a PAM prompt, and repeated failures lock the account. Session lifetime and idle timeouts decide when they must prove themselves again. The browser portal lists users, devices, rules, registration tokens, and webhooks with real-time notifications, while a command line locks devices, resets MFA, and manages administrators. Webhooks turn JSON from an HR or identity system into new tokens or removed users and devices, and clients can fetch the list of guarded routes from a small API. Remote staff, contractors limited to one host, and homelabs are typical uses. When a server fails, the VPN remains reachable through clustering with witness nodes or an external etcd, and certificates arrive through ACME with HTTP-01 or Cloudflare DNS-01. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. BSD-3-Clause licensed.

Watching a MikroTik RouterOS v7 router in real time is what MikroDash is for: live traffic, connections, Wi-Fi clients, DHCP leases, and WireGuard peers reach the browser the moment anything changes. Cards drag into any layout, and the arrangement follows your account to every browser. Managing a fleet happens on the Devices page, which shows routers as cards, a list, or a world map with 24-hour connectivity, last backup, open alerts, and pending updates. Rolling out a change starts in Config Management: choose one of 20 ready-made templates or capture your own, then deploy to one router or the fleet with a restore point, a canary router, and an automatic revert if a change cuts MikroDash off. Scheduled backups are kept only when something changed, with a diff and a guarded restore. New sites join through a generated script that calls home over a built-in WireGuard tunnel, even from behind NAT. Alerts reach SMTP, Telegram, ntfy, Discord, Slack, Gotify, Pushover, and Apprise. Troubleshooting stays in the browser with ping, traceroute, torch, bandwidth tests, a packet sniffer, and a RouterOS terminal. Read-only API access covers every page and alert, while roles, OpenID Connect sign-in, and an audit trail of every write govern shared use. Off by default, an optional assistant answers from live router data and asks before changing anything. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

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.