Flamingo Raises $4.5M to Get MSPs Out of the Ticket Queue

Skip to content
WireGuard logo

WireGuard

Zero Trust Network Access (ZTNA)

Open Source
Free Tier
OpenMSP Score
53
40
Reddit Impact Score
Github Score
664K
744Stars
334Forks
496Commits
GNU General Public License v2.0License
Nov 10, 2026Last commit
WireGuard is a free, open-source VPN created by Jason A. Donenfeld: a protocol plus the tools and apps that run it. It carries IP packets inside UDP through an ordinary network interface such as wg0, and each peer is identified by a public key, much like an SSH key. The handshake is built on the Noise protocol framework with one fixed set of modern primitives (Curve25519, ChaCha20, Poly1305, BLAKE2s, SipHash24 and HKDF), so there are no cipher suites to negotiate or get wrong. The protocol has symbolic proofs in Tamarin and a verified Curve25519 implementation, and the project designed the codebase to be small enough for one person to review in full. WireGuard was merged into the Linux kernel in version 5.6, released on 29 March 2020. The project publishes official apps for Windows 10 and 11 and Windows Server 2016, 2019, 2022 and 2025, for macOS and iOS through the App Store, and for Android through Google Play or a direct APK, plus packages for Debian, Ubuntu, Fedora, RHEL, Arch, FreeBSD, OpenBSD, OpenWrt and other systems. Because a peer is identified by its key, a laptop or phone keeps its tunnel when its address changes between Wi-Fi and mobile data. Licensing, checked 4 November 2026: the kernel module is GPLv2, like the Linux kernel itself, and so are wireguard-tools (the wg and wg-quick commands) and the WireGuardNT driver for Windows. The WireGuard for Windows client, the macOS and iOS apps and wireguard-go, the userspace implementation in Go, are MIT licensed, and the Android app is Apache 2.0. All of these licenses allow commercial use at no cost. "WireGuard" and the WireGuard logo are registered trademarks of Jason A. Donenfeld, and development is funded by donations, including monthly sponsors through GitHub Sponsors. Setup on Linux: install the package (apt install wireguard on Debian and Ubuntu, or wireguard-tools on Fedora, Arch and others), create a key pair with wg genkey and wg pubkey, and write a short config file. The [Interface] section holds the private key, the tunnel address and a listen port, commonly 51820/UDP; each [Peer] section holds a public key, its AllowedIPs and, on a client, the server's endpoint. wg-quick up wg0 starts the tunnel and adds routes for every peer's AllowedIPs, and wg show lists each peer's latest handshake and traffic. AllowedIPs works as both routing table and access list: a packet from a peer is accepted only when its source address falls inside that peer's AllowedIPs. A client behind NAT that must receive traffic sets PersistentKeepalive, and the project suggests 25 seconds. PreUp, PostUp, PreDown and PostDown lines run commands, such as firewall rules, as the tunnel comes up or goes down. Setup on Windows fleets: admins can push the MSI packages through Group Policy or any tool that installs MSIs (the DO_NOT_LAUNCH property keeps the app from opening after install), then install a tunnel as a Windows service with wireguard /installtunnelservice and a .conf file. Config files copied into the manager service's Configurations folder are encrypted with DPAPI and made readable only by Local System. The tray app opens for built-in Administrators, and a registry setting adds a limited view for Network Configuration Operators. wireguard /update can run as a daily scheduled task, wireguard /dumplog /tail streams the log to a collector, and PreUp and PostUp scripts run on Windows only when an admin registry key allows them. WireGuard on OPNsense: since OPNsense 24.1 (30 January 2024) WireGuard ships in the core install, so the os-wireguard plugin step in older guides no longer applies. The OPNsense road warrior guide follows this order. Under VPN > WireGuard > Instances, add an instance, generate its keys with the cogwheel, and set a listen port such as 51820 and a tunnel address such as 10.10.10.1/24. Under Peers, add each client with its public key and one /32 address inside that subnet as its Allowed IP, or use the Peer generator to build client configs with a QR code for the mobile apps, then select the peers on the instance. Turn WireGuard on under General. Assign the wg device as an interface, which creates a firewall alias for the tunnel subnet and an IPv4 source NAT rule. Then add a WAN rule that passes UDP to the listen port and a rule on the WireGuard interface for what clients may reach; the guide also adds MSS clamping under Firewall > Settings > Normalization. A site-to-site link between two OPNsense firewalls uses one instance on each side, with the other site's subnets in that peer's Allowed IPs. pfSense adds WireGuard as a package from its Package Manager. Pricing, checked 4 November 2026: WireGuard is free at any scale, with no paid edition, license key or per-user fee from the project. The costs sit around it: the server or firewall that ends the tunnels, staff time to issue and revoke keys, and any managed service on top. Tailscale, NetBird, Netmaker and Firezone sell hosted control planes with their own plans, and firewalls such as OPNsense, pfSense and IPFire include WireGuard with the platform. Limits to plan for: the project leaves key distribution and pushed configuration to other layers, so WireGuard itself has no user directory, SSO, MFA, dynamic address assignment or central console, and each client address is set by hand. It runs over UDP only by design, so a network that allows only TCP 443 needs a wrapper such as udp2raw or udptunnel. It is not post-quantum secure by default; the optional pre-shared key adds a post-quantum layer. A server keeps each peer's latest endpoint address in memory while the interface is up, which matters to privacy-focused services. Logging is minimal: wg show gives handshake times and byte counts, and the Windows app adds a diagnostic log. For MSPs and IT teams: plain WireGuard fits site-to-site links between firewalls, admin access to management networks and small groups of remote users whose peers change rarely. Give each client network its own instance and address range, keep a register of which key belongs to which person or device, and remove a peer the day a technician leaves. Where users join and leave often, or SSO and MFA are required, a control plane ties keys to identity: Tailscale runs a WireGuard mesh with identity-based access rules and a hosted coordination server, Headscale is an open-source, self-hosted implementation of that control server, NetBird adds SSO, MFA and access policies, self-hosted or in the cloud, and Netmaker and Firezone are further options. OpenVPN fits where tunnels must run over TCP 443, and IPsec, for example strongSwan, where the other end is a cloud VPN gateway or another company's firewall. In Kubernetes, Calico and Cilium can use WireGuard to encrypt traffic between nodes.
image media

Key Features

In-Kernel Performance

Runs in the Linux kernel since 5.6, with high throughput and low latency

Modern Fixed Cryptography

Curve25519, ChaCha20-Poly1305 and BLAKE2s, with no cipher negotiation to misconfigure

Public-Key Peers

Each peer is identified by a public key and its allowed IPs, much like SSH keys

Simple Configuration

Small config files managed with the wg and wg-quick command-line tools

Roaming

Peers keep working when they change networks or IP addresses

Small Auditable Codebase

A few thousand lines of code, far smaller than OpenVPN or IPsec stacks

Pros and Cons

Pros

Free and open source

GPLv2 kernel module and tools, MIT apps, no licensing cost at any scale

Secure by design

Modern fixed cryptography and a small, audited codebase

Easy to configure

A tunnel needs only keys and allowed IPs

Foundation for other tools

Tailscale, NetBird, Netmaker, OPNsense, pfSense and IPFire build on it, so skills carry over

Fast

In-kernel and multi-threaded; the project reports it well ahead of OpenVPN and ahead of IPsec in some tests

Cons

No user management

No built-in directory, SSO, MFA or central admin console; keys are managed by hand or by another product

Static peer addressing

No dynamic IP assignment; each client address is set in configuration

Endpoint addresses kept in memory

The server keeps the last known IP of each peer until restart, a concern for privacy-focused services

UDP only

No TCP mode by design; networks that allow only TCP 443 need a wrapper such as udp2raw

Not post-quantum by default

Post-quantum protection needs the optional pre-shared key or a post-quantum handshake run on top

Feature Comparison

Features
Cost and Licensing
Loading the comparison

Comments

No reviews yet. Be the first to share your experience with WireGuard.

Frequently Asked Questions

/vendor/wireguard