Pinggy

Developers building web apps, APIs, or webhooks on their local machine often need to share that work publicly or test it from other devices, even when the machine sits behind a firewall or NAT. Traditionally this requires deploying to a cloud server, configuring DNS and certificates, or installing and configuring dedicated tunneling software just to get a temporary public endpoint. Debugging the traffic flowing through such a tunnel typically means adding separate logging or proxy tools. This adds setup time and friction for a task that is often needed quickly and temporarily, such as demoing a site, testing a webhook, or sharing a local build with a teammate.

Pinggy creates HTTP, HTTPS, TCP, UDP, or TLS tunnels from a public URL to a local address using standard SSH remote port forwarding, so no special client binary needs to be downloaded to get started. Users run a single SSH command (or use the CLI, GUI desktop app for Windows/Mac/Linux, or SDKs for Node.js and Python) to expose a local port, with support for password protection, IP whitelisting, key/token authentication, and custom or wildcard domains with built-in Let's Encrypt HTTPS. A built-in Web Debugger, now integrated into the Pinggy Dashboard, lets users inspect, modify, and replay HTTP requests and responses live, along with a terminal interface showing request logs and bandwidth stats. Tunnels can run from servers in multiple regions (USA, Europe, Asia, Brazil, Australia), and TLS tunnels offer end-to-end encryption so Pinggy cannot read the traffic (a