VLESS and Reality: what a VPN business owner should know

What these terms mean for your business, and which decisions follow from them.

Updated: · Markdown version

In short

VLESS is the protocol a client and an Xray node use to exchange traffic. Reality is a connection security layer that replaces regular TLS: the node needs no domain or certificate, recognizes its own clients by key, and hands every other connection to a third-party site from its configuration. VLESS + Reality is the most common setup on nodes of Remnawave-based services.

Xray, VLESS, Reality: what's what

LayerWhat it isExamples
ServerThe program on the node that accepts connectionsXray-core
ProtocolHow the client identifies itself and what to carryVLESS, VMess, Trojan
Connection securityHow the channel is encrypted and authenticatedTLS, Reality
TransportHow the bytes travelTCP, gRPC, XHTTP

By default VLESS doesn't encrypt anything; that's by design, to keep the protocol light. Since 2025 Xray has offered optional built-in VLESS encryption, but in practice services still rely on TLS or Reality for protection.

How Reality differs from regular TLS

With regular TLS, each node has its own domain and certificate. You buy domains, renew certificates, and a shared domain ties your nodes together.

With Reality, the node has no certificate of its own. It recognizes your clients by key and completes the handshake with them itself; anything it doesn't recognize, it passes through to the real third-party site. For a business owner that means:

  • Nodes don't need domains or certificates. You still need them for the panel and the subscription page.
  • A Reality connection has a key pair. It belongs to the inbound; in Remnawave it's stored in the panel's settings and gets backed up with the database.
  • The configuration names a third-party site. It's part of your config, so know where it's recorded and keep it with the rest.

What about VMess?

VMess is an older protocol with built-in encryption that you'll still find in services launched a few years ago. Remnawave's official migration tool doesn't carry VMess connections over, so in a Marzban migration those users are a separate group. See the migration checklist.

Decisions that follow

  1. Keys are data. If a Reality key is lost, it gets reissued, and users only receive the new one through their subscription link. Without subscriptions, that's a message to everyone. So your panel settings need to be in your backups.
  2. The subscription link matters more than the protocol. As long as users pull settings from a subscription link, you can change nodes and parameters without involving them. A service that hands out configs manually turns every change into a mass message.
  3. A node can be up and still unreachable. The server is alive and Xray is running, yet users on some networks can't connect. "Server responds" monitoring won't catch that; you need a view from the networks your users are on. See reachability probes.
  4. Client compatibility. Client apps support Reality differently and update at different speeds. Before changing anything network-wide, check which apps your users run.

Short definitions are in the glossary.

Let us look at your network

The audit is free: we review nodes, panel and bot and show the weak spots. We reply on Telegram.

Free audit →