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.
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.
| Dimension | CloudLink | ngrok | Cloudflare Tunnel |
|---|---|---|---|
| Main focus | Client previews for independent developers | General-purpose ingress and tunneling | Infrastructure-grade tunnels on Cloudflare |
| Account required | CloudLink account (browser or OpenCode Mobile) | ngrok account | Cloudflare account and DNS (named tunnel) |
| Tunnel setup | Connector, browser pairing, local approval | Agent and account configuration | cloudflared plus dashboard or config |
| Stable public URL | One opaque hostname per paired machine | Depends on plan and configuration | Your hostname and DNS configuration |
| Client access controls | Private, password link, expiry, revocation built in | Configured separately by plan | Configured separately, for example Cloudflare Access |
| Multiple local services | Dedicated HTTPS ports or path prefixes | Separate tunnels or endpoints | Separate hostnames and routes |
| OpenCode or agent integration | Optional built-in integration and local MCP | Not part of the product | Not part of the product |
| Best fit | Client reviews, prototypes, live demos | Ad-hoc ingress, webhooks, debugging | Organizations already standardised on Cloudflare |
Choose CloudLink when…
- You want a client to open a working app from your machine today.
- You want a stable link instead of a new random URL for every session.
- You want password, expiry, and revocation controls without configuring an identity provider.
- You want OpenCode or an AI coding agent available alongside the preview.
- You do not want to manage a Cloudflare account, DNS record, or tunnel configuration.
Choose a general-purpose tunnel when…
- You need arbitrary ingress for webhooks, APIs, or infrastructure automation.
- You need a custom domain or a networking model CloudLink does not expose.
- You already run Cloudflare and want tunnels managed as part of your infrastructure.
- You need the provider's own plan, support, and regional controls.
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.