VaderVPN sells prepaid bandwidth tokens. Use the VaderVPN client, or generate a vanilla WireGuard config and QR after payment for the official WireGuard apps.
Token-authenticated WireGuard access with Pi-hole filtering.
Pi-hole is live. SOCKS relay will land after Android tunnel parity.
Paste a VaderVPN token when you want to check remaining bandwidth. The checker loads only after you activate it, keeping the landing page fast.
Bandwidth-based tokens, WireGuard transport, optional DNS filtering, and vanilla WireGuard configs for users who prefer the official apps.
Buy a token and provision a device without creating a user account. The service tracks token state, bandwidth, and device claims needed to operate the network.
The current public flow is centered on full-tunnel WireGuard with straightforward onboarding, token import, QR/config fallback, and server-side bandwidth enforcement.
Enable filtered DNS when you want tracker and junk-domain blocking. Leave it off if you want a plain tunnel.
Simple flow: buy bandwidth, redeem a token, provision a device.
Choose a prepaid bandwidth tier. Current public plans range from 50 GB to 1 TB and do not rely on a subscription clock.
Import the token in the client, or use the checkout page to generate a standard WireGuard .conf and QR code for the official WireGuard apps.
The backend provisions the peer, the VPN node tracks bandwidth server-side, and the token remains valid until its bandwidth is exhausted or 90 days pass from issuance.
If you want straightforward network access without the usual subscription-account baggage, this is the model.
Low-overhead WireGuard sessions and simple token import work well when you just need reliable access fast.
Use a device credential instead of a recoverable consumer login and keep personal profile sprawl out of the connection flow.
The purchase and redemption flow is designed to avoid account-linked identity data in normal use.
Good fit for routers, labs, vanilla WireGuard apps, and WireGuard-capable hardware where a token-based provisioning flow is easier to manage.
The main difference is the access model: prepaid bandwidth token instead of a standing user account.
| Feature | VaderVPN | Typical VPN |
|---|---|---|
| Account required for use | No | Usually yes |
| Email required | No | Usually yes |
| Billing profile tied to login | No standing login | Usually yes |
| Access model | Prepaid bandwidth token | Subscription account |
| Current public token clock | Bandwidth-based | Time-based subscription |
| Transport | WireGuard | Varies |
| Optional DNS filtering | Yes | Varies |
| Device provisioning | Token redemption, QR, or .conf | Username/password or app login |
| Personal profile required to connect | None | Often yes |
| Payment options | Card, BTC, XMR | Usually card only |
Prepaid bandwidth. No subscription clock on current public tokens. Current public tokens expire 90 days after issuance.
Light usage, testing, or a short trip.
Comfortable daily browsing and general travel use.
Default public plan and the current website baseline.
Heavier personal use across more devices.
Large transfers and high sustained usage.
Contact info@vadervpn.com if you need multiple tokens, staged rollout help, or a deployment path for WireGuard-capable devices.
Windows, Debian, Fedora/RHEL RPM, AppImage, CLI, and the current direct Android APK are mirrored now. macOS public packaging is still being refreshed before broader promotion.
Start with the public installer or package below. Token import is built into the current desktop client, and checkout can generate vanilla WireGuard configs.
Paste your token, import the token file, or generate a standard .conf and QR from the payment success page for the official WireGuard clients.
Enable DNS filtering when you want it, or leave the connection in plain tunnel mode when you do not.
No. The current public access flow is token-based and does not require a standing user account or email address.
The network keeps token state, bandwidth counters, and device claim information needed to provision peers and enforce quotas. It is not built around a personal profile or account login.
No fixed subscription clock is attached to the current public plans, but current public tokens do expire 90 days after issuance. Within that window, they are bandwidth-based rather than month-metered.
Yes. After payment, the token page can generate a standard WireGuard configuration file and QR code. Bandwidth remains tracked against the generated key.
Windows, Debian, Fedora/RHEL RPM, AppImage, CLI, and the current direct Android APK are mirrored here now.
Current public mirrors and checksum file. Start with the current Windows, Linux desktop, CLI, or direct Android build today.