Teitunnel

Docs

Teitunnel vs ngrok

Teitunnel and ngrok compared — free plan limits, the browser warning page, custom domains, request inspection and logins — and how to move from ngrok commands to Teitunnel.

ngrok is a hosted tunnel service with its own network, a polished agent and many paid features. Teitunnel is a free app for Cloudflare Tunnel: your shares and routes run on Cloudflare, on your own account.

Teitunnelngrok Free
Pricefree, open sourcefree; paid from $10/month
Trafficno cap on tunnel traffic1 GB out and 20,000 HTTP requests a month
Endpoints online at onceno limit of Teitunnel's3
Addressrandom trycloudflare.com, or any name on your domainone assigned *.ngrok-free.app domain
Your own domainfree, once it's on Cloudflarepaid plans
Warning page for browsersnone on your domainyes, until visitors click through
Inspect and replaythe inspector, in the app and teitunnel trafficlocalhost:4040, with replay
LoginsCloudflare Access, free up to 50 usersOAuth and OIDC
Desktop appmacOS, Windows, Linuxno

Checked 2026-09-26

From ngrok's pricing, free plan limits and inspection interface. ngrok's pages are the final word.

The warning page

On ngrok's free plan, a browser opening your address first sees ngrok's warning page and has to click through; scripts can skip it with an ngrok-skip-browser-warning header. A share on your own domain with Teitunnel shows your site straight away, which matters for demos, previews sent to clients, and webhooks from services that load the page in a browser.

From ngrok commands

ngrokTeitunnel
ngrok http 3000teitunnel share 3000
ngrok http 3000 --url app.yourhost.comteitunnel share 3000 --on app.yourhost.com
ngrok http 3000 --traffic-policy-file policy.yml with an OAuth actionteitunnel share 3000 --on app.yourhost.com --allow you@yourhost.com
localhost:4040, ReplayInspector in the app, or teitunnel traffic ls and teitunnel traffic replay
ngrok.yml endpointsteitunnel.yml in your repository, or routes
an always-on agent serviceKeep running when Teitunnel quits (run modes)

When ngrok fits better

  • Your domain can't move its nameservers to Cloudflare, and you need your own name.
  • You use ngrok's other products, such as its API gateway and Traffic Policy features, and want them in one place.
  • Your company already pays for ngrok and manages access there.
Edit on GitHub

Last updated on

On this page