The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
docs(realtime): broadcast replay retention limits - REAL-874 (#47270)
Leandro Pereira32764ec4834b
diff --git a/apps/docs/content/guides/realtime/broadcast.mdx b/apps/docs/content/guides/realtime/broadcast.mdxindex 457326b1dd3..20a23ed37ba 100644--- a/apps/docs/content/guides/realtime/broadcast.mdx+++ b/apps/docs/content/guides/realtime/broadcast.mdx@@ -1042,6 +1042,12 @@ You can configure replay with the following options:- **`since`** (Required): The epoch timestamp in milliseconds (for example, `1697472000000`), specifying the earliest point from which messages should be retrieved.- **`limit`** (Optional): The number of messages to return. This must be a positive integer, with a maximum value of 25.+<Admonition type="note">++Messages are stored in daily partitions, and partitions older than 72 hours are dropped. Because whole days are removed at once, a message stays available for at least 72 hours and at most 4 days, depending on the time of day it was sent. Setting `since` further back than the retained window does not recover deleted messages. See [Realtime Limits](/docs/guides/realtime/limits) for details.++</Admonition>+<Tabsscrollablesize="small"diff --git a/apps/docs/content/guides/realtime/limits.mdx b/apps/docs/content/guides/realtime/limits.mdxindex 5c45b111e4d..6ac95151ec2 100644--- a/apps/docs/content/guides/realtime/limits.mdx+++ b/apps/docs/content/guides/realtime/limits.mdx@@ -15,17 +15,19 @@ Upgrade your plan to increase your limits. Without a spend cap, or on an Enterpr## Limits by plan-| | Free | Pro | Pro (no spend cap) | Team | Enterprise |-| ----------------------------------------------------------------------------------- | -------- | -------- | ------------------ | -------- | ---------- |-| **Concurrent connections** | 200 | 500 | 10,000 | 10,000 | 10,000+ |-| **Messages per second** | 100 | 500 | 2,500 | 2,500 | 2,500+ |-| **Channel joins per second** | 100 | 500 | 2,500 | 2,500 | 2,500+ |-| **Channels per connection** | 100 | 100 | 100 | 100 | 100+ |-| **Presence keys per object** | 10 | 10 | 10 | 10 | 10+ |-| **Presence messages per second** | 20 | 50 | 1,000 | 1,000 | 1,000+ |-| **Presence calls per client, per 30 seconds** | 5 | 5 | 5 | 5 | 5 |-| **Broadcast payload size** | 256 KB | 3,000 KB | 3,000 KB | 3,000 KB | 3,000+ KB |-| **Postgres change payload size ([**read more**](#postgres-changes-payload-limit))** | 1,024 KB | 1,024 KB | 1,024 KB | 1,024 KB | 1,024+ KB |+| | Free | Pro | Pro (no spend cap) | Team | Enterprise |+| -------------------------------------------------------------------------------------------------- | -------- | -------- | ------------------ | -------- | ---------- |+| **Concurrent connections** | 200 | 500 | 10,000 | 10,000 | 10,000+ |+| **Messages per second** | 100 | 500 | 2,500 | 2,500 | 2,500+ |+| **Channel joins per second** | 100 | 500 | 2,500 | 2,500 | 2,500+ |+| **Channels per connection** | 100 | 100 | 100 | 100 | 100+ |+| **Presence keys per object** | 10 | 10 | 10 | 10 | 10+ |+| **Presence messages per second** | 20 | 50 | 1,000 | 1,000 | 1,000+ |+| **Presence calls per client, per 30 seconds** | 5 | 5 | 5 | 5 | 5 |+| **Broadcast payload size** | 256 KB | 3,000 KB | 3,000 KB | 3,000 KB | 3,000+ KB |+| **Postgres change payload size ([**read more**](#postgres-changes-payload-limit))** | 1,024 KB | 1,024 KB | 1,024 KB | 1,024 KB | 1,024+ KB |+| **Broadcast replay retention ([**read more**](/docs/guides/realtime/broadcast#broadcast-replay))** | 72 hours | 72 hours | 72 hours | 72 hours | 72 hours |+| **Broadcast replay messages per request** | 25 | 25 | 25 | 25 | 25 |Beyond the Free and Pro Plan you can customize your limits by [contacting support](/dashboard/support/new).