Keeps its URL
Wi-Fi drops, laptop sleeps, the edge restarts: menfez reconnects and gets the same address back. Visitors see a "reconnecting" page meanwhile, not a dead link.
Private preview
menfez opens a tunnel from a port on your machine tohttps://<name>.menfez.cloud. Show a client your work in progress, test webhooks, try your site on a phone.
curl -fsSL https://menfez.dev/install.sh | shirm https://menfez.dev/install.ps1 | iex$ menfez login <token> Token saved to ~/.config/menfez/menfez.toml $ menfez http 3000 menfez 0.1.0 connected http https://k3x9m2p7qa4b.menfez.cloud -> localhost:3000
Wi-Fi drops, laptop sleeps, the edge restarts: menfez reconnects and gets the same address back. Visitors see a "reconnecting" page meanwhile, not a dead link.
WebSockets, server-sent events, hot reload and large uploads pass through as they happen. Nothing is buffered or cached on the way.
Pages from the edge say whether the tunnel or your app is down, and carry a menfez-error header with a documented code.
A single outgoing HTTPS connection. No open ports, no router setup; works behind most firewalls and corporate proxies.
Describe your services once in menfez.toml, give the ones you share often a fixed subdomain, and start them together with menfez start.
# ~/.config/menfez/menfez.toml
[tunnels.web]
addr = "3000"
subdomain = "my-app"
[tunnels.vite]
addr = "5173"
host_header = "rewrite"