Overview
A tunnel client does one job: it wraps the machine's traffic in an encrypted connection to a server somewhere else, so the local network sees an encrypted stream rather than a list of destinations, and the destinations see the server rather than the machine. On a hotel network, a conference connection or any shared link, that is the difference between browsing privately and browsing in public.
This client covers the practical set. A server list spanning a good number of regions with latency shown per location, a choice of tunnel protocol so a restrictive network can be worked around when the default is blocked, split tunnelling to decide which applications go through the tunnel and which do not, and a kill switch that cuts traffic entirely if the tunnel drops rather than quietly letting it out unencrypted.
The configuration here removes the limits the free tier applies: the bandwidth cap, the restricted server list, the single device restriction and the session time limit. Auto connect rules can start the tunnel on an untrusted network and leave it off at home, and connection profiles keep separate settings for different situations rather than reconfiguring by hand each time.
What it does well
No bandwidth cap
The transfer limit and the session timer that the free tier applies are both removed in this configuration.
Full server list
Access to every region rather than the handful the restricted tier offers, with latency shown per location.
Split tunnelling
Choose per application which traffic goes through the tunnel, so a local device or a fast download can bypass it.
Kill switch
If the tunnel drops, traffic is blocked rather than falling back to the open connection.
Auto connect rules
Connect automatically on untrusted networks and stay off on the ones you trust, with per-profile settings.
Changes in this build
- Additional tunnel protocol added for networks that block the default.
- Reconnection handling improved so a brief drop no longer requires a manual reconnect.
- Server list refreshed with more regions and better latency measurement.
- Split tunnelling rules now survive an application update rather than resetting.
- Lower idle resource use in the background service.
What is in the package
- AMAN VPN client installer, 64-bit
- Full server list across all regions
- Multiple tunnel protocol support
- Split tunnelling and kill switch configuration
- Multilingual interface files, 15 languages
System requirements
| Processor | Any x64 processor |
| Memory | 2 GB minimum |
| Graphics | Any adapter |
| Storage | 200 MB free |
| Display | 1024 x 768 minimum |
| System | Windows 10 or Windows 11, 64-bit |
Installation
- Extract the archive and close any running instance from the tray.
- Run the installer and allow the network adapter driver to register.
- Apply the included configuration step before the first connection.
- Turn the kill switch on before connecting for the first time.
- Disable the updater so the configuration is not replaced.
Before you start
The virtual adapter has to install for the client to work, allow the driver prompt during setup.
Split tunnelling rules are per application, a browser routed outside the tunnel stays outside it.
An update will restore the standard limits, keep the updater off.
Questions about this title
Is there a data limit?
No, the transfer cap and session timer are removed in this configuration.
Can I choose which applications use it?
Yes, split tunnelling sets that per application.
What happens if the connection drops?
The kill switch blocks traffic rather than letting it out unencrypted, when it is enabled.
Does it support more than one protocol?
Yes, an alternative protocol is available for networks that block the default.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.