VPN

Switch from commercial VPN apps

By Mist Latch editorial team Current release, published August 21, 2026

Abstract tunnel panel with umber arc and sand accent on fog paper.
Tunnel panel diagram: concentric rings interrupted by a single encrypted hop arc. Mist Latch original hop-pipe geometry for factory-vpn (not an Amnezia logo).

Moving from a commercial vpn seat into AmneziaVPN means installing the GPL-3.0 client, deploying a server you control, and proving a tunnel before you cancel anything.

What transfers

Your mental model of “connect” transfers. Your paid commercial server fleet does not. Account history, vendor apps, and proprietary configs stay with the commercial product.

Steps

  1. Install AmneziaVPN. Prefer the Windows x64 exe, winget, macOS pkg, or Linux .run from Releases.
  2. Prepare a VPS. Keep SSH access ready with a key or password you control.
  3. Deploy or import. Let Amnezia install containers, or import a supported config if you already have one.
  4. Prove one tunnel. Load a site through the new path before you change DNS habits.
  5. Keep the commercial app briefly. Retire it only after the self-hosted path is boring.

What not to expect

Do not expect commercial anycast coverage on a single VPS. Do not expect one-click import of every proprietary vendor profile. Comparison context: vs commercial vpn apps.

Related

Self-host: self-host server. First hour: installed. Safety: 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.

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.