Install AmneziaVPN first. Prepare SSH access to a VPS. Deploy containers or import a supported config. Prove one site through the tunnel. Only then retire the commercial app.
What does not transfer
Paid fleets, vendor support seats, and proprietary account history stay with the commercial product. Your “connect” habit transfers; the servers do not.
Cluster page: /switch-from-commercial-vpn. Comparison: /vs-commercial-vpn.
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
Do commercial configs import automatically?
Not as a universal promise. AmneziaVPN supports deploy and import flows documented upstream; proprietary vendor profiles may not transfer one-to-one. 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.
Should I cancel the commercial seat immediately?
No. Keep it briefly until the self-hosted vpn tunnel is boring and 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.
What do I need before switching?
A VPS or server with SSH access, plus the AmneziaVPN client from Releases or winget. 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.