Pinggy

Public reverse tunnels to localhost using SSH remote forwarding or the Pinggy CLI. Use for authorized dev/test ingress, webhook capture, controlled lab callbacks, and temporary remote access without router port forwarding.

Scope Guard

• Confirm the exposed service, audience, time window, and authorization before creating a public URL or port.
• Default to short-lived tunnels, strong app-layer auth, and IP allowlists for anything sensitive.
• Do not expose admin consoles, databases, model servers, MCP tools, or shells to the internet without explicit access controls and owner approval.
• Prefer tls for end-to-end encrypted HTTPS services when Pinggy must not inspect HTTP content; HTTP tunnels terminate at Pinggy to provide debugger and header features.

Choose the Mode