v•vpnbot.dev
EN中文RU
GitHub

01 / YOUR PERSONAL VPN

Your VPN.
Your rules.

Be your own VPN provider. Install it on your server and manage users, access, statistics and protocols through Telegram.

Installation guide How it works

We provide the software. You provide the server and stay in control.

v•
Personal VPN BotInteractive preview · sample data
Your server. All under control.

Administrators: 7*******, 3********

9 users · 126.2 GB transferred

Choose a protocol or manage your server.

AmneziaWG 2.0AmneziaWG 3.1VLESSAdmin
MenuChoose a section
SCROLL TO EXPLOREAWG 2.0 / AWG 3.1 / VLESS

FROM YOUR SERVER TO YOUR PERSONAL VPN

Only you are in control.

02 / VPS

Install VPN on your server.

Get a VPS, run the installer and connect your Telegram bot. Your VPN runs on your infrastructure, not on our servers.

03 / TELEGRAM

Manage access to your VPN.

Create a separate profile for yourself, family or friends. Share a QR code or configuration. When access is no longer needed, remove the user’s profile.

04 / STATS

Monitor usage statistics.

See each user’s traffic, recent connections and server load. Know how your personal VPN is using your resources.

v•
Personal VPN BotDEMO DATA
Your server is ready.

The installer has configured VPN and connected your Telegram bot. You can now create users.

Debian 13VPN Bot
Choose a section

Preview only. No real users or VPN connections are created.

05 / RUN ONLY WHAT YOU NEED

Your protocols. Your choice.

Switch AmneziaWG 2.0, AmneziaWG 3.1 and VLESS on or off in the bot settings. Switching a protocol off stops its connections but keeps its users and configurations.

01 / AWG

AmneziaWG 2.0

AmneziaWG 2.0 with configuration files and device QR codes.

02 / AWG

AmneziaWG 3.1

A separate AmneziaWG 3.1-compatible setup running alongside AWG 2.0.

03 / XRAY

VLESS ↗

VLESS / Xray with connection links, QR codes and traffic tracking.

Try the switches. This is a preview — no real servers are affected.

READY WHEN YOU ARE

Set up your own VPN.

Follow these steps on a separate VPS. Once installed, manage your VPN through Telegram.

Debian 13+ or Ubuntu 22.04+ · root access · Telegram bot token · administrator Telegram ID

1

Prepare your server

Use a separate, clean VPS. The default VLESS setup uses TCP 443; do not run it on a web server already using that port. Back up existing data first.

2

Download and run

Run the command as root. It downloads the installer from the project repository and runs it immediately after a successful download.

3

Run the installer

Enter your bot token and administrator Telegram ID. Review the proposed changes and select the components to install.

4

Open your bot

Send /start in Telegram, select a protocol and create your first user. Import the configuration into a compatible VPN client.

root@your-vps:~
apt-get update &&
apt-get install -y ca-certificates curl &&
curl -fsSL \
  https://raw.githubusercontent.com/Telemtinstall/telemt2/main/bots/vpn-manager_awg/install_bot.sh \
  -o /root/install_bot.sh &&
bash /root/install_bot.sh
Run the command on your own server running Debian 13 or later.

Read installation documentation ↗

A few things to know.

Is this a VPN service?

No. VPN Bot is software you install on your own server. You provide the server and manage access yourself. This website does not sell VPN subscriptions.

Do users need server access?

No. An administrator manages the server. Users receive their own connection profiles; access to the bot can be granted separately.

What does “online” mean?

For AmneziaWG, the bot uses a recent handshake to estimate connection status. This is not a guarantee that a person is actively using the connection.

Will it work on every network?

No protocol can guarantee connectivity everywhere. Results depend on the network, server and client versions. Test the options on your own devices.

Website analytics

This site uses a first-party visitor cookie to recognise a returning browser, renewed for up to 400 days per visit. We record page, language, referral source, selected campaign tags, IP address and browser information in our own database. Detailed visits are retained for 180 days; a minimal visitor record and IP/geolocation history are kept longer. Clearing cookies or using a different browser creates a new visitor. If geolocation is enabled, your IP is sent to IPinfo and, when needed, ipwho.is. IP geography is approximate and may describe a VPN exit server. We respect the browser’s Global Privacy Control signal. We do not use fingerprinting to restore deleted cookies.