mirror of
https://github.com/fosrl/docs-v2.git
synced 2026-02-08 05:56:45 +00:00
Renaming to remote-nodes
This commit is contained in:
@@ -1,72 +0,0 @@
|
||||
---
|
||||
title: "Managed Self-Hosted"
|
||||
description: "More reliable and low-maintenance self-hosted Pangolin server with extra bells and whistles"
|
||||
---
|
||||
|
||||
**Managed Self-Hosted Pangolin** is a deployment option designed for people who want simplicity and extra reliability while still keeping their data private and self-hosted.
|
||||
|
||||
With this option, you still run your own Pangolin node — your tunnels, SSL termination, and traffic all stay on your server. The difference is that management and monitoring are handled through our cloud dashboard, which unlocks a number of significant benefits.
|
||||
|
||||
<Tip>
|
||||
You can deploy a managed Pangolin node in seconds [using the installer](/self-host/quick-install-managed).
|
||||
</Tip>
|
||||
|
||||
## How It Works
|
||||
|
||||
The managed self-hosted approach gives you the best of both worlds:
|
||||
|
||||
- **You Host the Node**: You maintain complete control over your infrastructure and where your data flows. Your tunnels, SSL termination, and all traffic processing happen on your servers.
|
||||
- **We Handle Coordination**: Pangolin Cloud manages the control plane, DNS, certificate management, database, and backups through our cloud dashboard.
|
||||
- **Seamless Failover**: Deploy multiple nodes with automatic failover between them. If your nodes become unavailable, traffic can optionally fail over to our cloud infrastructure until you restore service.
|
||||
|
||||
<Frame>
|
||||
<img src="/images/ha.svg" width="400" centered/>
|
||||
</Frame>
|
||||
|
||||
## Why Choose Managed Self-Hosted?
|
||||
|
||||
**Data Control & Privacy**: All your traffic flows through your own servers, giving you complete control over data transit, costs, and ensuring compliance with your security policies.
|
||||
|
||||
**Simplified High Availability**: Get enterprise-grade reliability without the complexity of managing distributed systems, load balancers, and monitoring infrastructure yourself.
|
||||
|
||||
**Reduced Operational Burden**: Focus on your core business while we handle the operational complexity of keeping your tunneling infrastructure running smoothly.
|
||||
|
||||
<Note>
|
||||
For detailed information about how nodes work and their advantages, see our [Nodes](/manage/nodes) documentation.
|
||||
</Note>
|
||||
|
||||
## Key Benefits
|
||||
|
||||
### Simpler Operations
|
||||
No need to run your own mail server or set up complex alerting. You'll get health checks and downtime alerts out of the box, making it much easier to monitor your infrastructure without additional complexity.
|
||||
|
||||
### Automatic Updates
|
||||
The cloud dashboard evolves quickly, so you get new features and bug fixes without having to manually pull new containers every time. Your self-hosted node stays current automatically.
|
||||
|
||||
### Less Maintenance
|
||||
No database migrations, backups, or extra infrastructure to manage. We handle that in the cloud, so you can focus on what matters most to your business.
|
||||
|
||||
### Cloud Failover
|
||||
If your node goes down, your tunnels can temporarily fail over to our cloud points of presence until you bring it back online. This ensures continuous availability even during maintenance windows.
|
||||
|
||||
### High Availability (PoPs)
|
||||
You can also attach multiple nodes to your account for redundancy and better performance. Deploy nodes across different regions or providers for maximum reliability.
|
||||
|
||||
### Future Enhancements
|
||||
We're planning to add more analytics, alerting, and management tools to make your deployment even more robust. You'll automatically benefit from these improvements as they're released.
|
||||
|
||||
## Getting Started
|
||||
|
||||
<Tip>
|
||||
You can deploy a managed Pangolin node in seconds [using the installer](/self-host/quick-install-managed).
|
||||
</Tip>
|
||||
|
||||
Ready to convert your existing self-hosted node to managed? Learn how in our [conversion guide](/self-host/convert-managed).
|
||||
|
||||
<Note>
|
||||
For detailed information about how nodes work and their advantages, see our [nodes](/manage/nodes) documentation.
|
||||
</Note>
|
||||
|
||||
<Tip>
|
||||
Managed deployment is ideal for organizations that need high availability and reduced operational overhead while maintaining complete control over their infrastructure and data transit.
|
||||
</Tip>
|
||||
104
manage/nodes.mdx
104
manage/nodes.mdx
@@ -1,104 +0,0 @@
|
||||
---
|
||||
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 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 Nodes?
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Entry Points" icon="door-open">
|
||||
Handle incoming user requests before routing them to your applications.
|
||||
</Card>
|
||||
|
||||
<Card title="Global Coverage" icon="globe">
|
||||
Located regionally to minimize latency for users in different regions.
|
||||
</Card>
|
||||
|
||||
<Card title="High Availability" icon="shield-check">
|
||||
Multiple locations ensure your applications remain accessible even if individual locations fail.
|
||||
</Card>
|
||||
|
||||
<Card title="Authentication" icon="key">
|
||||
Verify user identity and enforce access policies before allowing access.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
<Info>
|
||||
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 Nodes Work
|
||||
|
||||
<Steps>
|
||||
<Step title="Ingress Routing">
|
||||
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 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 node.
|
||||
</Step>
|
||||
|
||||
<Step title="Failover Handling">
|
||||
If the primary tunnel fails, traffic automatically switches to an alternative route.
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
## Advantages of Nodes
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Low Latency" icon="bolt">
|
||||
Users connect to the geographically closest node.
|
||||
</Card>
|
||||
|
||||
<Card title="Optimized Routing" icon="route">
|
||||
Automatic selection of the best available tunnel to route to your backend services.
|
||||
</Card>
|
||||
|
||||
<Card title="Edge Computing" icon="microchip">
|
||||
Provide ingress to thin-clients on private networks via tunnels.
|
||||
</Card>
|
||||
|
||||
<Card title="Health Monitoring" icon="heart-pulse">
|
||||
Each node continuously monitors its health and connectivity to your backend.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Regional Redundancy" icon="check-double">
|
||||
Multiple nodes ensure your applications remain accessible during regional outages.
|
||||
</Card>
|
||||
|
||||
<Card title="Fault Tolerance" icon="shield">
|
||||
No single point of failure - if one location goes down, there is always a way back to your application.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
## Deployment Models
|
||||
|
||||
<CardGroup cols={3}>
|
||||
<Card title="Pangolin Cloud" icon="cloud" href="https://pangolin.fossorial.io/auth/signup">
|
||||
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 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 node.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
<Warning>
|
||||
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>
|
||||
Managed deployment is ideal for organizations that need high availability while maintaining control over their infrastructure and data transit.
|
||||
</Tip>
|
||||
Reference in New Issue
Block a user