Realtime broadcast from database
Trigger realtime broadcasts directly from database operations. This feature is in public beta status and fully available on self-hosted deployments.
realtime
19 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
Realtime Postgres changes
Receive your database changes through WebSockets in real-time. This feature is generally available and fully available on self-hosted deployments.
Realtime broadcast for WebSocket messaging
Send messages between connected users through WebSockets. This feature is generally available and fully available on self-hosted deployments.
Realtime presence for shared state synchronization
Synchronize shared state across your users, including online status and typing indicators. This feature is generally available and fully available on self-hosted deployments.
Realtime broadcast authorization
Control who can send and receive broadcast messages through realtime. This feature is in public beta status and fully available on self-hosted deployments.
Realtime presence authorization
Control who can see presence information through realtime. This feature is in public beta status and fully available on self-hosted deployments.
Public Realtime connections limited to 24 hours
Public Realtime connections are limited to 24 hours unless the connection is upgraded with user-level authentication through Supabase Auth or a supported third-party auth provider. This is a known limitation when using the new publishable and secret keys.
Realtime errors troubleshooting table
Symptom: Realtime TIMED_OUT; TooManyChannels; silent disconnect; missed database changes; broadcast-from-DB warning; heartbeats. Layer: Realtime → realtime_logs. Troubleshooting guides: TIMED_OUT; TooManyChannels; Silent disconnects; Broadcast warning; Heartbeats; Logger.
Realtime logging disabled by default
Realtime doesn't log new WebSocket connections or Channel joins by default. Enable connection logging per client by including an info log_level parameter when instantiating the Supabase client.
Enable Realtime connection logging in JavaScript client
To enable Realtime connection logging in the JavaScript client, instantiate the Supabase client with: const options = { realtime: { params: { log_level: 'info' } } }; const supabase = createClient('https://xyzcompany.supabase.co', 'sb_publishable_...', options)
Realtime API Gateway report charts and metrics
The Realtime API Gateway report includes: Total Requests (HTTP requests to Realtime endpoints, shows API usage alongside WebSocket activity including top routes), Response Errors (HTTP requests to Realtime endpoints, shows API usage alongside WebSocket activity including top routes), Response Speed (performance of Realtime API endpoints, shows infrastructure optimization opportunities including top routes).
Realtime report charts and metrics
The Realtime report includes: Connected Clients (active WebSocket connections over time, shows concurrent user activity and connection stability), Broadcast Events (broadcast events over time, shows real-time feature usage patterns), Presence Events (presence events over time, shows real-time feature usage patterns), Postgres Changes Events (Postgres Changes events over time, shows real-time feature usage patterns), Rate of Channel Joins (frequency of new channel subscriptions, shows user engagement with real-time features), Message Payload Size (median size of message payloads sent, shows payload size being transmitted), Broadcast From Database Replication Lag (median latency between database commit and broadcast when using broadcast from database, shows latency to Broadcast from the database), Read/Write Private Channel Subscription RLS Execution Time (median time to authorize private channels, shows realtime.messages RLS policies performance), Total Requests (HTTP requests to Realtime endpoints, shows API usage alongside WebSocket activity), Response Speed (performance of Realtime API endpoints, shows infrastructure optimization opportunities).
Realtime egress definition and example
Realtime egress is data pushed to clients via Supabase Realtime for subscribed events. Example: when a user views a product page in an online shop and their client subscribes to real-time inventory updates, as stock levels change, Supabase Realtime pushes updates to all subscribed clients, contributing to Realtime Egress.
Database changes message count calculation
Each database change counts as one message per client that listens to the event. For example, if a database change occurs and 5 clients listen to that database event, it counts as 5 messages.
Broadcast message count calculation
Each broadcast message counts as one message sent plus one message per subscribed client that receives it. For example, if you broadcast a message and 4 clients listen to it, it counts as 5 messages—1 sent and 4 received.
Realtime security guides index
Supabase provides a security guide for Realtime covering authorization.
Re-enable database publications after restore
After restoring a database, if replication for Supabase Realtime was used in the old database, you must re-enable publication on the tables that need it through the Database > Publications section of the Dashboard.
Realtime connections quotas by plan
Free: 200 peak connections. Pro: 500 peak connections. Team: 500 peak connections. Enterprise: custom quota.
Performance implications of realtime subscriptions at scale
Realtime connections are measured as peak concurrent connections and have per-plan quotas. Exceeding the quota incurs charges of $10 per 1,000 peak connections, indicating that organizations must monitor peak connection usage for cost management at scale.