Flirexa / Protocols / VLESS-Reality

Starter and above

Operate VLESS-Reality without separating it from the customer business

Reality is part of the Xray ecosystem and modifies TLS behavior so traffic can take on the handshake characteristics of a selected target. Flirexa manages the server lifecycle, customer access, subscriptions, URI and QR delivery, and multi-location operations.

Where it fits

A proxy option for networks where a plain VPN signature is a poor fit

Xray-based access

Flirexa uses Xray-core for the supported VLESS-Reality implementation and delivers a client access URI and QR code rather than a WireGuard configuration file.

Reality transport security

The official XTLS documentation describes Reality as a modified TLS form that uses the appearance and handshake characteristics of a target site as camouflage.

Different client contract

Customers need a compatible Xray/VLESS client and the parameters carried in the issued URI. A WireGuard or AmneziaWG application cannot consume that access format.

Managed lifecycle

Keep protocol access tied to the same subscription

  • install and verify the supported Xray/Reality server profile
  • create per-customer VLESS identity under the licensed protocol gate
  • render the access URI and QR code from authoritative server settings
  • enforce customer expiration and enabled state
  • deliver access through the admin panel, customer portal, or supported application path
  • update the endpoint record and refresh access when infrastructure changes
TierVLESS-Reality begins with Starter; multi-server orchestration begins with Business
CoreXray-core, maintained by the official XTLS project
DeliveryVLESS URI and QR code for a compatible client
ScopeFlirexa manages the supported profile; it is not intended to expose every possible Xray transport combination

Questions

VLESS-Reality in Flirexa

Does Flirexa replace a general Xray panel?

No. Flirexa supports a commercial VLESS-Reality profile as one protocol in the wider VPN operator platform. It does not aim to expose every Xray inbound, transport, and routing combination.

Can the same WireGuard app use VLESS-Reality?

No. It requires a compatible VLESS/Xray client and the issued Reality access parameters.

Does Reality guarantee that a server cannot be blocked?

No. The transport changes observable behavior, but server reputation, target choice, probing, routing, client fingerprint, and policy can still affect reachability.

Can I offer it beside WireGuard?

Yes. A plan and customer account can exist in the same commercial system while devices receive the protocol-specific access payload supported by their selected server.

Protocol statements are based on the official XTLS/Xray project and documentation. Flirexa is an independent operator platform.