# Supabase — Realtime or Pipelines? How to choose the right tool

- Company: Supabase (supabase.com)
- Announced: 2026-05-05
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://supabase.com/blog/realtime-or-pipelines-how-to-choose-the-right-tool
- Record: https://forck.live/items/21288-realtime-or-pipelines-how-to-choose-the-right-tool
- Subject: Supabase

Both Supabase Realtime and Supabase Pipelines read changes from your Postgres database. They both use logical replication under the hood. They even look similar when you squint. But they solve very different problems, and choosing the wrong one will frustrate you. This post explains what each product does, how they differ, and when you should pick one over the other. Two tools, two jobs # Here is the simplest way to think about it: Realtime sends database changes to your users' browsers and apps, right now, as they happen. It is built for live experiences. Pipelines sends database changes in near real time to supported analytical destinations. It is built for reliable data movement. Realtime answers the question: "How do I show my users what just happened?" Pipelines answers the question: "How do I get my production data into my analytics warehouse?" If you mix these up, you will run into problems. We see it happen regularly, and the rest of this post will help you avoid that. What Realtime does # Realtime is three features in one product: Broadcast. Send messages between connected clients in real time. No database required. …

---

Record: https://forck.live/items/21288-realtime-or-pipelines-how-to-choose-the-right-tool
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md