From 8476910754a615e6d89685cccfcb98dcd599d397 Mon Sep 17 00:00:00 2001
From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com>
Date: Wed, 23 Sep 2026 18:20:51 +0200
Subject: [PATCH] docs: say why the installer deployment runs no Redis or NATS

---
 .../maintenance/scaling/high-availability-from-installer.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx b/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
index 41fd85f4..e7fc949c 100644
--- a/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
+++ b/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
@@ -25,7 +25,7 @@ After the installer, one host runs everything. After this guide:
 | Login data (embedded identity provider) | An SQLite file on node 1 | The same PostgreSQL endpoint |
 | Signal | Built into the server | A Signal pool behind the load balancer, at the same URL |
 | Relay | Built into the server | Separate relay instances, one address each |
-| Redis and NATS | Not used | Shared by every node |
+| Redis and NATS | None: one server keeps its cache and messaging in memory | Shared by every node, so they share that state |
 
 The example uses these names. Replace them with your own throughout: