mirror of
https://github.com/netbirdio/docs.git
synced 2026-04-15 23:16:36 +00:00
Add more clarifications NetBird cloud vs Self-hosting
This commit is contained in:
@@ -7,6 +7,17 @@ on our servers.
|
||||
Often times, the question arises: what is the difference between the two? This post gives a short overview of the
|
||||
differences between the two versions.
|
||||
|
||||
## Before Choosing to Self-Host NetBird in Production
|
||||
|
||||
When we first created NetBird, our goal was to simplify network administration — freeing admins from the headaches of
|
||||
configuring firewalls, opening ports, managing VPN gateways, handling certificates, and so on. We wanted to provide a
|
||||
tool that lets teams completely close off their network from the outside world, while still enabling devices to seamlessly
|
||||
discover and connect to internal resources just by installing the client apps. However, as is often the case with easy-to-use tools,
|
||||
a lot happens behind the scenes. NetBird relies on a range of interconnected components that work together to ensure secure
|
||||
peer-to-peer connectivity, fallback relayed connections through a network of geographically distributed relay servers,
|
||||
and overall system reliability and availability. It is not an easy task to deploy and maintain such infrastructure in
|
||||
a reliable manner. NetBird is not just one VPN server. You can read more about how NetBird works [here](/about-netbird/how-netbird-works).
|
||||
|
||||
## Installation and Maintenance
|
||||
|
||||
NetBird platform is a combination of [multiple components](/about-netbird/how-netbird-works) that make it possible for
|
||||
|
||||
Reference in New Issue
Block a user