How it works

From localhost to client-ready in three steps.

CloudLink turns a local app into a secure HTTPS link. Nothing is deployed: the connector forwards the service you choose, while the code and environment stay on your machine.

Before you start

You need a machine that can stay online, an app listening on loopback, and a CloudLink account. The subscription is€2.99 per month during the current offer (regular price €7.99 per month); start it in the browser atapp.opencodecloud.linkor through OpenCode Mobile. No deployment target, hosting account, or Cloudflare account is involved. The price shown by Stripe or the app store at checkout governs.

The three steps

  1. 01

    Run your application locally

    Start the dev server, API, or prototype the way you normally do. It only needs to listen on loopback (127.0.0.1 or ::1). Keep the terminal running; CloudLink forwards the process you already have, not a copy of it.

    # any framework works
    npm run dev
    
    # example output
    Local: http://localhost:5173
  2. 02

    Create a CloudLink tunnel

    Create an account in the browser, subscribe, and install the connector on the same machine. Pair it through the browser activation link or the OpenCode Mobile QR code, then approve the machine locally. Add the running port as a service and choose a public HTTPS port.

    # macOS: install the DMG, then open the tray app
    # Windows: run the installer, then open the tray app
    # Linux:
    tar -xzf opencode-cloudlink_linux_amd64.tar.gz
    cd opencode-cloudlink_linux_amd64
    ./opencode-cloudlink run --no-opencode
  3. 03

    Share the link with your client

    Choose an access mode — private, password protected, or public link — set an expiry if the review is time-boxed, and send the generated HTTPS URL. The client opens it in a normal browser without installing anything.

    https://m-7f3a91c2.opencodecloud.link:8443/
    
    # private by default
    # password and expiration optional

Working with a Git project? The desktop app's Projects tab can save the repository folder and foreground start command, then start and expose the app when you choose. SeeProjects.

What happens behind the scenes

The connector starts a local authenticated proxy in front of your chosen service. A managed Cloudflare Tunnel publishes that proxy on a stable, opaque hostname and one of Cloudflare's supported HTTPS ports. Access is checked at the connector on every request before traffic reaches your app. Cloudflare terminates TLS at its edge; there is no separate application-layer encryption.

Targets must be loopback addresses. New services start disabled and private. A private service requires a CloudLink device or browser credential; a public-link service is reachable by anyone with the URL; a password-protected service also requires the visitor password. The control plane stores connection and billing metadata, not your source, prompts, or provider credentials.

Read Security and privacy for the full model and Exposed services for the field reference.

OpenCode is optional

Run the connector with the integration off and it exposes only local services. Turn it on when you want a managed or adopted OpenCode server, the OpenCode web UI window, phone pairing, or the local agent MCP. Existing OpenCode Mobile users keep their subscription, machines, and documentation.

Common questions

Do I need to deploy the app?

No. CloudLink publishes the app that is already running on your machine. The machine and connector must stay online while the client uses the link.

Do I need OpenCode or OpenCode Mobile?

No. Use the browser account console to create an account, subscribe, install the connector, and activate the pairing. OpenCode and OpenCode Mobile are optional integrations for agent workflows.

Do I need a Cloudflare account?

No. CloudLink provisions and supervises a managed named tunnel, including DNS and TLS. There is no Cloudflare account, tunnel, or DNS record to configure.

Which local address should I expose?

Use the loopback address and port your app prints when it starts, for example 127.0.0.1:5173. CloudLink rejects hostnames, private network ranges, and cloud metadata addresses.

How do I stop a client from accessing the link?

Revoke sharing, change the visitor password, disable the service, or delete the machine. Revoking a managed share invalidates its link and visitor sessions for that policy revision.

Can I use CloudLink with OpenCode?

Yes. Keep the integration enabled to manage or adopt an OpenCode server, open the OpenCode web UI, pair OpenCode Mobile, and let a local agent manage services through MCP. The sharing workflow is the same.