Documentation/Connecting/Your own panel·1 / 9
Your own panel for a VPN service
A panel on a server of its own keeps your clients and gives each one link to all your nodes. One veli command sets it up; nodes and clients are run from the console, the API and MCP. Free, with no licences.
How it works
- Panel
- A server of its own: it keeps the clients, gives them links and takes the nodes' reports. No traffic goes through it.
- Nodes
- Servers with Veli and the ordinary protocols: Reality, Shadowsocks, Trojan, VMess, Hysteria2, TUIC. They take the list of clients from the panel by themselves.
- Link
- A client opens one link in Veli, Happ or another app and connects to a node directly.
- Control
- By the veli command on the panel's server, by the API with a token, and through MCP for an AI agent. There is no window in a browser.
What it takes
Two Linux servers (Ubuntu, Debian, Fedora, Arch, AlmaLinux, Rocky, CentOS Stream): one for the panel, one for a node. Each has a public IPv4 and root or sudo. A node needs TUN: nearly every VPS has it, and in OpenVZ and LXC containers it is turned on in the host's panel.
Set the panel up
Point the domain at the panel server's IP (an A record). Sign in to the server over SSH and paste the line with your domain: it fetches the veli command, checks its hash and sets the panel up. Ports 443 and 80 must be open — the certificate comes through 80.
curl -fLo veli https://velivpn.com/own-server/1.13.0-45e7dfa/veli-x86_64 &&
echo "2e39f2aa4a21b91535399f881de4cb76847c0a5195b82aab50fbd85f19e0be15 veli" | sha256sum -c &&
chmod +x veli &&
$( [ "$(id -u)" = 0 ] || echo sudo ) ./veli panel install --domain panel.example.comOn the screen: “The panel is up: https://panel.example.com” and the date of the Let's Encrypt certificate.
With no domain, write --host and the IP address instead of --domain and the name. The panel works with a certificate of its own, and only the Veli app opens the clients' links.