Public URLs for Localhost.

Without downloading any binary!
Create HTTP, TCP, UDP, or TLS tunnels to your Mac/PC.
Even if it is sitting behind firewalls and NATs.
 Free persistent URL  for 7 days & custom domain support:
Please enter a valid email

Configure your tunnel

Web Debugger
QR Code
Enter "yes" to continue connecting. Enter blank password if prompted.
Default Web Debugger URL: http://localhost:4300
Docs

Quickest way to

jupyter django apache drupal flask github gitlab joomla laravel mongodb mysql mssql nuxt nginx postgresql redis wordpress xampp ghost homeassistant shopify razorpay traefik portainer slack stripe wamp rails react svelte next express springboot nextcloud twilio telegram hugo jekyll netdata strapi jupyter django apache drupal flask github gitlab joomla laravel mongodb mysql

Share your websites and apps in seconds!

  • Skip uploading to cloud
  • No need to download any tool
  • Link your own domain
  • Basic Authentication
Learn more

Debug on the go!

  • Debug HTTP / HTTPS requests live
  • No need to download any tool
  • Replay requests
Learn more
Pinggy web debugger screenshot

Rich Terminal Interface

  • Live request logs
  • View request / response headers
  • Stats on bandwidth and more
Learn more

Secure tunnels to your private network.

Pinggy tunnel network diagram showing how the tunnel works

Easy to use apps

Desktop App

  • Available for Windows, Mac, and Linux
  • Easy to use GUI to manage your tunnels
  • Auto start tunnels on boot
Learn more

Command Line App

  • Robust auto reconnection
  • JSON configuration
Learn more
Pinggy desktop app screenshot

Features

No downloads

Runs everywhere

Windows
Mac
Linux

Multiple Protocols

HTTPS tunnels with built-in Let's Encrypt certificates for web applications.
TCP tunnels for other applications.
UDP tunnels.
TLS tunnels for end-to-end encryption.

Instant Domains

Subdomain: Instantly get persistent custom subdomains.
Custom domain: Use your own domains with built-in HTTPS certificates.

Access Control

Password authentication with HTTP Basic authentication.
Bearer token / key based authentication.
IP whitelisting for restricted access.

Inspect & Debug

Live debugger: Inspect HTTP requests on the fly. View requests, responses, headers, etc.
Header manipulation: Change HTTP request headers before they arrive at your server.

Multiple Regions

Fast Tunnels

USA
Europe
Asia

Brazil
Australia

Subscribe to the easiest localhost tunneling.

Make your developement experience smoother by unlocking the full potential of Pinggy.

(Save upto 17%)

Free

0/month

Free for life
  • Single command tunneling
  • HTTP(S), TCP, UDP, TLS tunnels
  • Live header manipulation
  • Request-response inspection & replays
  • 60 minutes tunnel timeout
  • Random subdomains
  • Restricted bandwidth and connections

Pro

Seats

/month

(billed annually)

/month

(billed monthly)
  • Everything in Free plan
  • Persistent tunnels
  • Custom subdomains
  • Custom domains
  • Persistent TCP/UDP ports
  • Teams
  • Unlimited Data Transfer
  • Priority mail / Discord support
Get Started

Enterprise

Contact Us

 contact@pinggy.io
  • Dedicated Servers / On Premise
  • Unlimited persistent tunnels
  • Unlimited custom subdomains
  • Unlimited custom domains
  • Unlimited persistent TCP/UDP ports
  • Unlimited Teams
  • API to monitor and manage tunnels
  • Priority Discord & Call Support
Contact Us

Frequently Asked Questions

If the ssh command prompts you for a password you can just press enter (a blank password). Or you can type in something random and press enter.

For long running tunnels with auto-reconnect, generate an ssh key.
In your terminal / command prompt run: ssh-keygen
Press Enter key (Return key) till the command finishes.
After this the ssh command will no longer ask for a password.

In windows, sometimes, the ssh tunnel cannot reach localhost because of some bug in the ssh client. Replace localhost with 127.0.0.1 in your Pinggy command.

Example:

ssh -p 443 -R0:127.0.0.1:8000 -L4300:127.0.0.1:4300 qr@a.pinggy.io

Pinggy relies on SSH remote port forwarding. The option -R 0:localhost:8000 in the command only implies that connections to the public URL given by pinggy are forwarded to your localhost:8000.

No other port than the one specified by you can be accessed by Pinggy or by anyone through the public URLs provided by Pinggy.

You can read more about the -R option of openssh client here. If you are using a different ssh client, then refer to its documentation.

a.pinggy.io is routed to the Pinggy server nearest to your location. Currently we have our servers in USA, Europe, UK, Singapore, Brazil, and Australia.

Pinggy's free plan has a tunnel timeout of 60 minutes. If the tunnel is closed by you or reaches the time limit, starting a new tunnel will generate a new URL.

To obtain a permanent or persistent URL, or to use your own domain, you must subscribe to Pinggy Pro.

Yes. Current versions of Windows, Mac, as well as almost all Linux distributions come with openssh client pre-installed. Therefore Pinggy will just work out of the box.

To learn more about using Pinggy on Android read our blog post.

You can use TCP and TLS tunnels for free with Pinggy. Click on "Advanced Settings" on the top of the homepage, and select TCP.

Read our guide on long running tunnels here.

Make sure you do not add any arbitrary argument after the SSH command.

One common reason for this is that an existing tunnel with the same token is active.

Terminate your existing tunnel with the same token. You can do so from the Active Tunnels option in the dashboard.

You can also use the Force option in the dashbaord.

Pinggy does read tunnel traffic for providing the Web Debugger feature.

Use TLS tunnels for Zero trust mode, where Pinggy cannot read your data. In this case your traffic is end-to-end encrypted.