supabase/realtime

Broadcast, Presence, and Postgres Changes via WebSockets

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 8th, 2026
Created on September 23rd, 2019
Open Issues & Pull Requests: 71 (+1)
GitHub issues: Enabled
Number of forks: 462
Total Stargazers: 7,630 (+0)
Total Subscribers: 110 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 40.5 hours
Mean response time: 43.3 days
90th percentile: 86.6 days
Tracked items: 91

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 4% of issues opened in the past year have been closed. Three people close 63% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 422 days
Stale 30+ days: 26
Stale 90+ days: 23

Recent activity

Opened in 7 days: 3
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (73)
  • enhancement (9)
  • released (8)
  • documentation (2)
  • p4 (1)
  • question (1)
  • semantic-release (1)

Detailed Description

Supabase Realtime is a WebSocket server that enables broadcast messaging, presence tracking, and Postgres change notifications for connected clients.

The tool solves the problem of delivering real-time updates from a database and between clients without polling. It works by maintaining WebSocket connections and streaming changes from Postgres through a server built with Elixir and the Phoenix Framework. Clients can subscribe to broadcast channels for ephemeral messages, track shared state through presence features, or listen to database changes with row-level security applied. The server does not guarantee message delivery, so applications must be designed with that constraint in mind.

Realtime suits projects that need low-latency synchronization between clients or between a database and clients, such as collaborative applications or live dashboards. It integrates with Postgres directly for change-data-capture, making it particularly valuable for applications already using Postgres as their primary database. The tool is designed to work within the Supabase ecosystem but can be deployed independently.

The codebase is under active development with evolving documentation. The project maintains separate versions with v1 available in archived form while v2 receives ongoing work. Developers can reference architecture documentation covering cluster behavior and broadcast fan-out patterns, detailed environment variable configuration, and observability metrics for monitoring deployments. The team provides local development setup guidance and example workflows for contributors.