Pricing
Learn about the pricing, limits, and licensing model for ngrok’s paid production plans.Limits and licensing
For the most complete limits and pricing information, see the ngrok Pricing page.Add-on pricing
These features are available as add-ons on the Pay-as-you-go plan:Custom TLS certificates are billed once per certificate for any hour in which at least one endpoint using that certificate is active.
Endpoints on domains covered by the same wildcard certificate (for example,
foo.acme.com and bar.acme.com under a *.acme.com certificate) share one certificate charge, but each hostname still accrues its own endpoint hours—see TLS certificates pricing.You can check your usage in the ngrok dashboard.
Refreshing limits
Your usage refreshes on the first day of each month.Endpoint limits
Your endpoint limit is the number of endpoints you can have online at the same time. On the Free and Hobbyist plans, you can have up to 3 online endpoints. On the Pay-as-you-go plan, there’s no limit on the number of online endpoints. An endpoint that has outgoing traffic during a clock hour counts as active for that hour and accrues one endpoint hour. Free and Hobbyist plans allow you to use your included credit to start endpoints.Wildcard endpoints
Wildcard endpoints let you create a single endpoint that receives traffic for every subdomain that matches a pattern, such as*.example.com.
For example, if you create the wildcard endpoint https://*.example.com, it receives traffic for https://foo.example.com, https://bar.example.com, and any other matching subdomains.
Billing for wildcard endpoints
A wildcard endpoint isn’t billed as a single endpoint. You’re charged endpoint hours for each hostname that receives traffic through the wildcard endpoint, as if each hostname were its own endpoint. For example, requests tohttps://a.example.com and https://b.example.com are billed the same whether they’re served by the wildcard endpoint https://*.example.com or by two separate endpoints.
Wildcard Cloud Endpoints forwarding to internal endpoints
When you use a wildcard Cloud Endpoint that forwards traffic to multiple internal endpoints using Traffic Policy actions (such as theforward-internal action), billing works as follows:
- Endpoint hours: You’re charged endpoint hours for each hostname that receives traffic through the wildcard Cloud Endpoint. The internal endpoints that receive forwarded traffic don’t accrue additional endpoint hours because they’re internal-only.
- Traffic Policy: Traffic Policy actions that run on the wildcard Cloud Endpoint are billed at standard Traffic Policy Unit (TPU) pricing. This includes actions that route or forward traffic to internal endpoints.
-
Individual endpoints vs. wildcard endpoints: Endpoint hours are the same whether you create individual endpoints for specific subdomains (for example,
https://api1.example.comandhttps://api2.example.com) or serve them through a wildcard endpoint. Each hostname that receives traffic is billed separately either way.
Check your usage
To see how your usage compares to your limits, go to the Usage page in the dashboard.Pay-as-you-go FAQs
What is the Pay-as-you-go plan?
The Pay-as-you-go plan is a flexible pricing model that lets you pay only for the resources you use, without any upfront commitment. It’s ideal for production workloads that require scalability and flexibility.How does the Pay-as-you-go plan work?
You pay a $20 per month base fee that includes $20 in usage covering data transfer, endpoints, connections, and other resources. Usage beyond the included amount is billed monthly based on actual consumption. You can scale your usage up or down as needed.Is bandwidth generated by malicious traffic counted toward usage?
The ngrok cloud service automatically protects all endpoints from attacks with its DDoS Firewall. Bandwidth generated before an attack is detected may count toward the usage-based portion of your Pay-as-you-go invoice.Free plan
Monthly usage quotas: these reset at the start of each monthly billing cycle.
Rate limits: the maximum sustained throughput at any moment, separate from the monthly quotas above.
Concurrency and account limits: these apply at all times, not per month.
Free plans include HTTPS endpoints with automatic TLS certificates and encryption. The TLS endpoints row above refers to raw TLS endpoints that you terminate yourself, which require a paid plan.
- HTTPS Tunnels
- Web Inspection Agent
- Replay Requests
- ngrok SDKs
- ngrok Kubernetes Operator
- Remote Agent Management
- Circuit Breaking
- Automatic Certificates and Encryption
- Email Support