Every server at hand
A single registry of VPS instances with agent status, interfaces, selected transport and current state.
Manage nodes, peers and configurations from a single panel — without editing files by hand or doing routine work over SSH.
Keys are generated by the agent on the server. The private key is never stored in the control plane and is only available when the configuration is issued.
The snapshot stays safe: private keys and preshared keys are never transferred. A green dot means a handshake in the last 5 minutes, and the toggle enables or blocks the peer's access.
Everything you need for day-to-day node and peer operations — without bloated interfaces or hidden magic.
A single registry of VPS instances with agent status, interfaces, selected transport and current state.
Create, disable and delete access without editing configuration files by hand.
Recent handshakes, RX/TX, snapshot freshness and traffic charts show what is happening across your nodes.
Download a ready-made .conf or connect a device by QR code straight from the panel.
The native agent connects over outbound HTTPS — PeerBlade needs no SSH access to your servers.
A history of sign-ins and administrative operations that never records passwords, tokens or private keys.
On a clean Debian or Ubuntu server the installer sets up Docker, brings the panel up behind TLS and, with --with-node, turns the same host into your first node: WireGuard interface, firewall rules and agent included.
curl -fsSL https://peerblade.com/install.sh | sudo bash -s -- panel.example.com --with-nodeA clean Debian or Ubuntu server with root access, x86_64 or arm64, 2 GB RAM, ports 80 and 443 free, a UDP port for the tunnel, and a DNS name pointing at it.
How PeerBlade relates to your infrastructure, your keys and your traffic.
The Linux node agent is open source under GPL-3.0-or-later, including its tests, installer scripts, protocol description and public release workflow. The web panel and control-plane API remain proprietary and are distributed as container images. This split lets you inspect and build the privileged component that runs with CAP_NET_ADMIN on your WireGuard nodes without presenting the entire product as open source.
No. PeerBlade is a control panel for your own WireGuard infrastructure. You own the servers, and user traffic does not pass through PeerBlade infrastructure.
No. PeerBlade is deployed as a self-hosted panel: the first launch creates a local administrator, and further accounts are added inside your own installation. Account data is stored in your own database.
The agent generates and stores private and preshared keys on your node in a separate state file with 0600 permissions. They never enter snapshots or PostgreSQL. When an authenticated administrator requests a .conf file or QR code, the node sends the configuration through the protected API; the control plane does not persist it.
All your WireGuard servers, peers and configurations — in one place.