pangolin_mirror/docs-v2
1
0
Fork 0
mirror of https://github.com/fosrl/docs-v2.git synced 2026-02-23 13:26:47 +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

14
manage/managed.mdx
View File

@@ -1,35 +1,35 @@
---
title: "Self host a Managed PoP"
title: "Self-host Managed Nodes"
description: "Learn about Pangolin's managed deployment mode"
---
In this deployment modality you can host your own points of presence with cloud coordination and automatic failover. Data always transits your servers and the cloud handles orchestration between all of your PoPs.
In this deployment modality you can host your own nodes with cloud coordination and automatic failover. Data always transits your servers and the cloud handles orchestration between all of your nodes.
Its essentially just the normal self hosted pangolin setup, but with added benefits of cloud integration and coordinated failover.
<Tip>
You can deploy a managed Pangolin PoP in seconds [using the installer](../self-host/quick-install-managed).
You can deploy a managed Pangolin node in seconds [using the installer](../self-host/quick-install-managed).
</Tip>
### How It Works
- **You Host the PoP**: Manage the infrastructure for your points of presence, which connect your Newt tunnels.
- **You Host the node**: Manage the infrastructure for your nodes, which connect your Newt tunnels.
- **We Handle the Rest**: Pangolin Cloud manages the control plane, DNS, certificate management, database, and backups.
- **Failover Made Simple**: Host multiple PoPs with automatic failover between them. Optionally, if your PoPs are unavailable, traffic automatically fails over to our cloud PoPs.
- **Failover Made Simple**: Host multiple nodes with automatic failover between them. Optionally, if your nodes are unavailable, traffic automatically fails over to our cloud nodes.
<Frame>
<img src="/images/ha.svg" width="400" centered/>
</Frame>
<Note>
For detailed information about how points of presence work and their advantages, see our [Points of Presence](/manage/points-of-presence) documentation.
For detailed information about how nodes work and their advantages, see our [Nodes](/manage/nodes) documentation.
</Note>
### Benefits
- **Data Control**: Traffic flows through your servers, giving you control over data transit costs, privacy, and works with your security policies.
- **High Availability**: Eliminates the complexity of managing high availability while still owning your own infrastructure.
- **Less Management Overhead**: While we update the cloud with new features you don't need to touch your PoPs unless you want to.
- **Less Management Overhead**: While we update the cloud with new features you don't need to touch your nodes unless you want to.
<Tip>
Managed deployment is ideal for organizations that need high availability while maintaining control over their infrastructure and data transit.

34
manage/points-of-presence.mdx → manage/nodes.mdx
View File

@@ -1,11 +1,11 @@
---
title: "HA & Points of Presence"
description: "Learn about Pangolin's network of points of presence and how they provide highly available, low-latency access to your applications"
title: "Highly Available Nodes"
description: "Learn about Pangolin's network of nodes and how they provide highly available, low-latency access to your applications"
---
Pangolin's points of presence (PoPs) are strategically located servers around the world that serve as entry points for user traffic to your applications. They form the foundation of Pangolin's distributed architecture, providing high availability and optimal performance.
Pangolin's nodes are an ability to put strategically located servers around the world that serve as entry points for user traffic to your applications. They form the foundation of Pangolin's distributed architecture, providing high availability and optimal performance.
## What Are Points of Presence?
## What Are Nodes?
<CardGroup cols={2}>
<Card title="Entry Points" icon="door-open">
@@ -26,22 +26,22 @@ Pangolin's points of presence (PoPs) are strategically located servers around th
</CardGroup>
<Info>
Think of points of presence as the "front doors" to your applications - users connect to the closest one, and it securely routes their requests to your backend services.
Think of different nodes as the "front doors" to your applications - users connect to the closest one, and it securely routes their requests to your backend services.
</Info>
## How Points of Presence Work
## How Nodes Work
<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 node 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">
Pangolin selects the optimal tunnel route to your backend service. Site tunnel clients (Newt) connect to the optimal point of presence.
Pangolin selects the optimal tunnel route to your backend service. Site tunnel clients (Newt) connect to the optimal node.
</Step>
<Step title="Failover Handling">
@@ -49,11 +49,11 @@ Think of points of presence as the "front doors" to your applications - users co
</Step>
</Steps>
## Advantages of Points of Presence
## Advantages of Nodes
<CardGroup cols={2}>
<Card title="Low Latency" icon="bolt">
Users connect to the geographically closest point of presence.
Users connect to the geographically closest node.
</Card>
<Card title="Optimized Routing" icon="route">
@@ -65,13 +65,13 @@ Think of points of presence as the "front doors" to your applications - users co
</Card>
<Card title="Health Monitoring" icon="heart-pulse">
Each point of presence continuously monitors its health and connectivity to your backend.
Each node continuously monitors its health and connectivity to your backend.
</Card>
</CardGroup>
<CardGroup cols={2}>
<Card title="Regional Redundancy" icon="check-double">
Multiple points of presence ensure your applications remain accessible during regional outages.
Multiple nodes ensure your applications remain accessible during regional outages.
</Card>
<Card title="Fault Tolerance" icon="shield">
@@ -83,20 +83,20 @@ Think of points of presence as the "front doors" to your applications - users co
<CardGroup cols={3}>
<Card title="Pangolin Cloud" icon="cloud" href="https://pangolin.fossorial.io/auth/signup">
Network of points of presence with automatic failover and routing to your backend services.
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>
</CardGroup>
<Warning>
Self-hosted Pangolin provides only a single point of presence and is not highly available. Consider Pangolin Cloud or managed deployment for production environments requiring high availability.
Self-hosted Pangolin provides only a single node and is not highly available. Consider Pangolin Cloud or managed deployment for production environments requiring high availability.
</Warning>
<Tip>