ngrok pricing depends on the plan, endpoint type, usage, domains, traffic, team members, and features you need. The free plan can handle many tests, but you should check current vendor pricing before you build a workflow around it.
The practical question is simple: do you need ngrok for webhook and tunnel development, or do you need a short-lived browser link for a review session?
ngrok pricing: what to check first
As of the current public pricing page fetched for this article, ngrok lists Free, Hobbyist, and Pay-as-you-go plans. The free plan includes a one-time usage credit, a cap on online endpoints, data transfer, HTTP/S requests, an interstitial page on HTTP/S endpoints, an assigned development domain, and one team member. Paid plans add more usage, remove some friction, and unlock more capacity or team features.
Treat those details as volatile. Vendor pricing pages change. Before you decide, check:
- How many endpoints can stay online at the same time.
- Data transfer included in the plan.
- HTTP/S request limits.
- TCP or TLS endpoint availability and verification steps.
- Whether an interstitial warning page appears for reviewers.
- Domain options, including development domains, branded domains, and custom domains.
- Team member limits and SSO or RBAC add-ons.
- Traffic inspection retention or log export costs.
For quick local testing, the free plan may be enough. For team workflows, persistent endpoints, custom domains, or heavier traffic, the cost model needs a closer read.
Is ngrok free?
Yes, ngrok has a free plan. Free does not mean unlimited. The current pricing page includes usage and endpoint limits, and it shows an interstitial page on HTTP/S endpoints. TCP endpoint use can require account verification steps, so check the docs for the endpoint type you plan to use.
That matters for client review. A developer may accept a warning page, a vendor-branded domain, or a usage cap during a technical test. A non-technical reviewer may stop at an interstitial page or ask why the link looks unfamiliar.
For webhook testing, ngrok’s docs and ecosystem make it a common default. For external stakeholder review, the buying criteria shift. You care less about protocol breadth and more about review length, viewer state, request failures, and what the reviewer sees.
Where ngrok costs can come from
ngrok pricing can involve several buckets:
| Cost driver | Why it matters |
|---|---|
| Online endpoints | More concurrent tunnels can require a higher plan |
| Data transfer | Large assets, video, or repeated QA sessions can consume transfer |
| HTTP/S requests | Automated tests and busy review links can hit request buckets |
| Domains | Custom and branded domains may change plan fit |
| Team members | Shared team use can move you out of solo plans |
| Observability | Retention and exports can matter for audit-heavy teams |
| Advanced security | SSO, RBAC, mTLS, and policy features may cost more |
The right answer may still be ngrok. If you test webhooks, expose TCP services, need custom domains, or want a mature tunnel product with broad docs, ngrok earns its place.
If the job is “send this local page to a client for 30 minutes,” a different cost model may fit better.
Review links need different pricing logic
A review link has a short life. It should exist for the review window, then close. It should give the reviewer a browser URL and give the developer enough visibility to handle failures.
wiremaven focuses on that workflow. It creates temporary encrypted public links for local dev servers. Your machine opens an outbound-only WebSocket connection to the relay. The reviewer gets a browser link. The developer sees viewer joins, request outcomes, failures, and the remaining session time.
npx wiremaven-cli 3000 --expires 30m --name pricing-reviewDuring beta, wiremaven requires no account. Review windows support 15, 30, and 60 minute TTLs. That keeps the default unit close to the job: a controlled local review session.
That does not make wiremaven a drop-in replacement for every ngrok use case. If you need persistent endpoints, broad TCP workflows, custom domain operations, or long-term traffic policy, compare vendor docs and pricing. If you need a client to open your current local build, start with a review-focused tunnel.
Decision checklist
Ask these before you choose:
- Does the reviewer need a plain HTTPS browser link?
- Will the session end in 15, 30, or 60 minutes?
- Do you need request and failure signals during the review?
- Do you need webhook inspection or traffic replay?
- Do you need TCP, TLS, custom domains, or team access controls?
- Will traffic volume or automated tests affect plan limits?
If most answers point to protocols, domains, and long-running operations, check ngrok’s current pricing page. If most answers point to a short-lived browser review, check wiremaven.
For wiremaven setup, read the docs. For the relay flow, see how wiremaven works.
FAQ
Is ngrok free?
ngrok offers a free plan, but it has limits. Check current vendor pricing for endpoint counts, usage, data transfer, request limits, domains, and warning pages.
Does ngrok show a warning page?
The current pricing page lists an interstitial page on HTTP/S endpoints for the free plan. Check ngrok’s pricing page before relying on that detail.
What should I use instead of ngrok for client reviews?
Use a tunnel built around temporary review sessions. wiremaven gives reviewers a browser link and gives developers viewer, request, and failure signals.
Does wiremaven require an account?
During beta, wiremaven does not require an account. It supports 15, 30, and 60 minute TTLs for review links.
Try a short-lived review link
Start your local app and create a 30 minute link:
npx wiremaven-cli 3000 --expires 30mRelated: 7 ngrok Alternatives for Developers in 2026 | ngrok vs. localtunnel vs. wiremaven | How to Share Localhost with a Client