ngrok

ngrok is a cloud networking and developer tool that creates secure public endpoints for applications, APIs, websites, and network services running on a local Windows PC.



It is particularly useful for developers who need to share localhost projects, test webhooks, demonstrate unfinished applications, or provide temporary remote access without configuring routers, firewalls, port forwarding, or public IP addresses.

The Windows agent establishes an encrypted outbound connection between the computer and ngrok’s globally distributed cloud network.

Incoming requests sent to the generated public address are then forwarded to the selected local port.

Because the connection starts from the computer, ngrok can normally operate behind NAT, corporate firewalls, and dynamic IP connections.

Although it is commonly described as a tunneling utility, it also provides API gateway, traffic management, authentication, request inspection, domain management, and production ingress capabilities.



The FileHorse dev team recommends ngrok as a practical solution for developers who regularly test web applications, integrations, and externally triggered services.

Features

• Secure Public Endpoints: Exposes local HTTP, HTTPS, TCP, and supported TLS services through public addresses.
• Automatic HTTPS: Protects web endpoints with automatically managed encryption certificates.
• Localhost Sharing: Makes development websites available to clients, colleagues, or testing devices.
• Webhook Testing: Receives callbacks from payment platforms, messaging services, repositories, and other external APIs.
• Traffic Inspector: Displays incoming HTTP requests, headers, response details, and timing information.
• Request Replay: Resends captured requests without requiring the external service to trigger them again.
• Custom Domains: Paid plans can connect endpoints to domains owned by the user.
• Traffic Policies: Applies authentication, routing, header modification, redirects, rate controls, and other traffic rules.
• OAuth and OIDC Protection: Restricts access by requiring visitors to authenticate through supported identity providers.
• TCP Forwarding: Provides remote access to services such as SSH, databases, game servers, and development devices.
• Agent Management: Allows connected agents and endpoints to be monitored from a central dashboard.
• SDK and Infrastructure Support: Integrates with application code, APIs, Kubernetes environments, and automated deployment workflows.

User Interface

ngrok is primarily operated through Command Prompt, PowerShell, or Windows Terminal.

Its command-line interface is compact and easy to understand once the account token has been configured.

Starting a basic endpoint normally requires only one command containing the protocol and local port.

A browser-based dashboard complements the Windows agent by displaying endpoints, domains, account usage, credentials, traffic policies, and connected agents.

The local inspection interface is especially useful during development because it organizes captured requests and responses in a readable format.

Beginners may need time to learn command-line options, configuration files, and networking concepts. However, routine localhost sharing remains simple.

Installation and Setup

It can be installed through the Microsoft Store, WinGet, Scoop, or as a standalone Windows executable.

The standalone version does not require a large installer or additional runtime package.

After installation, users must create an account and add their personal authentication token to the agent.

This connects the Windows installation to the user’s account and enables assigned domains, usage tracking, and endpoint management.

The basic configuration command is:

ngrok config add-authtoken YOUR_TOKEN

Once authorization is complete, ngrok is ready to expose a local service.

How to Use

• Install ngrok on the Windows PC.
• Open PowerShell, Command Prompt, or Windows Terminal.
• Add the account authentication token using the configuration command.
• Start the local website, API, or application that you want to expose.
• Identify the local port used by the application, such as 3000, 5000, 8000, or 8080.
• Enter a command such as ngrok http 8080.
• Copy the generated HTTPS forwarding address shown in the terminal.
• Open the public address in a browser or add it to the external service being tested.
• Review incoming requests through the inspection interface when debugging webhooks or APIs.
• Press Ctrl+C in the terminal when you want to close the endpoint.

FAQs

Is ngrok free?
Yes. A Free plan is available for personal development and testing. It includes an assigned development domain, up to three online endpoints, 1 GB of monthly outgoing data transfer, and up to 20,000 HTTP or HTTPS requests.

Can ngrok expose a localhost website?
Yes. Running a command such as ngrok http 3000 creates a public address that forwards requests to the application using local port 3000.

Does ngrok require port forwarding?
No. The agent creates an outbound encrypted connection, so users generally do not need to modify router settings or obtain a static public IP address.

Can ngrok be used for production applications?
Yes, but production workloads normally require a paid plan, appropriate traffic policies, access controls, monitoring, and carefully planned usage limits.

Is it safe to use ngrok?
The connection is encrypted, but exposing any local service creates potential security risks. Users should protect private endpoints with authentication, access restrictions, and secure application settings.

Pricing

Free: $0 with limited monthly traffic, requests, endpoints, and one account member.

Hobbyist: $10 per month or $8 per month when billed annually, with monthly usage credit, higher limits, additional ngrok-branded domains, and removal of the browser interstitial page.

Pay-as-you-go: Starts at $20 per month with included usage, unlimited online endpoints, support for custom domains, additional team members, and usage-based charges beyond the included allowance.

Advanced identity management, dedicated connectivity, enhanced support, custom certificates, and enterprise compliance options may cost extra.

System Requirements

• Operating System: Windows 10 or Windows 11.
• Architecture: 64-bit x86 or supported ARM64 Windows device.
• Processor: Modern Intel, AMD, or ARM-compatible processor.
• Memory: Minimal RAM usage for the agent; additional memory depends on the local application.
• Storage: Small amount of free space for the executable and configuration files.
• Internet Connection: Required for connecting the agent to the cloud network.
• Account: Required for an authentication token and endpoint management.
• Terminal: PowerShell, Command Prompt, or Windows Terminal recommended.

PROS

• Creates public endpoints within seconds.
• Does not require router port forwarding.
• Includes automatic HTTPS encryption.
• Excellent for webhook testing.
• Provides request inspection and replay.
• Works behind NAT and many firewalls.
• Supports development and production workflows.

CONS

• Requires an online account.
• Primarily controlled through a command line.
• Free usage limits may be restrictive.
• Public endpoints can expose insecure local apps.
• Advanced features require paid plans.
• Usage-based pricing can become difficult to estimate.
• Some networking knowledge is needed for complex setups.

Conclusion

ngrok is a powerful Windows networking utility for exposing local applications, testing webhooks, sharing development projects, and securely routing external traffic.

Its straightforward commands make basic tunneling accessible, while traffic policies, authentication, custom domains, and gateway features support more advanced deployments.

Free limits are best suited to testing rather than sustained production traffic.