A small setup.
A new connection.

Sharp VPN for Windows · TCP tunnel · Version 0.3.1

1. Create your account

Register on the home page, then download the Windows app. Sign in with the same email and password. The app assigns a random device ID and keeps you signed in with a Windows-encrypted token until you sign out or revoke the device.

2. Choose a route

Dedicated node: uses a managed Sharp VPN exit. The server assigns the healthy node with the least reported transfer that day and keeps the VPN session on it. Each account can use 1 GiB per UTC day across dedicated nodes.

Community peer: uses another online member who has enabled sharing. Traffic passes through the PHP relay and exits from that member’s internet connection. Both members can be behind NAT.

3. Connect your Windows device

Click Connect VPN. On first use, Sharp downloads its verified tunnel engine from the publisher. Approve the Windows administrator prompt to create the VPN adapter. Sharp tests the outward IP and destination TLS before showing Connected.

Browse normally: no browser proxy setting is needed. TCP internet traffic and DNS use the selected exit. Unsupported UDP and IPv6 are blocked while the tunnel runs, so some games and calls will not work. Click Disconnect to restore normal routing.

If no dedicated node works, the operator can test it in the node panel. Community mode needs a peer on another internet connection; using a peer on your own public connection cannot change your outward IP.

4. Share on your terms

Check the sharing consent box, then click Enable sharing. Other members’ traffic will exit through your public IP. The app must remain open. Your dashboard can set a daily sharing cap from 0.1–100 GiB or pause sharing remotely. The default is 1 GiB per UTC day.

Use only internet connections you have permission to share. Private-network destinations are blocked by the sharing client. Closing the app stops sharing; an unexpected disconnect expires after 20 seconds.

Limits of this release

Sharp supports TCP, with DNS-over-HTTPS through the exit. It does not provide general UDP forwarding, IPv6 exits, a persistent kill switch after an engine crash, guaranteed anonymity, or guaranteed uptime. The managed exit uses authenticated HTTP CONNECT, while application HTTPS continues to protect content end to end. Exit operators can see destination metadata.