From ff6170673ef10e3e1adfa5aca80a51758bc76201 Mon Sep 17 00:00:00 2001 From: Bruno Mercier Costa <94469565+emrcbrn@users.noreply.github.com> Date: Thu, 22 Oct 2026 19:29:30 +0200 Subject: [PATCH] Clarify that lazy connections don't require self-hosting (#1061) --- src/pages/manage/peers/lazy-connection.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/manage/peers/lazy-connection.mdx b/src/pages/manage/peers/lazy-connection.mdx index faebfd4a..a65aab74 100644 --- a/src/pages/manage/peers/lazy-connection.mdx +++ b/src/pages/manage/peers/lazy-connection.mdx @@ -5,7 +5,7 @@ import {Note} from "@/components/mdx"; Lazy connections reduce resource use in large NetBird networks by opening peer connections only when traffic needs them, rather than maintaining every possible full-mesh connection continuously. - Lazy connections require NetBird v0.50.1 or later on the client, the peers it communicates with, and self-hosted Management and Signal servers. + Lazy connections require NetBird v0.50.1 or later on the client and on the peers it communicates with. If you self-host NetBird, your Management and Signal servers must also run v0.50.1 or later. NetBird Cloud already meets this requirement. ## How Lazy Connections Work