ngrok
Secure tunnels to localhost for sharing and testing local servers.
Open the official app on ngrok.com
This tool is hosted by its maintainers. Click below to open ngrok.com in a new tab — it's their official demo.
Browse developer tools →What's next with ngrok?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is ngrok?
ngrok is a developer tool that securely exposes local servers, APIs, and AI models to the internet by creating temporary tunnels. It acts as an intermediary between local development environments and external networks, enabling testing, sharing, and integration without complex server configurations. Developers, DevOps teams, and enterprises use ngrok to bypass limitations of local network restrictions, allowing tools like webhooks, APIs, and machine learning models to interact with external services. The tool solves critical challenges in development workflows by providing secure, reliable access to localhost services, eliminating the need for public IP addresses or complex firewall setups. Its core value lies in simplifying the process of testing, debugging, and deploying applications in isolated environments while maintaining data security and observability.
How it works
ngrok is a proprietary tool that creates secure, tunneled connections between local development environments and the internet. It routes traffic through encrypted tunnels to protect sensitive data while allowing external access to localhost services. Its primary purpose is to enable developers to test, share, and integrate applications without exposing local infrastructure to public networks. This is particularly useful for APIs, AI models, and web apps that require external interaction during development. ngrok supports secure tunneling with TLS encryption, domain mapping for custom URLs, and integration with cloud platforms. It also provides features like AI Gateway for managing multiple machine learning models and observability tools for monitoring traffic patterns.
How to use it
- 1Download ngrok from the Microsoft Store or via command-line tools like WinGet or Scoop. 2. Obtain an authtoken from the ngrok dashboard and configure it using 'ngrok config add-authtoken'. 3. Start a tunnel by running 'ngrok http <PORT>' with your application's port number. 4. Access the generated public URL to test or share the service. Practical tips include using the Microsoft Store for secure installation, specifying the correct port for your app, and leveraging the 'ngrok http' command for quick setups. Always verify the authtoken's validity to avoid connection issues.
What it can do
- tunneling
Use cases
Assumptions and limitations
Assumptions
- source: https://ngrok.com/
- license: Proprietary — free to use
- privacy: Opens an external demo
Limitations
- Dependence on ngrok's cloud infrastructure for tunnel operation
- Potential latency or downtime if the service experiences outages
- Limited advanced networking features compared to enterprise-grade solutions
- Requires an authtoken for basic functionality, which may be a barrier for new users
- Cost considerations for enterprise-scale usage beyond free tier limits
Understanding the result
Secure tunnels to localhost for sharing and testing local servers.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (MIT).
- Built with
- (https://ngrok.com/)
- License
- MIT
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with https://ngrok.com/. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- MIT
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- Proprietary License
Upstream project
Frequently asked
What is ngrok and how does it differ from traditional tunneling tools?
ngrok is a proprietary tool that creates secure tunnels to expose local services to the internet, unlike traditional tools that often lack built-in encryption or domain management. It provides features like TLS encryption, custom domain mapping, and integration with cloud platforms, making it more robust for development and production workflows.
How does ngrok secure traffic between local services and the internet?
ngrok uses TLS encryption to secure all traffic between the local machine and its cloud servers. Data is encrypted end-to-end, ensuring sensitive information remains protected. The tool also supports HTTPS termination at its edge servers, preventing man-in-the-middle attacks while maintaining secure access to local applications.
How do I set up a tunnel for my local HTTP server on port 8080?
First, install ngrok via the Microsoft Store or command-line tools. Next, obtain an authtoken from the ngrok dashboard and run 'ngrok config add-authtoken <YOUR_TOKEN>'. Finally, execute 'ngrok http 8080' to create a tunnel. Your public URL will appear in the terminal, allowing external access to your local server.
How does ngrok compare to alternatives like localtunnel or ngrok's own enterprise solutions?
ngrok offers more advanced features than localtunnel, such as domain mapping, HTTPS termination, and enterprise-grade observability tools. Its enterprise solutions include features like AI Gateway and centralized traffic management, which are not available in free-tier alternatives. For users requiring full control, self-hosted ngrok instances provide greater customization but require more infrastructure management.
What should I do if ngrok fails to start with an 'invalid authtoken' error?
Verify your authtoken by checking the ngrok dashboard or re-generating it from your account settings. Ensure there are no typos when entering the token. If the issue persists, contact ngrok support or check the official documentation for troubleshooting steps related to authentication errors.