Pangolin

Name: Pangolin
Brand: Pangolin

AI Native

Tailored software for builders, by builders.

Est 2025|Raised $5.2M

LinkedIn 824|Web traffic 58K|FTEs 4|HQ San Francisco, California, US

MarketsPrivileged Access Management (PAM)Security Service Edge (SSE)

Published Sep 26, 2026

01Common complaints

- Organizations that require audited enterprise compliance artifacts today: if procurement mandates SOC 2 Type II / ISO 27001 evidence and a standard vendor due‑diligence pack, Pangolin’s publicly verifiable posture was unclear based on accessible sources. - Organizations lacking operational capacity: teams without staff comfortable with DNS, VPS networking, and ongoing patching may face higher operational risk compared with managed ZTNA alternatives (Twingate, Cloudflare Zero Trust, Zscaler ZPA). - Organizations needing a broader secure web gateway (SWG) suite: Pangolin is primarily focused on remote access, tunneling, and identity-aware proxying rather than a full SWG/CASB platform. - Organizations requiring a published, predictable price list for procurement: competitors with transparent per-user pricing may be easier for standard procurement workflows.

Deal disqualifiers (poor fit)

Requires audited enterprise compliance reports (SOC 2 / ISO 27001) immediately and a downloadable vendor due‑diligence pack
Needs a fully managed service with formal SLAs and guaranteed support response times
Requires integrated SWG/CASB/DLP capabilities within the same platform

Reported by users (community)

Connectivity interruptions and resources becoming unreachable in some deployment configurations.
Confusion and errors related to SSH access configuration (e.g., resource not found errors).
Secrets management concerns, including examples of plaintext secrets in configuration files; operators need to enforce secure permissions and secret storage.

Vendor-acknowledged limitations / roadmap

Roadmap details and vendor-acknowledged limitations were not comprehensively captured from accessible official sources in this research.

Why some customers might leave (churn reasons; evidence-limited)

Direct narratives of leaving were limited in the reviewed sources. Likely churn drivers suggested by complaints include:

Troubleshooting complexity (connectors, DNS, VPS networking)
Need for a fully managed enterprise product with SLAs and accessible compliance documentation
Operator burden for security hardening and secrets management in self-hosted deployments

02Why they buy

Observed advantages (from docs/community)

Open-source codebase with a self-host option while a hosted control plane is also available.
An integrated approach that combines reverse proxy functionality with ZTNA private access in a single stack.
WireGuard-based architecture and site/connector model that enable access to resources behind NAT and firewalls.

Areas where competitors have advantages

Packaged compliance and procurement readiness (Cloudflare, Zscaler, Twingate)
Support maturity and formal SLAs from commercial vendors
Broader security suite breadth (integrated SWG/DLP/CASB capabilities)

03Field reports

Review platforms (G2 / TrustRadius / Gartner Peer Insights)

- Gartner Peer Insights: No clearly relevant or accessible product page for Pangolin was retrieved in the searches performed (possible naming ambiguity with other "Pangolin" brands). - G2: Search results returned a different entity (a marketing firm with a similar name), not Pangolin; therefore G2 did not provide usable reviews for this product in the searches conducted. - TrustRadius: No confirmed Pangolin review page was found in the accessible results. Interpretation: mainstream enterprise review platforms did not provide confirmed coverage for Pangolin in the queries performed; naming collisions and the product's relative novelty on enterprise review sites may be factors.

Community / social proof (Reddit) — summarized sentiments (positive and negative)

Representative community sentiment from forum posts includes both positive adoption reports and reports of friction. Examples below summarize common themes observed in Reddit threads: Positive / adoption comments (summarized): - Some users reported migrating from Cloudflare Tunnels/Access and found Pangolin straightforward to deploy for homelab use cases, commenting that it met their needs for exposing private resources. - Other users described Pangolin as a tunneled mesh reverse proxy with identity and access control features and a dashboard UI, and noted integrations with common tooling (e.g., proxying with Traefik, third-party plugins). Neutral-to-positive (functional descriptions): - Users have described the product as combining reverse proxy functionality with SSO and a dashboard for administration; some referenced available plugins such as GeoBlock and Crowdsec. Negative / friction & issues (summarized): - Reports of plaintext secrets appearing in some configuration files and concerns about secret handling and permissions. - Connectivity and reachability problems in specific VPS or site connector setups. - Error reports for specific features (for example, SSH access errors such as resource not found) and uncertainty about debugging.

Why customers choose Pangolin (inferred from discussions)

Drivers include:

Preference for a self-hosted alternative to Cloudflare Tunnels/Access
An integrated approach combining reverse proxying, identity-aware access, and WireGuard-based tunnels
Ease of exposing home or private services without opening inbound ports in some common homelab/SB setups

Vendor case studies

No formal vendor-published case studies with quantified ROI were located in the accessible sources during this research.

Third-party / press "case-like" signals

A Linux-focused article describing a recent release noted community interest and the introduction of mobile apps; this is an indicator of momentum but does not substitute for documented enterprise case studies.

Critical note: community metrics such as repository stars measure interest and adoption at the community level and are not direct evidence of standardized enterprise deployments or ROI.

04Best fit

Company sizes (practical ranges)

Homelab / prosumers / small teams: single users up to a few dozen, with tolerance for self-host operational work
SMB / mid-market technical teams: tens to a few hundred employees with DevOps/SRE capability and a preference for open-source

Industries

Based on vendor positioning and community usage patterns: IT/OT, IoT, engineering-heavy organizations, and teams that require secure access to internal services.

Roles/personas

Decision makers: Head of IT, Security Engineering lead, Platform Engineering, SMB CTO
End users: Developers, IT administrators, contractors requiring scoped access to internal tools

Qualification criteria (great fit)

Requires resource-level access controls instead of full network VPNs
Has capacity to operate a VPS and site connectors
Values open-source and the option to self-host

05The pitch

What the product does (objective core value proposition)

Pangolin (official product site) is an open-source, identity-aware remote access platform built on WireGuard that combines: - Tunneled reverse proxy (browser-based access to web apps) - Zero Trust "VPN-style" private access (client-based access to SSH/RDP/databases/subnets) The core objective is to provide least-privileged access to specific resources (apps/services/routes) rather than full network access typical of legacy VPNs, and to enable teams to expose private resources without opening inbound ports or requiring public IPs (via outbound connectors and NAT traversal).

Target market & positioning

Vendor materials describe Pangolin as a consolidated remote access solution positioned as an alternative to legacy VPNs, targeting environments such as:

IT/OT and engineering contexts
IoT / edge deployments
Hybrid networks (on‑prem + cloud + remote sites)

Community adoption appears notable among self-hosters and homelab operators seeking a self-hosted alternative to Cloudflare Tunnels/Access and some commercial ZTNA products.

Get a comprehensive analysis of Pangolin including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Sep 26, 2026

01Common complaints

Organizations that require audited enterprise compliance artifacts today: if procurement mandates SOC 2 Type II / ISO 27001 evidence and a standard vendor due‑diligence pack, Pangolin’s publicly verifiable posture was unclear based on accessible sources.
Organizations lacking operational capacity: teams without staff comfortable with DNS, VPS networking, and ongoing patching may face higher operational risk compared with managed ZTNA alternatives (Twingate, Cloudflare Zero Trust, Zscaler ZPA).
Organizations needing a broader secure web gateway (SWG) suite: Pangolin is primarily focused on remote access, tunneling, and identity-aware proxying rather than a full SWG/CASB platform.
Organizations requiring a published, predictable price list for procurement: competitors with transparent per-user pricing may be easier for standard procurement workflows.

Deal disqualifiers (poor fit)

Requires audited enterprise compliance reports (SOC 2 / ISO 27001) immediately and a downloadable vendor due‑diligence pack
Needs a fully managed service with formal SLAs and guaranteed support response times
Requires integrated SWG/CASB/DLP capabilities within the same platform

Reported by users (community)

Connectivity interruptions and resources becoming unreachable in some deployment configurations.
Confusion and errors related to SSH access configuration (e.g., resource not found errors).
Secrets management concerns, including examples of plaintext secrets in configuration files; operators need to enforce secure permissions and secret storage.

Vendor-acknowledged limitations / roadmap

Roadmap details and vendor-acknowledged limitations were not comprehensively captured from accessible official sources in this research.

Why some customers might leave (churn reasons; evidence-limited)

Direct narratives of leaving were limited in the reviewed sources. Likely churn drivers suggested by complaints include:

Troubleshooting complexity (connectors, DNS, VPS networking)
Need for a fully managed enterprise product with SLAs and accessible compliance documentation
Operator burden for security hardening and secrets management in self-hosted deployments

02Why they buy

Observed advantages (from docs/community)

Open-source codebase with a self-host option while a hosted control plane is also available.
An integrated approach that combines reverse proxy functionality with ZTNA private access in a single stack.
WireGuard-based architecture and site/connector model that enable access to resources behind NAT and firewalls.

Areas where competitors have advantages

Packaged compliance and procurement readiness (Cloudflare, Zscaler, Twingate)
Support maturity and formal SLAs from commercial vendors
Broader security suite breadth (integrated SWG/DLP/CASB capabilities)

03Field reports

Review platforms (G2 / TrustRadius / Gartner Peer Insights)

Gartner Peer Insights: No clearly relevant or accessible product page for Pangolin was retrieved in the searches performed (possible naming ambiguity with other "Pangolin" brands).
G2: Search results returned a different entity (a marketing firm with a similar name), not Pangolin; therefore G2 did not provide usable reviews for this product in the searches conducted.
TrustRadius: No confirmed Pangolin review page was found in the accessible results.

Interpretation: mainstream enterprise review platforms did not provide confirmed coverage for Pangolin in the queries performed; naming collisions and the product's relative novelty on enterprise review sites may be factors.

Community / social proof (Reddit) — summarized sentiments (positive and negative)

Representative community sentiment from forum posts includes both positive adoption reports and reports of friction. Examples below summarize common themes observed in Reddit threads:

Positive / adoption comments (summarized):

Some users reported migrating from Cloudflare Tunnels/Access and found Pangolin straightforward to deploy for homelab use cases, commenting that it met their needs for exposing private resources.
Other users described Pangolin as a tunneled mesh reverse proxy with identity and access control features and a dashboard UI, and noted integrations with common tooling (e.g., proxying with Traefik, third-party plugins).

Neutral-to-positive (functional descriptions):

Users have described the product as combining reverse proxy functionality with SSO and a dashboard for administration; some referenced available plugins such as GeoBlock and Crowdsec.

Negative / friction & issues (summarized):

Reports of plaintext secrets appearing in some configuration files and concerns about secret handling and permissions.
Connectivity and reachability problems in specific VPS or site connector setups.
Error reports for specific features (for example, SSH access errors such as resource not found) and uncertainty about debugging.

Why customers choose Pangolin (inferred from discussions)

Drivers include:

Preference for a self-hosted alternative to Cloudflare Tunnels/Access
An integrated approach combining reverse proxying, identity-aware access, and WireGuard-based tunnels
Ease of exposing home or private services without opening inbound ports in some common homelab/SB setups

Vendor case studies

No formal vendor-published case studies with quantified ROI were located in the accessible sources during this research.

Third-party / press "case-like" signals

Critical note: community metrics such as repository stars measure interest and adoption at the community level and are not direct evidence of standardized enterprise deployments or ROI.

04Best fit

Company sizes (practical ranges)

Homelab / prosumers / small teams: single users up to a few dozen, with tolerance for self-host operational work
SMB / mid-market technical teams: tens to a few hundred employees with DevOps/SRE capability and a preference for open-source

Industries

Based on vendor positioning and community usage patterns: IT/OT, IoT, engineering-heavy organizations, and teams that require secure access to internal services.

Roles/personas

Decision makers: Head of IT, Security Engineering lead, Platform Engineering, SMB CTO
End users: Developers, IT administrators, contractors requiring scoped access to internal tools

Qualification criteria (great fit)

Requires resource-level access controls instead of full network VPNs
Has capacity to operate a VPS and site connectors
Values open-source and the option to self-host

05The pitch

What the product does (objective core value proposition)

Pangolin (official product site) is an open-source, identity-aware remote access platform built on WireGuard that combines:

Tunneled reverse proxy (browser-based access to web apps)
Zero Trust "VPN-style" private access (client-based access to SSH/RDP/databases/subnets)

The core objective is to provide least-privileged access to specific resources (apps/services/routes) rather than full network access typical of legacy VPNs, and to enable teams to expose private resources without opening inbound ports or requiring public IPs (via outbound connectors and NAT traversal).

Target market & positioning

Vendor materials describe Pangolin as a consolidated remote access solution positioned as an alternative to legacy VPNs, targeting environments such as:

IT/OT and engineering contexts
IoT / edge deployments
Hybrid networks (on‑prem + cloud + remote sites)

Community adoption appears notable among self-hosters and homelab operators seeking a self-hosted alternative to Cloudflare Tunnels/Access and some commercial ZTNA products.

Get a comprehensive analysis of Pangolin including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →