Comparison - Pangolin vs. OpenVPN
OpenVPN has been the default self-hosted VPN for two decades. There are two versions most teams run: the open-source OpenVPN daemon, often called Community Edition, which you configure by hand, and OpenVPN Access Server, the commercial package with a web UI and licensing by connection. Both follow the classic VPN design: one server, users connect to it, and the server routes them into the network. This article compares both with Pangolin, which is also open source and self-hostable but organizes access around resources rather than networks.
What is Pangolin?
Pangolin is an open-source zero-trust network access platform built on WireGuard. You install a lightweight connector, called a site, on a machine inside a network you want to reach. The site only makes outbound connections, so the network needs no public IP, no port forwarding, and no inbound firewall rule.
Anything the site can reach can become a resource, and you grant users, roles, and machine clients access to each one. Public resources go through Pangolin's identity-aware reverse proxy: web apps on your own domains, and SSH, RDP, and VNC sessions in the browser, all behind Pangolin login. Private resources need the Pangolin client and cover hosts, CIDR ranges, private HTTPS, pangolin ssh, and exit nodes. Clients connect to sites peer-to-peer with NAT hole punching and fall back to a relay when they can't.
You can self-host Pangolin as Community Edition (AGPLv3) or Enterprise Edition, which is free for personal use and businesses under $100,000 in annual revenue, or use Pangolin Cloud.
What is OpenVPN?
OpenVPN is a TLS-based VPN protocol and daemon, licensed under GPLv2. The current release series is 2.7. You run it on a server with a reachable UDP or TCP port, commonly 1194 or 443. Clients authenticate with certificates from a PKI you manage, usually with easy-rsa, optionally combined with a username and password through a plugin. Each client gets an address on a tunnel subnet, and you push routes for the networks it should reach. Access control is done with routes, per-client config files, and firewall rules on the server. There's no web UI, user directory, or MFA built in.
OpenVPN Access Server is the commercial product built on the OpenVPN protocol. It adds an admin web UI, a self-service client portal for downloading profiles, authentication through local users, PAM, LDAP, RADIUS, and SAML, built-in TOTP MFA, per-user and per-group access rules, active-active clustering, and Data Channel Offload for kernel-level encryption. It runs on Linux, as a virtual appliance, or from cloud marketplaces. Licensing is by concurrent connection: free for two connections, then about $7 per connection per month, with custom pricing above 2,000. Clients use OpenVPN Connect.
OpenVPN Inc. also sells CloudConnexa, a hosted service with ZTNA features, priced per seat.
At a glance
| Feature | Pangolin | OpenVPN (Community and Access Server) |
|---|---|---|
| Architecture | Control plane plus outbound connectors in each network | Central VPN server that clients connect to and route through |
| Open ports on your network | None; sites only dial out | VPN server needs a reachable UDP or TCP port |
| Access model | Users and roles per resource; deny by default | Community: routes and firewall rules. Access Server: user and group rules on subnets, hosts, and ports |
| Identity | Built-in users or any OIDC provider; MFA; session revalidation | Community: certificates and plugins. Access Server: LDAP, RADIUS, SAML, PAM, TOTP |
| Browser access | Web apps on your domains; SSH, RDP, VNC in the browser | None; all access through the VPN client |
| Multiple sites | One connector per site; users reach all granted sites at once | Site-to-site tunnels to the server, or a server per site |
| Protocol | WireGuard | OpenVPN over TLS; DCO for kernel offload |
| License | AGPLv3; Enterprise Edition free under $100k revenue | Community: GPLv2. Access Server: commercial, per connection |
Detailed comparison
Architecture
OpenVPN is hub-and-spoke with the VPN server as the hub. Users connect to it, and it forwards their traffic into the networks it can reach. The server needs a public address and an open port, and every byte of user traffic passes through it. To reach a second office or a cloud VPC, you either run a site-to-site tunnel from there back to the server or stand up another server and give users another profile.
Pangolin also has a central server, but it coordinates rather than carries traffic. Sites in each network dial out to it. A client that needs a private resource builds a WireGuard tunnel directly to the site that can reach it, using NAT hole punching, and only falls back to relaying through the server when the direct path fails. Users can reach resources at every site they're granted at the same time, and when two sites can reach the same network, Pangolin picks the best one and fails over automatically.
Access control
With Community Edition, access control is whatever you build: client-specific config files, pushed routes, and iptables or nftables rules on the server keyed on each client's tunnel address. It's flexible but easy to get wrong, and it drifts as people come and go.
Access Server improves this with user and group rules in the web UI that allow access to subnets, hosts, and ports, and group mapping from LDAP, RADIUS, or SAML. It's still network-level: a user is given access to address ranges.
Pangolin is deny by default and organized around resources. You define a host, a CIDR range, a private HTTPS app, an SSH target, or a public web app, and grant users and roles access to each. Private resources can be limited to specific ports. Aliases give hosts names like nas.office.internal that resolve only over the tunnel and help when sites use overlapping subnets.
Identity and devices
Community Edition authenticates with certificates. Revoking access means maintaining a certificate revocation list and distributing it, and user management lives outside OpenVPN entirely.
Access Server adds LDAP, RADIUS, and SAML integration and TOTP, though users still connect with a VPN profile tied to the server, and access is still granted to address ranges.
Pangolin's clients sign in through a web login with Pangolin users or any OIDC provider, including MFA, and use ephemeral WireGuard keys for tunnels, so there are no long-lived client certificates or profiles to hand out. Pangolin can revalidate sessions against the identity provider so offboarding takes effect within minutes, collect device posture, and require admin approval for each new device per role. Machine clients for servers and CI have their own revocable credentials.
Browser access
OpenVPN has no browser path. Anyone who needs an internal web app, a server console, or a Windows desktop needs a VPN profile and the client.
Pangolin includes a reverse proxy. Web apps can be published on your own domains with automatic certificates and opened from any browser after SSO, a PIN, a passcode, an email code, or a shareable link. SSH, RDP, and VNC sessions run in the browser too. That covers contractors, vendors, and personal devices you'd rather not put on the VPN.
Performance
WireGuard, which Pangolin uses, is generally faster than OpenVPN on the same hardware and reconnects quickly when a device changes networks. OpenVPN's Data Channel Offload, available in Access Server and recent Community releases, narrows the gap considerably by moving encryption into the kernel. Pangolin's direct client-to-site connections also mean traffic doesn't have to pass through a central server, which matters more than raw cipher speed when users and resources are in different places.
Operations
Community Edition is a daemon and a set of config files. You manage the PKI, write client configs, set up routing and firewall rules, and build any UI, monitoring, or logging you need.
Access Server packages most of that in a web UI and adds clustering for high availability. Licensing is by concurrent connection, which makes costs predictable for small teams but grows with headcount.
Pangolin provides a dashboard, API, and YAML blueprints for configuration; health checks and alerting for sites and resources; and logs for authentication, admin actions, requests, network sessions, and SSH sessions, with streaming to a SIEM on Cloud and Enterprise Edition. Self-hosted Enterprise Edition adds clustering.
Which one fits
OpenVPN Community Edition fits when you want a mature, GPL-licensed VPN for a small, stable set of users, you're comfortable managing a PKI and firewall rules, and full network access is acceptable.
OpenVPN Access Server fits teams that want a classic remote access VPN with a web UI, directory integration, and per-connection pricing, and don't need browser access or per-resource policy.
Pangolin fits when you want to stop opening ports for remote access, grant access to specific resources instead of whole networks, give some users browser access with no client, and connect several sites without building a hub. It's open source and self-hostable like OpenVPN, with a cloud option if you'd rather not run the server.
FAQ
Is Pangolin an OpenVPN alternative?
Yes. Pangolin replaces the VPN server with outbound connectors and resource-based access, and adds browser access through its reverse proxy.
Can I self-host Pangolin like OpenVPN?
Yes. Community Edition is AGPLv3, and Enterprise Edition is free for personal use and businesses under $100,000 in annual revenue. Both run on a single server, and Enterprise Edition supports clustering.
Does Pangolin use the OpenVPN protocol?
No. Pangolin uses WireGuard for its tunnels and HTTPS for browser access.
Related comparisons
Try Pangolin
Get started with Pangolin. You can self-host the server or sign up for the cloud and try it with no commitment.
Get in touch
If you want more detail on how Pangolin can fit your setup, reach out.
About Pangolin
Pangolin is the open-source access platform that lets IT and security teams connect their workforce, AI agents, and infrastructure without the friction of legacy VPNs and stitched-together security tools. By unifying a zero-trust VPN, zero-trust reverse proxy, privileged access management, and an identity-aware AI gateway under one policy model, Pangolin helps organizations shrink their attack surface, contain stolen credentials, and pass audits with less work. Teams can roll it out one service at a time, self-hosted or on Pangolin Cloud, and verify exactly how their access is secured because every component is open source.
