ngrok 2.0

secure introspected tunnels to localhost

Get StartedPricing

Expose local servers behind NATs and firewalls to the public internet over secure tunnels.

Save time and be more productive. Show off in-progress work for feedback and build webhook integrations with ease. Use ngrok's unique request inspection and replay to iterate quickly.

Demo without deploying

Don’t constantly redeploy your in-progress work to get feedback from clients. ngrok creates a secure public URL ( to a local webserver on your machine. Iterate quickly with immediate feedback without interrupting flow.

Simplify mobile device testing

Test mobile apps against a development backend running on your machine. Point ngrok at your local dev server and then configure your app to use the ngrok URL. It won't change, even when you change networks.

Build webhook integrations with ease

Building webhook integrations can be a pain: it requires a public address and a lot of set up to trigger hooks. Save yourself time and frustration with ngrok. Inspect the HTTP traffic flowing over your tunnel. Then, replay webhook requests with one click to iterate quickly while staying in context.

Run personal cloud services from your own private network

Own your data. Host personal cloud services on your own private network. Run webmail, file syncing, and more securely on your hardware with full end-to-end encryption.

Need to run ngrok in production? Use ngrok link to manage your IoT devices or as a lightweight alternative to VPN for targeted access into customer networks.

What's new in 2.0

ngrok 2.0 is a ground-up redesign focused on scale, speed, and reliability that makes it a solid piece that can be used from development through production. ngrok 2.0 introduces the most highly requested features including wildcard domains, reserved TCP addresses, vhost-targeting, end-to-end TLS tunnels, team accounts and more.

What's new in ngrok 2.0

ngrok features

Secure Tunnels

Instantly create a public HTTPS URL for a web site running locally on your development machine.

ngrok http 80


ngrok tunnels run using an optimized version of the technology that powers HTTP/2 so that your tunneled services load fast.

Password Protected

Set http auth credentials to protect access to your tunnel and those you share it with.

ngrok http -auth "user:password" 80

Websocket Support

Share your real-time web apps! ngrok tunnels websocket connections over HTTP tunnels without any changes.

ngrok http 8000

Replay Webhook Requests

Easily develop webhook integrations by simply 'replaying' webhook requests to your dev server.

Automate ngrok via API

Dynamically start, stop and query tunnel status all with a simple RESTful API.


Request Inspection

Use ngrok's web inspection interface to understand the HTTP request and response traffic over your tunnel.


No more port forwarding

Don't configure port forwarding on your router or waste time setting up dynamic DNS solutions. ngrok works everywhere with no changes, even when a device changes networks.

TCP Tunnels

Expose any networked service to the internet, even ones that don't use HTTP like SSH.

ngrok tcp 22

Multiple Simultaneous Tunnels

Run multiple tunnels simultaneously with a single ngrok client.

ngrok start demo-site ssh admin-ui

Target virtual-host sites

Rewrite the Host header of tunneled requests to target a specific site in your WAMP/MAMP/Pow development environment.

ngrok http 80

Shared account access for teams

Accounts can share access to reserved domains and addresses allowing multiple developers to collaborate on a project while still having their own credentials.

ngrok paid plans

Some features of the ngrok service are only available to customers using one of the paid plans. Features only available on paid plans are enumerated below.

Custom Subdomains

Your app will appear on instead of on a randomly chosen subdomain.

ngrok http -subdomain myapp 80

Tunnels on your own domains

Run tunnels over your own domain names! This requires a simple change to your DNS.

ngrok http -hostname 80

Reserved TCP Addresses

Reserve a unchanging IP and port exclusive for your use. Perfect for personal cloud services or anything you expose via ngrok TCP tunnels.

ngrok tcp --remote-addr 22

Wildcard domains

Tunnel HTTP requests for all of your subdomains to a local service with just a single command.

ngrok http -hostname * 8080

Reserved domains

Reserve your subdomains so that they are never provisioned to another user and are always available for your use.

End-to-End TLS Tunnels

Tunnel HTTPS (or other TLS) traffic to your local services end-to-end encrypted with your own SSL certificate and private key. You can even run them over your own domains!

ngrok tls -hostname 443

TLS Client Termination

Use ngrok's TLS tunnels with end-to-end encryption even if your local service doesn't support TLS termination by offloading it to the ngrok client!

ngrok tls -crt tls.crt -key tls.key 443

IP Whitelisting

Whitelist access to your tunnel endpoints by IP address or IP range for additional security of your tunneled services.

Developer time is expensive

Making it more productive is a no-brainer


$5 / mo

per user, billed annually

(not available monthly)

  • Custom subdomains
  • Reserved domains
  • Google Apps SSO
Per user limits
3 reserved domains
1 online ngrok process
8 tunnels per ngrok process
60 connections / minute


$8.25 / mo

per user, billed annually

($10 billed monthly)

Everything in Basic, plus . . .
  • Whitelabel domains
  • Reserved TCP addresses
  • End-to-End TLS Tunnels
Per user limits
5 reserved domains
2 reserved TCP addresses
2 online ngrok processes
12 tunnels per ngrok process
60 connections / minute


$12 / mo

per user, billed annually

($15 billed monthly)

Everything in Pro, plus . . .
  • IP whitelist tunnel access
  • Reserved wildcard domains
  • Priority Support
Per user limits
5 reserved domains
2 reserved TCP addresses
1 wildcard domain
2 online ngrok processes
20 tunnels per ngrok process
120 connections / minute

Free Plan

For quick demos and other simple tunneling needs.

  • HTTP/TCP tunnels on random URLs/ports
  • 1 online ngrok process
  • 4 tunnels per ngrok process
  • 40 connections / minute

Pricing and Limits FAQ

What is an 'online ngrok process'?

An 'online ngrok process' is a single running instance of the ngrok process connected to the service. Documentation and error messages sometimes refer to this as an 'ngrok client session'. You can run multiple tunnels over a single ngrok process.

How do the per-user limits work?

Limits to your ngrok account will be multiplied by the number of users. Examples:

Basic plan with 1 user
  • 3 reserved domains
  • 60 connections / minute
Basic plan with 3 users
  • 9 reserved domains
  • 180 connections / minute

Can you explain the connections / minute limit?

ngrok limits the number of inbound connections to your tunnel endpoints. Limits are imposed on connections, not requests. If your HTTP clients use persistent connections aka HTTP keep-alive (most modern ones do), you'll likely never hit this limit. ngrok will return a 429 response to HTTP connections that exceed the rate limit. Connections to TCP and TLS tunnels violating the rate limit will be closed without a response.

Can you explain the tunnels per process limit?

ngrok can run multiple tunnels over a single ngrok client session. The tunnels per process limit expresses how many tunnels you may run simultaneously over a single ngrok process.

None of your plans work for me! I need additional reserved domains, addresses, or transfer.

Not to worry! Email and we'll work out a custom plan.