Transport protocols
SingLink Beta · SingLink Sola · SingLink 2.0
Handle authentication, encrypted sessions, data transport and connection recovery. They prioritize speed, overall performance and stability respectively, and are available by plan.
SingLink ProtocolComparison and Selection Guide
Compare SingLinkVPN's own transport protocols, Beta, Sola and SingLink 2.0, and the Mini disguise layer: who can use each one, positioning, speed ceiling, stability and use cases. Then see a short, documentation-based comparison with VLESS, AnyTLS, Shadowsocks and WireGuard.
Separate protocols, the disguise layer and service policies
SingLinkVPN's four names do not sit on the same layer: Beta, Sola and SingLink 2.0 are transport protocols, Mini is a disguise layer on top of them, and commitments such as zero logging belong to service operations.
Disguise layer
SingLink Mini · Beta Mini · Sola Mini · 2.0 Mini
Runs on top of Beta, Sola or SingLink 2.0 and changes only how a connection looks on the network. It is not a standalone protocol and does not replace the underlying protocol's authentication or encryption.
VPN services and operating policies
Zero logs · Data retention · Server operations · Support
These depend on provider architecture and operating commitments. Zero logging is not a protocol switch.
Beta, Sola, SingLink 2.0 and Mini side by side
Beta, Sola and SingLink 2.0 are transport protocols. Mini is not a standalone protocol but a disguise layer on top of them. The table lines them up by plan, positioning, speed, stability, disguise and typical use.
| Dimension | SingLink Beta | SingLink Sola | SingLink 2.0 | SingLink Mini |
|---|---|---|---|---|
| Plans | Every plan: Free Plan, Fast, Plus, Pro, Max, Rich | Plus, Pro, Max, Rich (not the Free Plan or Fast) | Pro, Max, Rich | Plus, Pro, Max, Rich; appears only on underlying protocols the plan already unlocks |
| Positioning | Speed-first protocol for everyday connections | Next-generation high-performance transport rebuilt on the SingLink 2.0 stack | High-stability protocol for difficult networks | Disguise layer, not a standalone protocol: runs on top of Beta, Sola or SingLink 2.0 |
| Speed ceiling | Rises with plan tier, up to 1 Gbps on higher plans | Faster than Beta overall, with further gains in speed, latency, packet loss and bandwidth use | Stability first rather than a peak speed-test number | Depends on the underlying protocol |
| Stability | Free nodes are shared and fluctuate at peak times; paid plans use separately allocated resources | Less packet loss than Beta, with fewer stalls and reconnects | Connection stability of up to 99%, with fewer drops and reconnects | Keeps the underlying protocol's connection, tuned for fast start-up and connection stability |
| Disguise | Can carry the Mini disguise layer (Beta Mini) | Can carry the Mini disguise layer (Sola Mini) | Can carry the Mini disguise layer (2.0 Mini) | Is the disguise layer: changes how the connection looks on the network, not how it is encrypted |
| Typical use | Browsing, social media, HD video, light gaming | 4K streaming, video calls and remote desktop, large files and cloud sync | Long video meetings, sustained large transfers, remote work, networks that drop easily | Instant video start, high-speed streaming, voice calls and other low-latency use |
Figures come from official SingLinkVPN materials. Real-world results vary with region, carrier, device and node load, and the nodes available to you are shown live in the app.
Read the full guides to all four protocolsPublish only verifiable technical conclusions
This page gives no protocol a star rating or an absolute speed ranking. Figures for SingLinkVPN's own protocols (up to 1 Gbps, stability of up to 99%) come from official SingLinkVPN materials; third-party protocols are described only from their official documentation, each with its limits stated.
Official specification
Specifications published by protocol authors, standards bodies or official maintainers.
Public project documentation
Official documentation, public source code and maintainer statements.
Public SingLink design
Design boundaries disclosed by the SingLink whitepaper and technical report.
Environment-dependent validation
Performance and availability vary with device, server and network conditions.
“Not publicly documented” does not mean insecure. It means the public evidence is insufficient for a more specific conclusion.
How the design differs from VLESS, AnyTLS, Shadowsocks and WireGuard
The table compares only design features published in each project's official documentation. It is not an absolute performance ranking and does not imply code compatibility or a security audit result. Real-world results also depend on implementation, servers, distance, network quality and configuration.
| Dimension | SingLink | VLESS | AnyTLS | Shadowsocks | WireGuard |
|---|---|---|---|---|---|
| Published role | SingLinkVPN's own protocol family, covering both the control plane and the data plane | Stateless, lightweight client-server transport protocol | TLS-based proxy protocol that aims to reduce the TLS-in-TLS handshake fingerprint | Encrypted proxy protocol built on a pre-shared key | Compact VPN tunnel protocol that carries IP packets |
| Authentication and encryption | Nodes verify the account and session with replay protection, and each connection gets its own encryption context | Authenticates with a UUID; must run inside outer transport security such as TLS or REALITY, or use the optional VLESS Encryption | Authenticates with a SHA-256 hash of the password after the TLS handshake; encryption comes from the outer TLS | AEAD encryption; the 2022 edition derives session subkeys with BLAKE3 and has built-in replay protection, but no forward secrecy | Noise protocol framework with Curve25519, ChaCha20-Poly1305 and BLAKE2s |
| Traffic appearance | Beta, Sola and SingLink 2.0 can carry the Mini disguise layer; no claim of absolute invisibility | Depends on the chosen transport and flow, often combined with TLS or REALITY | Looks like TLS traffic, with configurable packet splitting and padding that the server can update | No plaintext header; the specification says the traffic is indistinguishable from a random byte stream | Officially not focused on obfuscation, which should happen at a layer above it |
| TCP and UDP | Published design covers TCP, UDP and QUIC-style traffic | Proxies TCP and UDP, with UDP carried inside the proxy connection | TCP; UDP is carried as UDP over TCP | The specification defines both TCP and UDP | UDP only; TCP mode is officially not supported |
| Deployment and upkeep | Managed end to end by the SingLinkVPN apps and nodes, available by plan | Open protocol; you deploy a server (such as Xray-core) and maintain the configuration | Open protocol with the anytls-go reference implementation; you deploy and maintain it | Open protocol with several open-source implementations; you deploy and maintain it | Open source and built into the Linux kernel; suited to self-hosting and system integration |
The complete connection lifecycle
SingLink 2.0 materials divide a connection into control-plane work, DNS and routing, authentication, transport, recovery and state cleanup. This is a summary of the published flow.
01
Configuration retrieval
The client obtains the account, server and protocol settings needed for the current connection.
02
DNS and routing decision
Resolution and traffic paths are selected from the domain, destination, rules and network state.
03
Authentication and session setup
The client validates the server, negotiates keys and creates session state.
04
TCP and UDP transport
Reliable streams, datagrams, flow control and MTU are handled according to connection type.
05
Network roaming and recovery
Network changes, failures, reconnection and server reselection are handled.
06
Session close and state cleanup
The connection is closed and temporary state that is no longer needed is cleared.
Design explanation, whitepaper and security verification
The three resources have different jobs: the technical report explains operation, the whitepaper defines the public design and the independent audit verifies the versions and scope listed in its report.
Technical analysis
SingLink 2.0 technical report
Explains configuration, DNS, routing, authentication, sessions, TCP, UDP, recovery and cleanup.
Read the technical reportOfficial technical document
SingLink protocol whitepaper
Documents protocol and app versions, control and data planes, reference models, test boundaries and public evidence status.
Read the official whitepaperIndependent verification
2026 cross-platform security audit
Review tested versions, platform scope, findings, limitations, report files and SHA-256 verification material.
View the security auditThe SingLink 2.0 technical report is an official technical analysis, not an independent security audit. The two are labeled separately.
Choose by use case, not by name alone
No protocol fits every network. Consider app support, server implementation, local network conditions, operating cost and available evidence.
Free or light everyday use
SingLink Beta
The only protocol on every plan, including the Free Plan, suited to browsing, social media and HD video.
More speed, lower latency
SingLink Sola
Plus and above. Better than Beta on speed, latency, packet loss and bandwidth use, suited to 4K streaming and real-time collaboration.
Connections that must not drop
SingLink 2.0
Pro, Max and Rich. Built for difficult networks, with connection stability of up to 99%.
Instant video and low-latency streaming
Mini nodes (such as Sola Mini)
Adds the disguise layer on an unlocked underlying protocol, suited to video, music streaming and voice calls. Plus and above.
Running your own server
VLESS, AnyTLS, Shadowsocks or WireGuard
For users who can deploy a server, manage keys and configuration, and understand each protocol's security limits.
Restricted or complex networks
Validate in the current network
The app switches protocols in one tap. Availability changes by region, carrier and time, so test the current nodes directly.
About SingLink protocols
Which protocols does SingLinkVPN offer?
Three transport protocols, Beta, Sola and SingLink 2.0, plus the Mini disguise layer that runs on top of them. Beta is on every plan; Sola and Mini start at Plus; SingLink 2.0 is available on Pro, Max and Rich.
Is Mini a standalone protocol?
No. Mini is a disguise layer. A node name ending in Mini (such as Sola Mini or 2.0 Mini) means the disguise layer runs on that protocol; authentication, encryption and data transport are still handled by the underlying Beta, Sola or SingLink 2.0.
Which protocol can the Free Plan use?
The Free Plan can use Beta protocol nodes only. Fast also has Beta only; Plus adds Sola and Mini, and Pro, Max and Rich add SingLink 2.0.
How do I choose between Beta, Sola and SingLink 2.0?
Beta is usually enough for everyday browsing; choose Sola if speed, latency and packet loss matter most; choose SingLink 2.0 when a connection has to stay up for a long time. The app switches protocols in one tap, so you can compare them directly.
How does SingLink differ from VLESS and AnyTLS?
VLESS is a stateless, lightweight transport protocol that must run inside outer transport security such as TLS or REALITY, or use the optional VLESS Encryption. AnyTLS is a TLS-based proxy protocol focused on reducing the TLS-in-TLS handshake fingerprint. SingLink also covers the app's traffic entry, DNS, smart routing, plan permissions and node scheduling, so the comparison is about system scope, not a claim that one is faster.
How does SingLink differ from Shadowsocks and WireGuard?
Shadowsocks encrypts with a pre-shared key, and its 2022 specification says the traffic is indistinguishable from a random byte stream, but it provides no forward secrecy. WireGuard is a compact UDP-only tunnel that is officially not focused on obfuscation. Both need a server you deploy and maintain yourself, while SingLinkVPN's protocols are managed end to end by its apps and nodes.
How does SingLink 2.0 differ from app version 2.0?
SingLink 2.0 identifies protocol architecture and server capability. App version numbers identify software releases. The two version systems are managed independently.
Which VPN protocol is fastest?
There is no permanent answer without test conditions. Protocol overhead is only one factor; device performance, server load, distance, MTU, carrier and congestion can all change results.
Start with evidence you can verify
Read primary specifications, check implementation boundaries and test on your own device and network. This guide, the whitepaper, security audit and feed use real revision dates.