OK Connect Panel 1.0.0
Modified distribution prepared by OKTEAM LLC on 2026-10-16.

This is a modified version of 3x-ui v3.10.2.
Upstream: https://github.com/MHSanaei/3x-ui
Upstream revision: 608ef4e4010bf83e2e78328e08f77efc051ad4d7
Copyright and license notices belonging to the upstream authors and other
contributors are retained. The original LICENSE is preserved unchanged.
This fork is not endorsed by, or affiliated with, the upstream project.

Modifications made on 2026-10-16 include OK Connect product branding,
English self-hosted remote-access wording, an OK Connect client onboarding
flow, public legal/source links, and deployment configuration. Upstream
panel self-update is disabled so that it cannot overwrite this distribution
with a different product. Operators must install verified, reviewed OK
Connect updates manually. Xray-core remains a separately identified
component and retains its own license and notices.

This panel is licensed under the GNU General Public License, version 3,
as supplied in LICENSE. It is provided WITHOUT ANY WARRANTY, including
implied warranties of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See LICENSE for the full terms, including source-code redistribution rights.

The complete corresponding source for this deployed modified panel,
including build instructions, is available at /panel/source.tar.gz.
The company-hosted copy is also offered at:
https://okconnect.net/downloads/ok-connect-panel-source-v1.0.0.tar.gz
Self-hosting operators should make the source archive for their exact
modified version available alongside their installation and retain the
applicable legal notices. Live credentials, private keys, user databases,
and runtime logs are not part of the public source archive.

The panel manages operator-controlled endpoints and user subscriptions.
The OK Connect client imports a subscription URL or an individual supported
configuration and establishes an encrypted connection to that endpoint.
The software does not itself provide a public VPN subscription. Operators
are responsible for server security, privacy notices, access controls,
applicable law, and authorization to use their networks.

Encryption protects traffic between the client and its configured endpoint;
it does not guarantee anonymity, a trustworthy endpoint, protection after
traffic exits the endpoint, or protection against malware. Continue using
HTTPS and appropriate device security on shared and public networks.

Technical compatibility identifiers (Go module/import paths, database
filenames, service interfaces, configuration keys, and protocol strings)
may retain upstream names. Their presence is not product branding.
