Frequently asked questions
How PeerBlade relates to your infrastructure, your keys and your traffic.
No. PeerBlade is a control panel for your own WireGuard infrastructure. User traffic does not pass through PeerBlade infrastructure, and the private keys of WireGuard peers never leave your servers.
No. The agent opens an outbound HTTPS connection to the control plane itself. PeerBlade never opens inbound SSH sessions to your VPS and never asks for SSH access.
WireGuard keeps running on your servers with its current configuration. The panel manages configurations, it does not carry the traffic. You can manage those servers directly with wg and wg-quick whenever you need to.
The agent generates private keys on your server and keeps them there, in a separate state file with 0600 permissions. Only public keys reach the control plane; the private key is available once, when a configuration or QR code is issued.
By default it only reads them and shows them in the panel. The installer does not create, modify or remove existing interfaces. Handing a particular interface over to PeerBlade is an explicit opt-in.
Ubuntu or Debian x86_64 with systemd, WireGuard installed, outbound HTTPS access to the control plane and an open UDP port for WireGuard. The agent runs under its own system user and uses the minimum capability it needs — CAP_NET_ADMIN.
Yes. Each server has its own agent, interface and endpoint, and the panel collects them into a single registry with handshake status, RX/TX and snapshot freshness. Peer addressing is per node, so the subnets must not overlap.
Not at this stage. PeerBlade is a self-hosted product, but its source code is proprietary and is not distributed under an open-source license. Container images are published so that you can deploy the panel yourself — that is not an open-source license and grants no rights to the code. Self-hosted does not mean open source: you run the service in your own infrastructure, while the rights to the code stay with the rights holder.
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 control panel sends no analytics. The public website uses Google Analytics — only after you consent in the cookie banner. Before consent the analytics script is not loaded. Advertising, remarketing and Google Signals are not used.