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. You own the servers, and user traffic does not pass through PeerBlade infrastructure.
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 and AmneziaWG keep running on your servers with their current configurations. The panel manages configuration and state; it does not carry user traffic. You can still manage those interfaces directly with their native tools.
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.
It reads supported interfaces and shows them in the panel, and nothing more. The interface PeerBlade manages is a separate one the installer creates itself — existing WireGuard and AmneziaWG interfaces are never modified or removed, and handing one over to PeerBlade is a deliberate, manual step.
Ubuntu or Debian with systemd, on x86_64 or arm64, outbound HTTPS access to the control plane and an open UDP port for the selected transport. The install command sets up WireGuard, AmneziaWG 1.x or AmneziaWG 3.x when required. 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.
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 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.
PeerBlade does not send personal data or information about your infrastructure. The control panel does not collect usage analytics. The public website uses Google Analytics only after you consent in the cookie banner; advertising, remarketing and Google Signals are not used.