SingLinkVPNOpen Source Projects

SingLinkVPN open source projects are SingLink Beta, the first-generation SingLinkVPN client, SingChat and the SingLinkVPN open-source hub, all maintained by SingLinkLabs on GitHub. After a security audit, SingLinkLabs released the first-generation protocol and client under Apache-2.0; the latest versions are not yet fully public for security reasons, and the open-source plan continues. Each project lists its maintainer, repository, license and public scope.

4 official projectsOwnership and public scope are verifiable

Visit SingLinkLabs on GitHub Explore protocol research

Establish ownership before describing technology

Every project on this page is maintained by SingLinkLabs, which also defines its public scope. Each card states the repository, the license and exactly what has been released.

Key facts

The SingLink protocol has evolved from SingLinkVPN's early versions to today's SingLink 2.0. The open-source SingLink Beta (first generation) and the SingLinkVPN first-generation client carry forward SingLinkVPN's long-standing design principles: account-based permissions, device binding and security by design. Both were released after a security audit. The official apps and protocol have since moved to a new-generation architecture that is not yet fully public for security reasons; we release only code that poses no security risk, and the open-source plan will continue.

Released on 2026-11-12: SingLink Beta (1.0.0-draft) and the SingLinkVPN first-generation client for Windows, macOS, Android and iOS.
License: Apache-2.0 for both repositories. The SingLink and SingLinkVPN names and logos remain trademarks.
Source code: github.com/SingLinkLabs/singlink-protocol and github.com/SingLinkLabs/singlink-vpn-app.
Security: an internal audit with 31 findings, all High and Medium fixed; a third-party audit is planned.
Closed for security reasons: the SingLink 2.0 core and the current official apps, servers, payment and nodes.

Official open-source projects

Code, technical materials and research projects maintained directly by SingLinkLabs, with a clear public scope and repository boundary for each project.

Maintained by SingLinkLabs · 01

SingLink Beta

SingLink Beta (1.0.0-draft) is the first-generation version of the SingLink protocol, an open VPN protocol that SingLinkLabs designed from scratch. From the outside it looks like ordinary HTTPS. Access passes signed by the account backend carry plan, expiry, speed and device limits and are bound to a device key, so a stolen pass is useless. Key exchange is hybrid X25519 + ML-KEM-768 post-quantum, with replay protection and probe resistance.

Maintainer: SingLinkLabs
Public scope: Open protocol specification and Go source
License / Status: Apache-2.0 · 1.0.0-draft

Technical areas

Protocol specification (SingLink Beta)

Signed, device-bound access passes

Hybrid post-quantum key exchange

Probe and replay resistance

Internal security review and fuzz tests

Node, CLI and C library for apps

An official SingLinkLabs project under Apache-2.0, written in Go using only the standard library. SingLinkLabs released this first-generation protocol after a security audit (an internal review with 31 findings, all High and Medium fixed), and a third-party audit is planned. The latest version is not yet fully public for security reasons, so only code with no security risk was released; the open-source plan continues.

View repository

Maintained by SingLinkLabs · 02

SingLinkVPN App

The first-generation SingLinkVPN client: one Flutter codebase for Windows, macOS, Android and iOS, with a Go core built on the open SingLink Beta protocol. On Android and iOS it runs as a device-wide VPN with DNS inside the tunnel; on desktop it sets the system proxy on connect and restores it on disconnect, quit or crash.

Maintainer: SingLinkLabs
Public scope: First-generation client source
License / Status: Apache-2.0

Technical areas

Windows, macOS, Android and iOS

Device-wide VPN on mobile

System proxy mode on desktop

Go core on SingLink Beta

GitHub Actions builds

Apache-2.0 with trademark notice

An official SingLinkLabs project under Apache-2.0. SingLinkLabs released this first-generation client after a security audit; the latest app versions are not yet fully public for security reasons, and the open-source plan continues. Android and macOS have been tested end to end, iOS builds and runs in the simulator, and the Windows app is built by the included GitHub Actions workflow. The names and logos remain SingLinkLabs trademarks, so forks must use their own name and icon.

View repository

Maintained by SingLinkLabs · 03

SingChat

SingChat is a live chat and AI support service. Its public SingChat MCP project provides the manifest, examples and technical documentation needed to connect compatible AI clients to workspace setup, website widgets, conversation management, knowledge workflows and support analytics.

Maintainer: SingLinkLabs
Public scope: Public source repository
License / Status: MIT

Technical areas

Live chat widget

AI support agent

MCP integration

Knowledge base and RAG

Conversation management

Support analytics

An official SingLinkLabs project. The public singchat-mcp repository contains the MIT-licensed manifest, examples and documentation for the hosted SingChat MCP service.

View repository Visit project website

Maintained by SingLinkLabs · 04

SingLinkVPN

The SingLinkVPN open-source hub is now in phase 2. It brings together the first-generation SingLink protocol and SingLinkVPN client, both released under Apache-2.0 in their own repositories after a security audit, and publishes documentation, research data, security and transparency reports and research tools.

Maintainer: SingLinkLabs
Public scope: Open-source hub, phase 2
License / Status: Phase 2 · Apache-2.0 code

Technical areas

SingLink Beta (Apache-2.0)

First-generation client (Apache-2.0)

Technical documentation

Research data and benchmarks

Security and transparency reports

Research tools

An official SingLinkLabs project. The hub holds the documentation, datasets, reports and research tools; the protocol and client code live in the singlink-protocol and singlink-vpn-app repositories. The latest versions, including the SingLink 2.0 core and the current official apps, remain closed for security reasons; more will be released in later phases after security review.

View repository Visit project website

Frequently asked questions

Is the SingLink protocol open source?

Yes, its first generation. On 2026-11-12 SingLinkLabs released SingLink Beta (1.0.0-draft) and the SingLinkVPN first-generation client under Apache-2.0, after a security audit. The latest version, SingLink 2.0, is not yet fully public.

How does SingLink 2.0 relate to the first generation?

The SingLink protocol has evolved from SingLinkVPN's early versions to today's SingLink 2.0. The released first generation carries forward the same principles: account-based permissions, device binding and security by design. The official apps and protocol have since moved to a new-generation architecture.

Which parts stay closed, and why?

The SingLink 2.0 core and the current official apps, servers, payment and nodes stay closed for security reasons. SingLinkLabs releases only code that poses no security risk, and more will follow in later phases after security review.

Which license applies, and can I fork the code?

Both repositories use the Apache-2.0 license, so you can use, modify and redistribute the code under its terms. The SingLink and SingLinkVPN names and logos are trademarks, so forks must use their own name and icon.

Is the SingLinkVPN app on the Snap Store open source?

No. Snap is only the package and installation method for the SingLinkVPN Linux app; it is not an open-source release. SingLinkVPN's open-source projects are the ones listed on this page.

Open source needs verifiable boundaries

A professional open-source page explains code, documentation, licensing, contribution paths and security boundaries. SingLinkVPN publishes traceable records instead of vague labels.

Project ownership

State the maintainer, repository and license of every project, without brand ambiguity.

Public scope

Separate released code, technical documents and research data from product components that remain closed.

Reproducible research

Publish versioned documentation, machine-readable data and test methods for independent review.

Security and contribution

Use repository guidance, licensing and disclosure channels to create a clear participation path.

Explore code, documentation and research records

Start with the official repositories to review the public scope, version history and technical direction of SingLinkVPN open source.

Visit SingLinkLabs on GitHub Download SingLinkVPN