Cloudflare Tunnel
Alternative to ngrok
Best for
Teams already using Cloudflare that want secure remote access to internal apps and services
Cost
Free tier available; paid Zero Trust and enterprise plans add advanced access controls, logging, and policy features.
Summary
Securely exposes local services and private applications through Cloudflare’s global network without opening inbound firewall ports, with tight integration into Cloudflare Zero Trust.
Why Switch
Teams switch from ngrok when they want a more enterprise-oriented zero-trust tunnel with stronger policy controls and broader Cloudflare security integration.
Migration Playbook
- Export ngrok tunnel configuration by saving the ngrok.yml file, which includes tunnel names, local addresses, and authentication tokens. Map the 'addr' field in ngrok.yml to the 'origin' field in Cloudflare Tunnel configuration. Prepare to use Cloudflare's 'cloudflared' CLI for importing these settings.
- Create Cloudflare Tunnel configurations by translating ngrok tunnel definitions into Cloudflare Tunnel YAML format. For each ngrok tunnel, define a corresponding 'tunnel' with a unique name and specify the 'ingress' rules mapping the local service ports to Cloudflare's edge. Use the Cloudflare API or 'cloudflared tunnel create' commands to register tunnels under your Cloudflare account.
- Deploy the Cloudflare Tunnel connector locally by installing 'cloudflared' on the host machine. Authenticate using the generated credentials from Cloudflare, then start the tunnel using 'cloudflared tunnel run <tunnel-name>'. Verify that the local services are accessible through Cloudflare's network, replacing ngrok's public URLs with Cloudflare Tunnel endpoints.
Pros
- 🟢No inbound ports required
- 🟢Strong identity-aware access controls
- 🟢Easy to pair with Cloudflare DNS and WAF
- 🟢Good performance via Cloudflare edge network
Cons
- 🔴Best experience is tied to the Cloudflare ecosystem
- 🔴Some advanced features require paid plans
- 🔴Not a full replacement for every tunneling workflow
0 builders switched
Cloudflare Tunnel
Alternative to ngrok
Best for
Teams already using Cloudflare that want secure remote access to internal apps and services
Cost
Free tier available; paid Zero Trust and enterprise plans add advanced access controls, logging, and policy features.
Summary
Securely exposes local services and private applications through Cloudflare’s global network without opening inbound firewall ports, with tight integration into Cloudflare Zero Trust.
Why Switch
Teams switch from ngrok when they want a more enterprise-oriented zero-trust tunnel with stronger policy controls and broader Cloudflare security integration.
Migration Playbook
- Export ngrok tunnel configuration by saving the ngrok.yml file, which includes tunnel names, local addresses, and authentication tokens. Map the 'addr' field in ngrok.yml to the 'origin' field in Cloudflare Tunnel configuration. Prepare to use Cloudflare's 'cloudflared' CLI for importing these settings.
- Create Cloudflare Tunnel configurations by translating ngrok tunnel definitions into Cloudflare Tunnel YAML format. For each ngrok tunnel, define a corresponding 'tunnel' with a unique name and specify the 'ingress' rules mapping the local service ports to Cloudflare's edge. Use the Cloudflare API or 'cloudflared tunnel create' commands to register tunnels under your Cloudflare account.
- Deploy the Cloudflare Tunnel connector locally by installing 'cloudflared' on the host machine. Authenticate using the generated credentials from Cloudflare, then start the tunnel using 'cloudflared tunnel run <tunnel-name>'. Verify that the local services are accessible through Cloudflare's network, replacing ngrok's public URLs with Cloudflare Tunnel endpoints.
Pros
- 🟢No inbound ports required
- 🟢Strong identity-aware access controls
- 🟢Easy to pair with Cloudflare DNS and WAF
- 🟢Good performance via Cloudflare edge network
Cons
- 🔴Best experience is tied to the Cloudflare ecosystem
- 🔴Some advanced features require paid plans
- 🔴Not a full replacement for every tunneling workflow
0 builders switched