Comparison - Pangolin vs. Fortinet
A lot of companies get remote access from the same box that runs their firewall. For Fortinet customers that has meant FortiGate SSL VPN with FortiClient, and over the last two years it has meant a migration. FortiOS 7.6.3 removed SSL VPN tunnel mode from every FortiGate model, and Fortinet now points customers to IPsec VPN or to its ZTNA products. If you're in the middle of that decision, this article compares Pangolin with each of Fortinet's remote access options and explains how the two can run side by side.
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 rule on the firewall.
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 use Pangolin Cloud, self-host the whole stack, or use the cloud control plane with your own remote nodes.
What Fortinet offers for remote access
Fortinet has several remote access options, and which ones you can use depends on your FortiGate model, FortiOS version, and licenses.
SSL VPN was the default for years. Users ran FortiClient in tunnel mode, or used a browser-based web portal, against a listener on the FortiGate's WAN interface. Starting with FortiOS 7.6.3, released in 2025, tunnel mode is no longer supported on any FortiGate model, and tunnel-mode configuration is not kept on upgrade. On models that still have the web portal, it has been renamed Agentless VPN. Many smaller models, including the 40F, 60F, and 90G and lower G-series units, have no SSL VPN at all in 7.6.
IPsec dial-up VPN is Fortinet's recommended replacement for tunnel mode. Users connect with FortiClient, and IPsec can run over TCP 443 for networks that block UDP. Like SSL VPN, it terminates on the FortiGate and gives users network-level access shaped by firewall policies.
Universal ZTNA uses the FortiGate as an access proxy. FortiClient EMS manages endpoints, issues device certificates, and tags devices based on posture, and the FortiGate checks the user, the certificate, and the tags before proxying HTTPS, TCP, or SSH to an application. FortiOS 7.6.1 added agentless ZTNA web access through a portal with bookmarks. ZTNA needs FortiClient EMS licensing on top of the FortiGate.
FortiSASE is Fortinet's cloud-delivered option, running FortiOS security in Fortinet's points of presence for internet and private access.
FortiGate SSL VPN has also been a frequent target. CISA's Known Exploited Vulnerabilities catalog lists several FortiOS SSL VPN flaws that were used in ransomware campaigns, including CVE-2018-13379, CVE-2022-42475, and CVE-2023-27997. That history is one of the reasons many teams want remote access off the firewall's internet-facing interface altogether.
At a glance
| Feature | Pangolin | FortiGate VPN (IPsec, SSL VPN) | Fortinet ZTNA |
|---|---|---|---|
| Inbound exposure | None on your networks; sites only dial out | VPN listener on the FortiGate | Access proxy listens on the FortiGate |
| Access model | Users and roles per resource; deny by default | Network-level access shaped by firewall policies on address objects | Rules per application, using EMS device tags |
| Browser access | Web apps on your domains; SSH, RDP, VNC in the browser | Agentless VPN portal on supported models | Agentless ZTNA portal in 7.6.1+ |
| Client | Pangolin client for Windows, macOS, Linux, iOS, Android, CLI | FortiClient | FortiClient, managed by EMS for posture |
| Data path | Client to site directly when possible; relay otherwise | Through the FortiGate | Through the FortiGate, or FortiSASE points of presence |
| Multi-site | One connector per site; users reach all granted sites at once | Per-FortiGate gateways, or site-to-site VPN behind a hub | Access proxy configured on each FortiGate |
| Open source | AGPLv3 or commercial license | Proprietary | Proprietary |
| Firewall and IPS | Not a firewall; runs alongside one | Full NGFW, IPS, web filtering, SD-WAN | Same FortiGate; adds EMS licensing |
Detailed comparison
Where access terminates
FortiGate SSL VPN, IPsec dial-up, and the ZTNA access proxy all terminate on the FortiGate. Something has to listen on an internet-facing interface for users to reach it, and that listener is part of the firewall's own software. When a vulnerability shows up there, the device protecting the network is the one exposed.
Pangolin moves the listener off your network. Sites dial out to the Pangolin server, which can be Pangolin Cloud, a server you host in a DMZ or a cloud VPC, or a remote node you run. Users connect to that server or directly to a site through NAT hole punching. The firewall only has to allow outbound traffic from the site, which it usually already does.
Access model
SSL VPN and IPsec dial-up give a connected user a tunnel into the network, and firewall policies decide what that user's group can reach. It works, but policies tend to grow broad over time, and every new app means another address object and rule.
Fortinet ZTNA narrows this to per-application rules with device tags from EMS, which is a real improvement and a good fit for shops that already run EMS. It also adds components: EMS, device certificates, tagging rules, and access proxy configuration on each FortiGate.
Pangolin starts from deny by default. You define a resource, such as a single host, a subnet, or a web app, and grant users and roles access to it. Private resources can be limited to specific ports. Roles can come straight from your identity provider's groups through auto-provisioning, and you can manage everything in the dashboard, API, or YAML blueprints.
Browser access
On FortiGates that still have it, the Agentless VPN portal provides bookmarks to web apps and RDP or SSH sessions, and FortiOS 7.6.1's agentless ZTNA portal does something similar through the access proxy. Neither is available on every model and are not a central reverse proxy tied to your domains.
Pangolin's public resources give each web app its own URL on your domain with an automatic certificate, and users sign in with SSO, a PIN, a passcode, an email code, or a shareable link. Rules on path, IP, country, and ASN control who gets through. SSH, RDP, and VNC run in the browser after the same login. This works the same regardless of what firewall you run.
Multiple sites
With FortiGate, each location's firewall can be its own VPN gateway, or you build site-to-site tunnels back to a hub and send remote users through it. Users often have to pick a gateway, and hub designs send branch traffic through headquarters.
With Pangolin, you install a site at each location and users reach every resource they're granted at the same time, without picking a gateway. If two sites can reach the same network, Pangolin routes each client through the best one and fails over automatically. Locations with overlapping subnets can be told apart with aliases. See branch office networking for an example.
Identity and devices
FortiGate VPNs authenticate against local users, LDAP, RADIUS, or SAML, often with FortiAuthenticator or FortiToken for MFA. ZTNA adds device identity through EMS certificates and posture-based tags.
Pangolin uses built-in users or any OIDC provider, such as Entra ID, Okta, or Google Workspace, and can revalidate sessions against the provider every few minutes so offboarding takes effect quickly. Its clients report device posture such as disk encryption, firewall state, and antivirus, and Pangolin can require admin approval for each new device per role. For SSH, Pangolin can create Linux accounts just in time, sign short-lived certificates, and apply sudo rules from roles.
Running both
Pangolin doesn't replace the FortiGate as a firewall. It doesn't do IPS, web filtering, SD-WAN, or perimeter policy. A common setup keeps the FortiGate as the network firewall and moves remote user access to Pangolin, which removes the internet-facing VPN listener and avoids the SSL VPN migration entirely. Pangolin sites run as a container, a VM, or a binary on any Linux, Windows, or macOS host behind the FortiGate.
Which one fits
Fortinet fits when you want one vendor for firewall, SD-WAN, and remote access, already run FortiClient EMS, and have the licenses and staff to deploy ZTNA across your FortiGates.
Pangolin fits when you want remote access that doesn't depend on a listener on your firewall, works the same on every network regardless of firewall model or firmware, and gives browser access to web apps, SSH, RDP, and VNC alongside client-based private access. It's open source, can be self-hosted, and can sit behind the FortiGate you already have.
FAQ
Does Pangolin work behind a FortiGate?
Yes. Sites only need outbound access. FortiGate is one of the firewalls that usually allows direct peer-to-peer connections between Pangolin clients and sites without configuration changes.
What happened to FortiGate SSL VPN?
In FortiOS 7.6.3 and later, SSL VPN tunnel mode is not supported on any FortiGate model, and its configuration is removed on upgrade. Web mode was renamed Agentless VPN on models that keep it. Fortinet recommends IPsec VPN or ZTNA instead.
Is Pangolin a replacement for FortiClient VPN?
For remote user access, yes. Pangolin's client gives users access to private hosts and subnets, and its reverse proxy covers browser access. It doesn't replace FortiClient's endpoint protection features.
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.
