Use the comparison table on /vs-commercial-vpn for a side-by-side. This guide expands the decision.
Pick AmneziaVPN when
You can SSH, patch a host, and want open-source clients with protocol choice including AmneziaWG.
Pick commercial apps when
You want managed coverage and vendor support more than you want to operate a server.
Pick DIY WireGuard when
You already script configs and do not need Amnezia’s deploy UI.
Why this path matters
A local AmneziaVPN client keeps the tunnel on a server you control. GPL-3.0 builds give you named release assets and package doors you can document on a machine ticket. That is enough for travel laptops, student machines, and desks that need a self-hosted path after install.
Keep Softonic-style mirrors out of the loop. Prefer GitHub Releases filenames or the verified winget id. After every reimage, prove one short tunnel before you call the machine ready.
Related doors
Home: /. Releases: /vpn-releases. Download safe: /vpn-download-safe. First hour: /installed. Guides hub: /guides.
Mist Latch publishes the install guide. Upstream remains at amnezia.org and amnezia-vpn/amnezia-client. When a tag drops an OS asset, re-check the live list before imaging a lab.
Family PCs and shared desks benefit from writing the update door beside the OS version. Windows exe, winget, macOS pkg, Linux .run, and Android APK are different doors. Mixing them without notes creates duplicate installs and confused uninstalls.
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.
Frequently asked questions
Which is cheaper?
AmneziaVPN the client is free; you pay for a VPS. Commercial apps charge a monthly seat that includes their fleet. Prefer GitHub Releases for amnezia-vpn/amnezia-client when you want named assets, and keep Softonic-style mirrors out of the loop. Document the update door on the machine ticket so the next bump stays honest for shared desks.
Which is more private?
Self-hosting can improve control when you harden the VPS. Commercial fleets add vendor trust. Neither is magic. Prefer GitHub Releases for amnezia-vpn/amnezia-client when you want named assets, and keep Softonic-style mirrors out of the loop. Document the update door on the machine ticket so the next bump stays honest for shared desks.
Can I use both?
Yes briefly while you prove the self-hosted path. Retire duplicates once the habit is documented. Prefer GitHub Releases for amnezia-vpn/amnezia-client when you want named assets, and keep Softonic-style mirrors out of the loop. Document the update door on the machine ticket so the next bump stays honest for shared desks.