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.
Don’t constantly redeploy your in-progress work to get feedback from clients. ngrok creates a secure public URL (https://yourapp.ngrok.io) to a local webserver on your machine. Iterate quickly with immediate feedback without interrupting flow.
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.
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.
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.
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.
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.
Set http auth credentials to protect access to your tunnel and those you share it with.
ngrok http -auth "user:password" 80
Share your real-time web apps! ngrok tunnels websocket connections over HTTP tunnels without any changes.
ngrok http 8000
Easily develop webhook integrations by simply 'replaying' webhook requests to your dev server.
Dynamically start, stop and query tunnel status all with a simple RESTful API.
Use ngrok's web inspection interface to understand the HTTP request and response traffic over your tunnel.
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.
Expose any networked service to the internet, even ones that don't use HTTP like SSH.
ngrok tcp 22
Run multiple tunnels simultaneously with a single ngrok client.
ngrok start demo-site ssh admin-ui
Host header of tunneled requests to target a specific site in your WAMP/MAMP/Pow development environment.
ngrok http -host-header=mysite.dev 80
Accounts can share access to reserved domains and addresses allowing multiple developers to collaborate on a project while still having their own credentials.
Some features of the ngrok service are only available to customers using one of the ngrok.com paid plans. Features only available on paid plans are enumerated below.
Your app will appear on
https://myapp.ngrok.io instead of on a randomly chosen subdomain.
ngrok http -subdomain myapp 80
Run tunnels over your own domain names! This requires a simple change to your DNS.
ngrok http -hostname tun.yourdomain.com 80
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 1.tcp.ngrok.io:21011 22
Tunnel HTTP requests for all of your subdomains to a local service with just a single command.
ngrok http -hostname *.yourname.com 8080
Reserve your ngrok.io subdomains so that they are never provisioned to another user and are always available for your use.
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 yourdomain.com 443
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
Whitelist access to your tunnel endpoints by IP address or IP range for additional security of your tunneled services.
For quick demos and other simple tunneling needs.
An 'online ngrok process' is a single running instance of the ngrok process connected to the ngrok.com service. Documentation and error messages sometimes refer to this as an 'ngrok client session'. You can run multiple tunnels over a single ngrok process.
Limits to your ngrok account will be multiplied by the number of users. Examples:
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.
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.