OpenVPN Access Server and Cloud pricing in 2026.
| Tier | List price (2026) | Concurrent tunnels / users | Notable features |
|---|
| OpenVPN AS self-hosted, 5 connections | $5 per connection per year | 5 | LDAP/AD, basic policy |
| OpenVPN AS self-hosted, 50 connections | $9 per connection per year | 50 | SAML, RADIUS, REST API |
| OpenVPN AS self-hosted, 100+ connections | $15 per connection per year | 100+ | HA clustering, dedicated support |
| OpenVPN Cloud (hosted) | $5-$10 per user per month | Per-seat, no per-site cap | SCIM, no appliance cap |
| OpenVPN Enterprise support | $3,000-$15,000 per year | Stacked on license | 24x7, named TAM |
Source: OpenVPN.net pricing page, retrieved September 14, 2026.
For a 250-employee enterprise that wants full SAML and dedicated support, OpenVPN AS self-hosted lands at roughly $1,500-$3,750 per year in licenses plus $3,000-$15,000 per year in support, totaling $4,500-$18,750 - which is competitive with Netmaker Business at the same scale.
WireGuard vs OpenVPN: 2026 commercial wrapper comparison.
| Platform | Underlying protocol | Per-tunnel cost | Identity integration | FIPS mode |
|---|
| Netmaker Business | WireGuard | $5-$7 per tunnel per month | OIDC (Okta, Azure AD, Keycloak) | No |
| Firezone Cloud | WireGuard | $0.50-$3 per user per month | SAML 2.0, OIDC | No |
| Tailscale Premium | WireGuard (Noise protocol) | $8 per device per month | SAML, SCIM, native | No |
| OpenVPN AS | OpenVPN (TLS) | $5-$15 per connection per year | LDAP, RADIUS, SAML | Yes (OpenSSL FIPS provider) |
| Algo VPN (self-hosted) | WireGuard | Free + 1-3 dev-days per site | DIY OIDC | No |
Source: Netmaker, Firezone, Tailscale, OpenVPN, Algo GitHub - September 14, 2026.
The TCO delta between the cheapest WireGuard wrapper (Firezone Starter at $0.50/user/mo) and the most expensive OpenVPN deployment (AS 100+ at $15/connection/yr plus $15K support) is roughly 30x at 250 seats, which is the largest single-line item in a 2026 enterprise VPN procurement.
Migration playbook: parallel cutover over 4-8 weeks.
The most reliable 2026 cutover pattern is dual-stack for 30 days: keep OpenVPN primary, deploy WireGuard to 2-3 pilot sites, validate NAT, firewall policy, and DNS resolution, then flip traffic once.
Firewall changes are the most-cited blocker: open UDP 51820 (or the chosen port), update inspection rules for WireGuard traffic, and confirm WireGuard is recognized as a known application on Palo Alto Networks PAN-OS 11.1+, Fortinet FortiOS 7.6+, and Check Point R81.20+ (Vendor Docs, September 2026). On older firmware WireGuard traverses as generic UDP and can be dropped by aggressive DPI; plan a firmware upgrade if you are on PAN-OS 10.x or earlier.
Identity is the second blocker: native WireGuard has no SAML/OIDC, so you must front it with Netmaker, Firezone, or Tailscale - or accept pre-shared key distribution via a config-management tool like Ansible, SaltStack, or Puppet. Most enterprises budget 20-40 engineering hours for a full migration, plus another $5,000-$15,000 for the wrapper subscription during parallel-run.
Regulated workloads still default to OpenVPN.
U.S. federal agencies, DoD contractors, and any organization bound by FIPS 140-2 or 140-3 contracts must use FIPS-validated cryptography, which excludes WireGuard's ChaCha20-Poly1305 and Curve25519 in 2026.
OpenVPN Access Server with Ubuntu 22.04 + OpenSSL 3.0.8 FIPS provider is the most common configuration; Cisco AnyConnect with FIPS mode is the alternative (NIST CMVP, September 2026). HIPAA and PCI-DSS do not require FIPS-validated cryptography explicitly - AES-256-GCM and RSA-4096 are acceptable - so WireGuard remains compliant for healthcare and retail workloads once the audit trail covers identity and key rotation.
Bottom line for 2026 buyers.
WireGuard is the right default for new enterprise deployments that are not bound by FIPS contracts and that can integrate OIDC/SAML via a commercial wrapper; OpenVPN Access Server remains the right fit for FIPS-bound workloads, complex PKI, and legacy client support. Per-tunnel cost favors WireGuard wrappers by 30-60% at 100-500 seat scale, throughput favors WireGuard by 5-8x per CPU core on 10 Gbps uplinks, and audit posture favors WireGuard for code-surface arguments and OpenVPN for TLS maturity.
Alternatives to consider
If neither contender in this comparison fits, these adjacent options are worth a look:
- Premium tier (when both candidates are mid-tier and you want the flagship experience).
- Budget tier (when you'd use the cheapest viable alternative anyway).
- Niche alternative (when one specific dimension — battery, ecosystem, weight — dominates your decision).
FAQs
Is WireGuard production-ready for enterprise in 2026?
Yes - WireGuard is production-ready in 2026 with Linux kernel 5.6+ (January 2020), OpenBSD 6.8+ (October 2020), and Windows via WireGuardNT 0.4+ (2021). Cure53 (2020) and Trail of Bits (2023) audits are public; commercial wrappers from Netmaker, Firezone, and Tailscale handle identity and management. Most enterprises run WireGuard as primary with OpenVPN as fallback for FIPS-bound sites.
Does WireGuard support split tunneling?
Yes - WireGuard's AllowedIPs field controls split tunneling at the route level. Each peer has an AllowedIPs list that tells the kernel which destination subnets traverse the tunnel; everything else uses the local default route. Netmaker and Firezone add a UI layer for managing AllowedIPs across thousands of peers.
What port does WireGuard use?
WireGuard uses UDP 51820 by default but can be configured to any UDP port. The WireGuard developers recommend UDP for lowest overhead, and most commercial wrappers let you change the port during setup. Running WireGuard on UDP 443 is technically possible but unusual because most enterprises expect TLS on 443.
Can WireGuard traverse restrictive firewalls?
WireGuard's pure-UDP design is dropped by some restrictive firewalls (hotels, captive portals, country-level DPI). OpenVPN's ability to run over TCP 443 is the reason some enterprises keep OpenVPN as a fallback for road warriors. Some commercial wrappers (Pritunl, OpenVPN Cloud) offer TCP fallbacks for WireGuard; expect 20-40% throughput penalty versus UDP.
What about WireGuard for site-to-site VPN on AWS or Azure?
AWS Site-to-Site VPN added native WireGuard support in 2024 and Azure Virtual WAN added WireGuard peering in 2025; both are free with the underlying VPN gateway hourly charge. Self-hosted WireGuard on EC2 or Azure VMs is also common for mesh topologies - a c6i.large handles roughly 2-4 Gbps of WireGuard throughput at ~$0.10-$0.15 per hour.
Is Netmaker open source?
Netmaker is dual-licensed: the core server is GPLv3 open source on GitHub (self-hostable free), and Netmaker Business is the paid managed offering with SSO, RBAC, and commercial support. Firezone is also dual-licensed (Apache 2.0 core + paid Cloud). Tailscale's headscale is open source but the managed Tailscale service is closed source.