From 67856f8f6a81860a2d0fb5d37643bbb90c3695b6 Mon Sep 17 00:00:00 2001 From: braginini Date: Tue, 10 Feb 2026 22:31:23 +0100 Subject: [PATCH] Add commercial license mention --- src/pages/selfhosted/scaling-your-self-hosted-deployment.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/pages/selfhosted/scaling-your-self-hosted-deployment.mdx b/src/pages/selfhosted/scaling-your-self-hosted-deployment.mdx index 66d1a2c4..1511cd78 100644 --- a/src/pages/selfhosted/scaling-your-self-hosted-deployment.mdx +++ b/src/pages/selfhosted/scaling-your-self-hosted-deployment.mdx @@ -356,6 +356,8 @@ sudo netbird service reconfigure --service-env NB_FORCE_RELAY=false In most deployments, the embedded Signal server works well and does not need to be extracted. Consider running an external Signal server if you want to separate it from the Management server for organizational or infrastructure reasons. +Unlike relay servers, the Signal server cannot be replicated as it maintains in-memory connection state. If you need high-availability active-active mode for both Management and Signal, this is available through an [enterprise commercial license](https://netbird.io/pricing#on-prem). + Changing the Signal server URL requires all clients to restart. After updating the configuration, each client must run `netbird down` followed by `netbird up` to reconnect to the new Signal server. This limitation will be addressed in a future client release.