Skip to content

Features

Cloud Link is more than a tunnel. Use this page to find the guide for the outcome you need.

  • Pairing with approval — scan a single-use QR code and approve the device on the machine before the tunnel starts.
  • Per-device credentials — each phone receives a signed, machine-scoped credential with an expiry.
  • Remote browser access — give a browser its own username and password, separate from the phone.
  • Stable address — keep one opaque hostname across re-pairs, restarts, and upgrades.
  • Supervised reconnects — survive logins, reboots, and network changes with capped retries and a visible Retry action.
  • Exposed services — publish a loopback dev server, API, or dashboard through the same tunnel.
  • Private by default — require a Cloud Link credential unless you explicitly mark a service public.
  • Separate origin — services use their own port and origin, so OpenCode paths and credentials are not mixed with them.
  • Live changes — add, edit, enable, or disable a service without restarting the tunnel.

OpenCode Cloud Link is an independent project. It is not built by the OpenCode team and is not affiliated with them in any way. See thePrivacy Policy andTerms & Conditions.