pangolin_mirror/docs-v2
1
0
Fork 0
mirror of https://github.com/fosrl/docs-v2.git synced 2026-02-07 21:46:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rename to nodes

Browse Source
This commit is contained in:
Owen
2025-08-22 09:48:36 -07:00
parent 9122f1d707
commit 45022e2668
12 changed files with 59 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
about/how-pangolin-works.mdx
View File

@@ -3,7 +3,7 @@ title: "How Pangolin Works"
description: "Learn about Pangolin's architecture and how its components work together to provide secure application access"
---
Pangolin provides secure, application-specific ingress to your applications through a network of points of presence. Users connect to the closest point of presence, which authenticates them and routes their requests through secure tunnels to your applications.
Pangolin provides secure, application-specific ingress to your applications through a network of nodes. Users connect to the closest node, which authenticates them and routes their requests through secure tunnels to your applications.
<Frame>
<img src="/images/diagram.svg" width="400" centered/>
@@ -12,12 +12,12 @@ Pangolin provides secure, application-specific ingress to your applications thro
## How It Works
<Steps>
<Step title="User enters through point of presence">
DNS automatically routes users to the closest available regional point of presence (PoP). A PoP is always available because the control plane fails over between PoPs.
<Step title="User enters through node">
DNS automatically routes users to the closest available regional node. A node is always available because the control plane fails over between nodes.
</Step>
<Step title="Authentication and authorization">
The point of presence verifies the user's identity, checks access permissions, and applies context aware rules such as IP and path based filters, geoblocking, and rate limiting.
The node verifies the user's identity, checks access permissions, and applies context aware rules such as IP and path based filters, geoblocking, and rate limiting.
</Step>
<Step title="Secure tunnel routing">
@@ -30,26 +30,26 @@ Pangolin provides secure, application-specific ingress to your applications thro
</Steps>
<Info>
Points of presence provide a mesh of high availability - if one location goes down, traffic automatically routes to the next closest location.
nodes provide a mesh of high availability - if one location goes down, traffic automatically routes to the next closest location.
</Info>
## Deployment Options
<CardGroup cols={2}>
<Card title="Pangolin Cloud" icon="cloud" href="https://pangolin.fossorial.io/auth/signup">
Large network of points of presence with automatic failover and routing to your backend services.
Large network of nodes with automatic failover and routing to your backend services.
</Card>
<Card title="Managed" icon="circle-nodes" href="/manage/managed">
Host your own multiple points of presence with cloud coordination and automatic failover. Data always transits your servers.
Host your own multiple nodes with cloud coordination and automatic failover. Data always transits your servers.
</Card>
<Card title="Self-Hosted" icon="server" href="/self-host/quick-install">
Fully self-hosted, self-contained Pangolin server acting as a single point of presence.
Fully self-hosted, self-contained Pangolin server acting as a single node.
</Card>
<Card title="Learn More" icon="book" href="/manage/points-of-presence">
Detailed information about points of presence and high availability options.
Detailed information about nodes and high availability options.
</Card>
</CardGroup>
@@ -61,7 +61,7 @@ Points of presence provide a mesh of high availability - if one location goes do
</Card>
<Card title="Ingress Mesh" icon="globe">
Users always connect to the closest available point of presence.
Users always connect to the closest available node.
</Card>
<Card title="Zero-Trust Security" icon="shield">
@@ -69,6 +69,6 @@ Points of presence provide a mesh of high availability - if one location goes do
</Card>
<Card title="High Availability" icon="check-double">
Multiple points of presence, failover, and load balancing between tunnels ensures there is always a way for users to access your applications.
Multiple nodes, failover, and load balancing between tunnels ensures there is always a way for users to access your applications.
</Card>
</CardGroup>

10
about/pangolin-vs-traditional-reverse-proxy.mdx
View File

@@ -3,7 +3,7 @@ title: "Pangolin vs. Reverse Proxy"
description: "Learn how Pangolin's distributed architecture eliminates single points of failure and provides authenticated access to your applications"
---
Pangolin builds upon traditional reverse proxy principles but adds distributed architecture, tunneling, and identity-aware access control. While traditional reverse proxies are typically single-server solutions, Pangolin operates as a distributed network of points of presence that provide highly-available access to your applications.
Pangolin builds upon traditional reverse proxy principles but adds distributed architecture, tunneling, and identity-aware access control. While traditional reverse proxies are typically single-server solutions, Pangolin operates as a distributed network of nodes that provide highly-available access to your applications.
## Traditional Reverse Proxy Limitations
@@ -33,11 +33,11 @@ Pangolin provides high availability at two critical layers: ingress points and b
<Steps>
<Step title="Ingress Routing">
Request is routed to the closest available point of presence. If one goes down, there is always another point available.
Request is routed to the closest available node. If one goes down, there is always another point available.
</Step>
<Step title="Authentication">
User identity is verified at the point of presence before getting routed to your backend.
User identity is verified at the node before getting routed to your backend.
</Step>
<Step title="Tunnel Selection">
@@ -54,7 +54,7 @@ Pangolin provides high availability at two critical layers: ingress points and b
</Steps>
<Info>
This dual-layer approach ensures your applications remain accessible even if individual points of presence or tunnel connections fail.
This dual-layer approach ensures your applications remain accessible even if individual nodes or tunnel connections fail.
</Info>
## Key Differences
@@ -110,5 +110,5 @@ Unlike traditional reverse proxies, Pangolin authenticates every single request,
| **Scalability** | Manual scaling | Automatic regional distribution |
<Card title="Try Pangolin Cloud" icon="rocket" href="https://pangolin.fossorial.io/auth/signup">
Get distributed, authenticated access to your applications with Pangolin's regional network of points of presence.
Get distributed, authenticated access to your applications with Pangolin's regional network of nodes.
</Card>

6
about/pangolin-vs-vpn.mdx
View File

@@ -65,7 +65,7 @@ Pangolin provides secure, application-specific ingress and routing without the l
</Card>
<Card title="Highly Available Mesh" icon="circle-nodes" href="/manage/points-of-presence">
Multiple points of presence ensure high availability.
Multiple nodes ensure high availability.
</Card>
</CardGroup>
@@ -78,7 +78,7 @@ Multiple points of presence ensure high availability.
| **Network Requirements** | Public IP, open ports | No public IP needed |
| **Access Control** | Network-level | Zero-trust, granular |
| **Authentication** | Basic credentials | Multi-factor, SSO, OIDC |
| **Infrastructure** | Single server | Distributed points of presence |
| **Infrastructure** | Single server | Distributed nodes |
| **Security Model** | Network-based trust | Identity-based trust |
<Card title="Try Pangolin Cloud" icon="rocket" href="https://pangolin.fossorial.io/auth/signup">
@@ -87,6 +87,6 @@ Multiple points of presence ensure high availability.
# Pangolin vs. Mesh VPN (e.g., Tailscale, Netbird)
Pangolin and mesh VPNs like Tailscale or Netbird both provide secure remote access, but they differ in their approach and functionality. Mesh VPNs focus on creating peer-to-peer connections between devices for full network access, while Pangolin is designed to expose specific applications or services securely through points of presence, with no need for client-side software on user devices.
Pangolin and mesh VPNs like Tailscale or Netbird both provide secure remote access, but they differ in their approach and functionality. Mesh VPNs focus on creating peer-to-peer connections between devices for full network access, while Pangolin is designed to expose specific applications or services securely through nodes, with no need for client-side software on user devices.
Pangolin is a better choice for application-specific access with zero-trust security and no client-side software requirements. Mesh VPNs like Tailscale or Netbird are more suitable for full network access and peer-to-peer connectivity. For environments prioritizing granular access control and simplicity, Pangolin offers a more focused and secure solution.