Supabase Pipelines Flutter Guide: Realtime Compared
Choosing between Supabase Pipelines and Realtime in your Flutter app? Get the direct verdict, a head-to-head comparison of latency, delivery, and cost, and clear rules for when each one wins.
Choosing between Supabase Pipelines and Realtime for your Flutter app? The short answer: use Realtime when your app's UI must react to database changes in milliseconds, and use Pipelines when you need to move data into a warehouse like BigQuery for analytics. They are not rivals — they solve different problems, and growing apps usually end up running both. If you haven't wired up Supabase in Flutter yet, the complete Flutter and Supabase guide gets you to a running project first. *Last updated: 2026-10-10* The choice, stated plainly You are deciding how change flows out of your Postgres database. One path pushes changes to *clients* — phones watching a screen. The other path replicates changes to *systems* — a warehouse, a data lake, an analytics engine. Supabase Realtime is the first path: a websocket server that broadcasts row changes to subscribed Flutter clients in well under 100ms. Supabase Pipelines is the second: a managed CDC (change data capture) service that streams your tables into destinations like BigQuery, batched and durable. The confusion is understandable — both "react to database changes." The difference that matters: Realtime answers "what just happened, right now, on this screen?" Pipelines answers "what happened across everything, so we can analyze it later?" A quick heuristic before we go deeper: if you removed the feature, would a *person* notice within seconds, or would a *dashboard* notice next quarter? Person-notices-fast means Realtime. Dashboard-notices-later means Pipelines. If you answered "both," keep reading — the verdict section is written for exactly that app. Supabase Realtime: strengths and weaknesses Realtime keeps a persistent websocket between your Flutter app and Supabase. Subscribe to a table, and inserts, updates, and…