Compare

CloudLink vs. ngrok and Cloudflare Tunnel

All three can put a local app on the internet. They are built for different jobs. CloudLink is a focused client preview environment; ngrok is a general-purpose ingress platform; Cloudflare Tunnel is infrastructure you configure inside Cloudflare.

Last reviewed November 2026. Providers change plans and features; check their current documentation before deciding.

The short version

CloudLink is the least configurable of the three, deliberately. It owns the tunnel, hostname, TLS, pairing, and client access policy so you can share a running app without assembling those parts. ngrok and Cloudflare Tunnel give you more networking control, and ask you to bring the account, configuration, and access layer.

DimensionCloudLinkngrokCloudflare Tunnel
Main focusClient previews for independent developersGeneral-purpose ingress and tunnelingInfrastructure-grade tunnels on Cloudflare
Account requiredCloudLink account (browser or OpenCode Mobile)ngrok accountCloudflare account and DNS (named tunnel)
Tunnel setupConnector, browser pairing, local approvalAgent and account configurationcloudflared plus dashboard or config
Stable public URLOne opaque hostname per paired machineDepends on plan and configurationYour hostname and DNS configuration
Client access controlsPrivate, password link, expiry, revocation built inConfigured separately by planConfigured separately, for example Cloudflare Access
Multiple local servicesDedicated HTTPS ports or path prefixesSeparate tunnels or endpointsSeparate hostnames and routes
OpenCode or agent integrationOptional built-in integration and local MCPNot part of the productNot part of the product
Best fitClient reviews, prototypes, live demosAd-hoc ingress, webhooks, debuggingOrganizations already standardised on Cloudflare

Choose CloudLink when…

Choose a general-purpose tunnel when…

CloudLink is not a replacement for a production hosting platform or a highly available ingress layer. It is for the review link between your local environment and your client.

Common questions

Is CloudLink an ngrok alternative?

For client previews, yes. Both can expose a local port over HTTPS. CloudLink adds a stable per-machine hostname, a browser account, approval-gated pairing, and built-in password, expiry, and revocation controls. ngrok remains a better fit for general-purpose ingress, webhook debugging, and infrastructure use cases.

Is CloudLink a Cloudflare Tunnel alternative?

It uses a managed Cloudflare Tunnel underneath. The difference is the product around it: CloudLink creates and supervises the tunnel, issues the hostname, enforces share access at the connector, and provides the account and pairing flow. You do not need a Cloudflare account or DNS configuration.

Do I need a Cloudflare account?

No. CloudLink provisions and supervises the named tunnel, DNS, and TLS. A Cloudflare account is only relevant if you choose to run your own Cloudflare Tunnel instead.

Can I use a custom domain?

The current product publishes generated m-<opaque>.opencodecloud.link hostnames. Custom domain mapping is not part of the documented product; use your own Cloudflare Tunnel if you need a domain you control.

Which one should I use for a client demo?

Use CloudLink when the job is showing a local app to a client with controlled access and a stable link. Use a general-purpose tunnel when you need arbitrary ingress, infrastructure automation, or custom networking that CloudLink does not provide.