ngrok
- Free allowance
- 1 GB out, 20,000 HTTP requests and 5,000 TCP connections per month; 3 endpoints
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- emailcard required, no phone
- Binding limit
- volume-quota1 GB per month of data transfer out; 20,000 HTTP requests, 5,000 TCP connections, 10,000 log events and 500 webhook verifications per month
- Evidence
- documented3 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | 1 GB out, 20,000 HTTP requests and 5,000 TCP connections per month; 3 endpoints unit GB; metered on downloaded-bytes |
|---|---|
| Price | none stated |
| Limits |
the allowance is a byte volume over a period, which none of the six kinds names; the number is in egress.free_allowance and binding names per-ip-shaping as the nearest kind. counts of things, not rates, so no vocabulary kind names them: 3 online endpoints and one dev domain per account |
| Binding | volume-quota 1 GB per month is about 1,100 times below 1 TiB, so the byte quota fails first by three orders of magnitude. The docs state the consequence as an upgrade recommendation rather than a throttle: once a limit is hit or the credit is gone, the endpoints stop being always available and the recommendation is to move to pay-as-you-go. |
| Identity | email an ngrok account; TCP tunnels need a card on file |
| Egress | metered at 1 GB/month, which is 33.3 MiB/day free allowance: 1 GB/month price per tb: USD 0.10/GB |
| Per-object cap | not applicable: counted per month rather than per object |
| Interface | cli, rest ngrok http; the dev domain is <name>.ngrok-free.app |
| Tooling | part of the text of Interface, above |
| Composes with | composes with an origin and no domain; the 1 GB monthly allowance is what stops it being the front of anything served. |
| Reliability | an interstitial page intercepts HTML browser traffic on the free tier |
| Notes | The record merged rate and quota into one request-rate entry. The docs separate three kinds of limit and the rate row is a distinct constraint that binds before the monthly count on a burst. Replaces the note about the vocabulary with the ratio and the documented consequence. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | ngrok.com/docs/pricing-limits/free-plan-limits | Data transfer out 1 GB/month, 20,000 HTTP requests/month, 5,000 TCP connections/month, 3 endpoints and one dev domain |
| 2026-10-23 | ngrok.com/compare/wireguard | 'No. ngrok supports HTTP, HTTPS, TCP, and TLS endpoints.' |
| 2026-10-23 | ngrok.com/docs/gateway/endpoints/protocols | endpoints are limited to http, https, tcp and tls |
More fields 4
| stale after days | 180 |
|---|---|
| bytes transit | yes |
| transit note | the agent dials out and ngrok's edge relays the bytes, which is what the 1 GB monthly counter counts |
| ingress | none |