What Security and Encryption Features Does Remotly Provide?

Updated

Remotly encrypts all transmitted data with AES-256, generates a unique AES key for each session, hides your connection code from unauthorized viewers, and lets businesses run their own relay server so sensitive traffic never passes through shared infrastructure. These protections apply to both remote work sessions and remote gaming, so the same security model covers every connection you make.

The four security mechanisms

1. AES-256 encryption on all transmitted data

Every piece of data sent between the two connected devices is encrypted using the AES-256 standard. This is the same cipher class used in many enterprise and government security contexts, and it applies to the full data stream rather than only the initial handshake.

2. A unique key per session

Connections are made using AES encryption with a unique key generated for each session. This matters because a reused key across sessions means one compromised key could expose multiple past or future connections. Per-session keys limit the blast radius to a single session.

3. Invisible User ID

The remote assistance application blocks access to the connection code from unauthorized persons. In practice, this means someone who does not already have your connection ID cannot discover it through the app itself — they need you to share it deliberately.

4. Self-hosted relay server for businesses

Companies can run their own relay server. With this setup, data and communications with clients do not pass through Remotly's shared infrastructure, which is the option to choose if your organization handles sensitive client data and needs to keep traffic inside its own perimeter.

How the pieces fit together

Feature What it protects against Who it matters most for
AES-256 on all data Interception of the data stream in transit Everyone
Unique key per session Key reuse exposing multiple sessions Everyone
Invisible User ID Unauthorized parties obtaining your connection code Anyone sharing access to their PC
Own relay server Traffic passing through third-party infrastructure Businesses with sensitive data

What this means in practice

For a typical remote gaming or remote work session, the practical effect is: you share a connection ID with the person or device you want to connect to, the session negotiates its own AES key, and the stream is encrypted end to end at AES-256. If you are an individual user, the first three mechanisms are what you rely on. If you are evaluating Remotly for a company, the self-hosted relay option is the differentiator worth checking against your internal data-handling requirements.

One caveat to keep in mind: encryption protects data in transit, but the security of a session still depends on you not sharing your connection ID with people you do not trust. The Invisible User ID feature prevents unauthorized discovery — it does not prevent you from handing the code to the wrong person.

For current plan details and whether the self-hosted relay option is available on your tier, check the pricing page at remotly.com/plans, since availability of business features can vary by plan.