ngrok

Overview

ngrok is a cloud networking platform for routing traffic to services wherever they run. It suits developers who need to expose a service without changing firewall settings, and teams that need request controls across different protocols. Its strongest case is the combination of tunnels, traffic policies, and broad protocol support; its main drawback for smaller plans is that usage caps can interrupt service.

Key features

Tunnels and traffic policy

The ngrok agent connects services through a secure tunnel, avoiding firewall changes. Its CEL-based Traffic Policy can route or authenticate requests, apply rate limits and web application firewall controls, or reject traffic. Those controls make ngrok more useful than a tunnel alone when a service needs request-level protections; teams that do not need them may not benefit from that added flexibility.

Protocols and integrations

ngrok supports HTTP, TLS, and TCP traffic, including WebSockets, gRPC, SSH, Postgres, MQTT, and Minecraft. That breadth suits both ordinary web services and less typical workloads such as database connections or game servers. The Integrations Hub includes guides and integrations for SSO, databases, event destinations, frameworks, Kubernetes, OAuth, protocols, webhooks, and web servers. It also verifies webhook signatures for more than 70 providers, including Stripe, GitHub, Bitbucket, Twilio, Slack, and Shopify.

Security and regional controls

Agent-to-edge connections use TLS 1.2 or higher, and ngrok encrypts databases, filesystems, and data warehousing at rest. It states that it is SOC 2 Type 2 compliant, supports HIPAA deployments and BAAs, complies with GDPR and CCPA, and participates in the EU-US Data Privacy Framework. Region pinning and points of presence across the United States, Europe, Asia Pacific, Australia, India, Japan, and South America give teams options for placing traffic closer to users or within a chosen region.

Paid support options include Dedicated On-Call with an eight-business-hour SLA, plus Slack or Teams support and 24×7 paging add-ons. Those options can matter for production services that need escalation paths, but they add to the cost beyond the base plan.

Pricing

ngrok uses a freemium model. The Free plan costs 0.00 USD per free, with one-time included usage of $5, up to 3 online endpoints, 1GB of data transfer, 20k HTTP/S requests, and one team member. It is suited to solo experimentation and light development, but the limited transfer and request allowances make it a poor fit for a service that must remain available under unpredictable traffic. When Hobbyist usage credit runs out, endpoints stop working until the billing cycle ends and the credit resets.

Hobbyist costs 10.00 USD per month, billed monthly. It includes $10 monthly usage, up to 3 online endpoints, 5GB of data transfer, 100k HTTP/S requests, and one team member. This is a modest step up for an individual developer, home lab, or game server, but the same endpoint and seat limits constrain collaboration, and exhausted credit still means endpoints stop until reset.

Pay-as-you-go costs 20.00 USD per month, billed monthly plus additional usage. Its $20 monthly included usage comes with unlimited online endpoints, data transfer, HTTP/S requests, and team members. That makes it the clearer fit for teams shipping production traffic, though additional usage means the monthly price is not necessarily the total bill.

Enterprise has custom pricing and is billed by contract. It adds SSO/SAML and SCIM, SLAs with dedicated support, HIPAA and SOC 2, BAAs, AWS Marketplace, and per-device or per-customer pricing. It is aimed at organizations with compliance, support, or deployment-pricing needs that exceed the self-service plans.

Platforms

ngrok supports API, Linux, macOS, self-hosted, web, and Windows environments. It supports both cloud and self-hosted deployment, with both GUI and code-based configuration options. That range gives teams flexibility across development and deployment environments rather than tying the service to a single operating system or setup style.

Who it's for

ngrok is a strong fit for developers and solo users exposing development services, home labs, or game servers, especially when firewall changes are undesirable. Teams can use it for production traffic when they need broad protocol support, request policies, or regional controls. The Free and Hobbyist limits make those plans less suitable for workloads that cannot tolerate endpoints stopping after usage credit is exhausted; teams with ongoing production traffic are better served by Pay-as-you-go or Enterprise.

Pros and cons

• Pro: Secure tunnels avoid firewall changes, while Traffic Policy adds authentication, rate limiting, WAF controls, and request rejection.
• Pro: Support for HTTP, TLS, TCP, and protocols including gRPC, SSH, Postgres, MQTT, and WebSockets serves more than conventional web traffic.
• Pro: Webhook signature verification covers more than 70 providers, reducing the need to handle provider-specific verification separately.
• Con: Free and Hobbyist plans have finite request and transfer quotas, and Hobbyist endpoints stop when usage credit is depleted until the next billing-cycle reset.
• Con: Free and Hobbyist allow only one team member, while the Free and Hobbyist plans also cap online endpoints at three.
• Con: Pay-as-you-go adds charges for additional usage, so its $20.00 USD per month starting price does not set a ceiling on spend.

Alternatives

For Kubernetes-focused ingress, compare Kubernetes Ingress Controllers; for broader reverse-proxy options, browse Reverse Proxy Software.

• Traefik Proxy is a free, open-source ingress controller, reverse proxy, and load balancer with service auto-discovery; choose it when those roles are the priority.
• Apache APISIX is a free option for API, Linux, and self-hosted environments.
• Kusk Gateway is a free option available across web, Windows, macOS, and Linux.
• agentgateway is a free open-source gateway deployable as a binary, Docker container, or Kubernetes workload; choose it when that deployment flexibility is central.
• Airlock Microgateway offers a free Community Edition for small environments or local development, with enforced throughput and six-month license validity.
• Contour is a free, self-hosted Kubernetes ingress controller with community support.
• HAProxy Ingress is a free Linux and self-hosted option that requires a Kubernetes cluster; v0.16 requires Kubernetes 1.21 or newer.
• kgateway is a free Linux and self-hosted option, with a separate Solo Enterprise offering at custom pricing.

Verdict

Choose ngrok if you need secure tunnels plus configurable request controls across a wide range of traffic types, particularly for development or production services with varied protocols. Its regional options and security commitments add value for teams with compliance or placement needs. Look elsewhere if you need dependable service on a tightly capped plan: Free and Hobbyist endpoints stop when their credit runs out, while production-scale usage belongs on a plan with additional monthly charges or custom Enterprise terms.