> Documentation index: https://jetkvm.com/llms.txt

# JetKVM Cloud

> Use JetKVM from anywhere through JetKVM Cloud: connect it, sign in with Google and see how connections stay secure.

JetKVM Cloud lets you use JetKVM from anywhere with an internet connection, on a computer or phone. You sign in with your Google account and open JetKVM from there. It's off by default; on your local network, JetKVM works without it.

## What you need

* [A Google account: To sign in at app.jetkvm.com.](https://app.jetkvm.com)

## Connect to JetKVM Cloud

1. Open JetKVM's web interface: go to the IP address on JetKVM's front display.
2. Go to **Settings**, then **Access**.
3. Under **Remote**, leave **Cloud Provider** on **JetKVM Cloud** and click **Adopt KVM to Cloud**.
4. Sign in with your Google account.

You land on the cloud dashboard, with JetKVM in your list. From now on, open [app.jetkvm.com](https://app.jetkvm.com) anywhere and sign in with the same Google account.

Your JetKVM password only protects local access. In the cloud, your Google account does that job. See [Password](https://jetkvm.com/docs/using-jetkvm/password).

## Disconnect from JetKVM Cloud

Either of these removes JetKVM from your cloud account:

* In JetKVM's web interface, go to **Settings**, then **Access**, and click **De-register from Cloud**.
* In the cloud dashboard, open the menu next to JetKVM and click **Deregister from Cloud**.

Local access keeps working.

## How it stays secure

Your browser and JetKVM talk directly over **WebRTC**, for local and remote access alike. Video, keyboard, mouse and data are encrypted end to end with DTLS and SRTP. The cloud only helps the two find each other.

The JetKVM device and the web dashboard connect directly over WebRTC. Cloudflare relays the connection with STUN and TURN when needed. JetKVM Cloud only handles the handshake, over a WebSocket to the device and HTTPS to the dashboard.

JetKVM checks every remote session itself. It verifies your Google sign-in and only accepts the account that adopted it, so the cloud can't let anyone else in. This is called a zero trust model.

### When a direct connection isn't possible

Firewalls and carrier-grade NAT, common on mobile networks, can block a direct connection. JetKVM then relays the connection through Cloudflare's TURN servers. The relay passes encrypted traffic along and can't read it.

To allow JetKVM through a firewall, see [Network Requirements](https://jetkvm.com/docs/networking/network-requirements).

## Host your own cloud

The cloud components are open source. To use your own, choose **Custom** as the **Cloud Provider** before you adopt, and enter your **Cloud API URL** and **Cloud Application URL**.

* [jetkvm/cloud-api: 239 stars on GitHub](https://github.com/jetkvm/cloud-api)

## Tailscale

To reach JetKVM over your own tailnet instead of the JetKVM Cloud, install Tailscale:

* [Tailscale](https://jetkvm.com/docs/networking/tailscale)