VPN on GitHub

By Mist Latch editorial team · Last verified September 15, 2026 · Current release, published August 21, 2026

This vpn client is open-source under GPL-3.0; desktop and mobile code lives on GitHub. Releases publish the Windows exe, macOS pkg, Linux .run, and Android APKs.

Repository: amnezia-vpn/amnezia-client. Homepage: amnezia.org. Docs: docs.amnezia.org.

Licence

Clients ship under GPL-3.0. You can read, build, and redistribute under those terms. Trademark and logos stay with upstream.

Stars and activity

As of September 15, 2026, the repo reports 15,014 stars in the live fetch used by this guide. Stars are a popularity signal, not a safety certificate. Prefer signed Releases assets and your own review.

What the repo contains

The client sources, translations, and release packaging live in the monorepo. Submodules matter when you build from source. Everyday installers still come from Releases, not from cloning for a casual vpn install.

Security reports

Security disclosures follow upstream SECURITY guidance at https://github.com/amnezia-vpn/amnezia-client/security. Ordinary bugs go to GitHub Issues. This install guide does not run a bounty.

Related doors

Releases filenames: releases. Safe download: download safe. Safety essay: is it safe.

Keep one installer door forever. Mixing Softonic wrappers with Releases and winget on the same PC creates duplicate installs and confused uninstalls. After every reimage, prove one short tunnel before you call the machine ready.

Mist Latch maps filenames and package ids for people who searched for a self-hosted client and need a local AmneziaVPN path. Upstream remains at amnezia.org and amnezia-vpn/amnezia-client under GPL-3.0. VPS billing stays your responsibility and stays separate from the program licence.

When Releases add or drop OS assets on a tag, re-check the live list before you image a classroom. Prefer Windows-bearing tags for the x64 exe. Prefer winget when that index matches machine policy. Refuse review portals that only rank with a renamed setup.

• Match AmneziaVPN_*_windows_x64.exe on Windows when Releases is the door.
• Use winget install -e --id AmneziaVPN.AmneziaVPN when winget is allowed.
• Use the macOS pkg or Linux .run from the same honest tag.
• Keep commercial apps as a brief fallback while you prove the tunnel.
• Return to the same door for updates instead of inventing a mirror.

Family PCs, student laptops, and shared desks all benefit from the same rhythm: one installer door, one server record, one documented protocol. That is how the habit stays boring in a good way.

When someone pastes a random download link into chat, ask for the GitHub Releases URL instead. The install path on this guide always returns to amnezia-vpn/amnezia-client.

Keep one installer door forever. Mixing Softonic wrappers with Releases and winget on the same PC creates duplicate installs and confused uninstalls. After every reimage, prove one short tunnel before you call the machine ready.

Mist Latch maps filenames and package ids for people who searched for a self-hosted client and need a local AmneziaVPN path. Upstream remains at amnezia.org and amnezia-vpn/amnezia-client under GPL-3.0. VPS billing stays your responsibility and stays separate from the program licence.

When Releases add or drop OS assets on a tag, re-check the live list before you image a classroom. Prefer Windows-bearing tags for the x64 exe. Prefer winget when that index matches machine policy. Refuse review portals that only rank with a renamed setup.

• Match AmneziaVPN_*_windows_x64.exe on Windows when Releases is the door.
• Use winget install -e --id AmneziaVPN.AmneziaVPN when winget is allowed.
• Use the macOS pkg or Linux .run from the same honest tag.
• Keep commercial apps as a brief fallback while you prove the tunnel.
• Return to the same door for updates instead of inventing a mirror.

Family PCs, student laptops, and shared desks all benefit from the same rhythm: one installer door, one server record, one documented protocol. That is how the habit stays boring in a good way.

When someone pastes a random download link into chat, ask for the GitHub Releases URL instead. The install path on this guide always returns to amnezia-vpn/amnezia-client.

Building from source

Casual vpn installs should use Releases. Building from source is for contributors who already pull submodules and follow upstream CONTRIBUTING notes. Do not treat a local build as a substitute for verifying the published Windows exe name on a Windows-bearing tag.

When you do build, record the commit hash on the machine ticket beside the protocol you plan to deploy. That note helps when a lab image mixes a custom build with a Releases install by mistake.