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.
Starter and above
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
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.
The official XTLS documentation describes Reality as a modified TLS form that uses the appearance and handshake characteristics of a target site as camouflage.
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
Questions
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.
No. It requires a compatible VLESS/Xray client and the issued Reality access parameters.
No. The transport changes observable behavior, but server reputation, target choice, probing, routing, client fingerprint, and policy can still affect reachability.
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.