Pricing and Limits

Learn about the pricing, limits, and licensing model for the paid ngrok for production plans.

​

Limits and licensing

For the most complete limits and pricing information, please see the ngrok Pricing page.

​

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 Free and Hobbyist, you can have up to 3 online endpoints. On the Pay-as-you-go plan, there is no limit on the number of online endpoints. An endpoint that has outgoing traffic during a clock hour is counted as an active endpoint for that hour and charged one endpoint hour. Free and Hobbyist plans allow you to use your included credit to start endpoints.

​

Wildcard endpoints

Wildcard endpoints allow you to create a single endpoint that receives traffic for all subdomains matching a wildcard endpoint pattern, such as *.example.com. For example, if you create the wildcard endpoint https://*.example.com, it will receive traffic for https://foo.example.com, https://bar.example.com, and any other matching subdomains.

​

Billing for wildcard endpoints

For any wildcard endpoint you create, you will be charged one endpoint hour for the wildcard endpoint itself, regardless of how many subdomains match the wildcard pattern or how many internal endpoints the wildcard endpoint forwards traffic to.

​

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 the forward-internal action), billing works as follows:

• Endpoint hours: You are charged one endpoint hour for the wildcard Cloud Endpoint. The internal endpoints that receive forwarded traffic do not incur additional endpoint hour charges, as they are internal-only endpoints.
• Traffic Policy (TP): Traffic Policy actions executed on the wildcard Cloud Endpoint are charged according to standard Traffic Policy Unit (TPU) pricing. This includes any actions used to route or forward traffic to internal endpoints.
• Individual endpoints vs. wildcard endpoints: If you create individual endpoints for specific subdomains (for example, https://api1.example.com and https://api2.example.com) instead of using a wildcard endpoint, each individual endpoint or wildcard endpoint will be charged separately for endpoint hours.

For more information on creating and using wildcard endpoints, see the wildcard endpoints documentation.

​

How to see how your account stacks up against your limits

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 allows you to pay only for the resources you use, without any upfront commitment. It is ideal for production workloads that require scalability and flexibility.

​

How does the Pay-as-you-go plan work?

You are charged based on your actual usage of ngrok resources, such as data transfer, endpoints, and connections. There are no fixed monthly fees, and you can scale your usage up or down as needed.

​

Why are there two invoices for each billing cycle?

The Pay-as-you-go plan generates two invoices: one for the base fee and another for the usage-based charges. This allows you to see your fixed costs separately from your variable costs.

​

ngrok’s free plan

Features included for free on all plans:

• HTTPS Tunnels
• HTTPS Edges
• Web Inspection Agent
• Replay Requests
• ngrok SDKs
• ngrok Kubernetes Operator
• Remote Agent Management
• Circuit Breaking
• Automatic Certificates and Encryption
• Email Support