|
1 | 1 | # TunnlTo |
2 | | -_A powerful WireGuard client for Windows with advanced split tunneling and an intuitive, user-friendly interface._ |
3 | 2 |
|
4 | | -## Download |
5 | | -Download for Windows 10/11 on the [Releases](https://github.com/TunnlTo/desktop-app/releases) page. |
| 3 | +**Note: This open source project has been discontinued and is no longer maintained.** |
6 | 4 |
|
7 | | - |
| 5 | +We've transitioned TunnlTo into a commercial service with enhanced features and professional support. |
| 6 | + |
| 7 | +## 🔗 Official Links |
| 8 | +- [Official TunnlTo website](https://tunnl.to) |
| 9 | +- [TunnlTo on X](https://x.com/TunnlTo) |
| 10 | + |
| 11 | +## 🚀 Getting Started with TunnlTo |
| 12 | + |
| 13 | +Visit [tunnl.to](https://tunnl.to) to download the latest application. |
8 | 14 |
|
9 | | -## What does TunnlTo do? |
10 | | -TunnlTo allows you to precisely control which Windows applications, processes, and IP addresses can or cannot use a WireGuard VPN tunnel. |
| 15 | +--- |
11 | 16 |
|
12 | | -## Contact |
13 | | -Email: contact [AT] tunnl.to |
| 17 | +## FAQ |
14 | 18 |
|
15 | | -## Support |
16 | | -Email: support [AT] tunnl.to |
| 19 | +### Why a "new" version? |
| 20 | +To meet feature requests and provide better support, a new version was built with additional functionality and premium support options. |
17 | 21 |
|
18 | | -## Feedback |
19 | | -Email: feedback [AT] tunnl.to |
| 22 | +### Do I have to pay for features from the old version? |
| 23 | +No - all features from the original open-source version are still available for free in the new release, along with even more new functionality, regular updates (including security updates) and improved UI. |
20 | 24 |
|
21 | | -## Website |
22 | | -- [Visit the TunnlTo Website](https://tunnl.to) |
| 25 | +### Can I still use the old version? |
| 26 | +Yes - however, please keep in mind the old TunnlTo licensing terms: **it’s free for personal use, but not licensed for business or commercial use**. These terms have been in place since the initial release of both TunnlTo/Wiresock and continue to apply. The old version is still available [here](https://github.com/TunnlTo/desktop-app/releases/tag/1.0.7). |
23 | 27 |
|
24 | | -## Follow For Updates |
25 | | -Please follow the project on Twitter to be notified of new releases and updates. |
26 | | -- [Follow TunnlTo on X](https://x.com/TunnlTo) |
| 28 | +### Why is the new version not open source? |
| 29 | +If open-source software is a requirement for you, keep in mind that TunnlTo has always relied on Wiresock, a closed-source network driver. Using an open-source GUI for a proprietary driver offers little practical benefit in terms of transparency or security. The new version of TunnlTo is digitally signed with a Microsoft-issued code signing certificate, ensuring its integrity and authenticity. |
27 | 30 |
|
28 | | -## Example use cases |
| 31 | +### Why was the old repo removed? |
| 32 | +Keeping outdated source code for a now closed-source app would be misleading. |
29 | 33 |
|
30 | | -### Privacy |
31 | | -- Route only FireFox through a privacy VPN |
32 | | -- Route a specific IP address range through a privacy VPN |
33 | | -- Route all traffic through a privacy VPN except a local IP address range |
| 34 | +### Why is the UI different? |
| 35 | +The previous UI was designed for advanced users managing one or two tunnels, but it wasn't approachable for those unfamiliar with WireGuard. The original TunnlTo documentation even stated that users needed a "good understanding of WireGuard," yet many still wanted to use the software. As a result, the majority of support requests were about tunnel configuration, often leading beginners to misconfigure their setups. |
34 | 36 |
|
35 | | -### Work |
36 | | -- Route Slack and Microsoft Office through a work VPN |
37 | | -- Stop a browser from routing through a work VPN |
| 37 | +**Goals of the Updated UI** |
| 38 | +- Make the interface more accessible to non-technical users. |
| 39 | +- Reduce misconfigurations that could lead to unintended tunnel behavior. |
| 40 | +- Eliminate tunnel config duplication. |
| 41 | +- Allow seamless switching between VPN endpoints without reconfiguring each tunnel’s include/exclude settings. |
| 42 | +- Improve functionality for users managing tens or even hundreds of tunnels. |
| 43 | +- Remove the need for extensive documentation by integrating explanations and form validation directly into the UI. |
38 | 44 |
|
39 | | -### Gaming |
40 | | -- Route a game through a gaming VPN |
41 | | -- Stop a game from routing through a privacy VPN |
42 | | -- Route all games within the Steam folder through a VPN |
43 | | -- Route all traffic through a VPN except applications within a folder |
| 45 | +Previously, the main repository homepage was a dense wall of text explaining the required syntax for each input field. Now, the UI itself provides this guidance, eliminating the need for separate documentation. |
44 | 46 |
|
45 | | -### Screenshots |
| 47 | +For users handling large numbers of tunnels (such as those importing from privacy-focused VPN services), the searchable dropdown significantly improves usability. Instead of scrolling through an overwhelming list, they can quickly find and select the tunnel they need. Additionally, rather than duplicating entries like "chrome, firefox" in every tunnel configuration, users now define them once and switch between tunnels effortlessly. This becomes even more valuable as more applications are added. |
| 48 | + |
| 49 | +Ultimately, these updates aim to balance simplicity for beginners with the flexibility that advanced users need—while ensuring tunnel configurations remain correct to minimize security and privacy risks. |
| 50 | + |
| 51 | +### What does the new version look like? |
| 52 | + |
46 | 53 |  |
47 | 54 |  |
48 | 55 |  |
49 | 56 |  |
50 | 57 |  |
51 | | - |
| 58 | + |
0 commit comments