Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

Clarify Supavisor SSL Enforcement (#51941)

Kostas Botsas6ea109c69c7c
diff --git a/apps/docs/content/guides/platform/ssl-enforcement.mdx b/apps/docs/content/guides/platform/ssl-enforcement.mdx
index 773bb123174..3befc749c69 100644
--- a/apps/docs/content/guides/platform/ssl-enforcement.mdx
+++ b/apps/docs/content/guides/platform/ssl-enforcement.mdx
@@ -7,6 +7,8 @@ Your Supabase project supports connecting to the Postgres DB without SSL enabled
Disabling SSL enforcement only applies to connections to Postgres, Supavisor (shared Connection Pooler) and PgBouncer (dedicated Connection Pooler); all HTTP APIs offered by Supabase (e.g., PostgREST, Storage, Auth) automatically enforce SSL on all incoming connections (see [TLS for project APIs](/docs/guides/security/tls)).
+For Supavisor (shared Connection Pooler) this setting governs both legs of the connection: client to pooler, and pooler to Postgres.
+
<Admonition type="caution">
Applying or updating SSL enforcement triggers a fast database reboot. On small projects this usually completes in a few seconds, but larger databases may see a longer interruption.