PROJECT V ECOSYSTEM
Project V, V2Fly, and Xray Explained
Keep ecosystem names, proxy cores, and GUI clients distinct to understand which parts of a guide apply to your setup. Similar names don't mean configurations are interchangeable. Check feature support against your selected core and client interface.
Project V: Background to the Configuration Model
Project V is the open-source ecosystem behind V2Ray-related tools and technical documentation. A common way to understand the configuration is through inbound, routing, and outbound: inbound receives application requests, routing checks conditions, and outbound makes the connection. This model is more reliable than memorizing a particular setting's location and remains useful as interfaces change.
When reading older guides, distinguish protocols, transports, and security layers. VMess, VLESS, and Trojan are different protocols; WebSocket and similar options are transport settings; TLS covers connection security. Treating these as a single “mode” can make it easy to miss required server settings.
V2Fly and Xray: Separate Core Development Branches
The V2Fly community continues V2Ray development and maintenance, while Xray-core has developed its own implementation and features from related code. The two share some configuration concepts, but protocol extensions, supported fields, and defaults can change independently. A configuration accepted by one core may not work with the other.
When choosing a core, check the complete server settings and core requirements first. Don't judge compatibility by the server name alone or treat switching cores as a speed boost. If you see unknown fields or an unsupported transport, confirm which core the configuration is for before deciding whether to update or switch cores.
Three Clients: Open-Source GUIs and Their Cores
v2rayN, v2rayNG, and v2flyNG are open-source GUI clients. v2rayN is for desktop systems and manages subscriptions, settings, and core execution. v2rayNG is for Android and uses the Xray core; v2flyNG offers a mobile option based on the V2Fly core. Check the client name and the core that handles connections separately.
Open-source licenses set the terms for using, modifying, and distributing code. Xray-core and the V2Fly core are licensed under MPL 2.0, while each GUI client has its own licensing requirements. A core's license does not replace the license for the entire client. For redistribution or modifications, review the notices for each project separately.
Update in Order: Back Up, Then Retest
The GUI client and core may update separately, as can their settings interfaces, configuration generation, and protocol support. Before upgrading, back up subscription groups, routing rules, and custom settings, and note the current proxy mode. After upgrading, test a known working connection first, then restore extra rules one at a time to identify any behavior changes.
The download center provides platform-specific options; the homepage does not pin a specific version. Subscription updates and program updates are also different: the former refreshes server entries, while the latter updates the client or core. If an entry stops working, check the subscription update results and connection logs before reinstalling the entire client.