Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

feat(pipelines): Adjust blog post naming (#48154)

Riccardo Busetti94f2f5a4a3f5
diff --git a/apps/www/_blog/2026-07-21-supabase-pipelines-public-alpha.mdx b/apps/www/_blog/2026-07-21-supabase-pipelines-public-alpha.mdx
index 3b67988f084..a3dd01b0ea1 100644
--- a/apps/www/_blog/2026-07-21-supabase-pipelines-public-alpha.mdx
+++ b/apps/www/_blog/2026-07-21-supabase-pipelines-public-alpha.mdx
@@ -1,6 +1,6 @@
---
title: 'Supabase Pipelines is now in Public Alpha'
-description: 'Supabase Pipelines is now in public alpha with schema change support, a faster initial copy, and a new destination request form for ClickHouse, Snowflake, and DuckLake.'
+description: 'Supabase Pipelines is now in public alpha with schema change support, a faster initial sync, and a new destination request form for ClickHouse, Snowflake, and DuckLake.'
author: riccardo_busetti
imgSocial: supabase-pipelines-public-alpha/og.png
imgThumb: supabase-pipelines-public-alpha/thumb.png
@@ -14,7 +14,7 @@ date: '2026-07-21'
toc_depth: 2
---
-Today we're moving **Supabase Pipelines** into public alpha. The biggest addition is schema change support: Pipelines can now detect supported schema changes in your source tables and apply them to the destination automatically. This release also brings a faster initial copy and a new destination request form for ClickHouse, Snowflake, and DuckLake.
+Today we're moving **Supabase Pipelines** into public alpha. The biggest addition is schema change support: Pipelines can now detect supported schema changes in your source tables and apply them to the destination automatically. This release also brings a faster initial sync and a new destination request form for ClickHouse, Snowflake, and DuckLake.
Supabase Pipelines replicates your Supabase Postgres data to external analytical systems in near real time. It is powered by [Supabase ETL](https://github.com/supabase/etl), our open source change-data-capture pipeline written in Rust. Supabase ETL reads changes from Postgres through logical replication, copies existing table data, streams inserts, updates, deletes, and truncates, and writes them to your destination.
@@ -30,8 +30,8 @@ Supabase Pipelines gives you a reliable way to move production data into systems
You get:
-- A complete initial copy of your selected tables.
-- Near real-time replication after the initial copy finishes.
+- A complete initial sync of your selected tables.
+- Near real-time replication after the initial sync finishes.
- At-least-once delivery for database changes.
- Destination-side tables that stay aligned with your source schema.
- A managed Dashboard experience for creating, monitoring, and controlling pipelines.
@@ -45,7 +45,7 @@ Since introducing Supabase Pipelines, we've been focused on making it faster, mo
We improved performance across the board, reduced memory usage, and lowered replication latency. This work is ongoing. Supabase Pipelines is still in alpha, and we're continuing to tune throughput, batching, and backpressure as we learn from more workloads.
-We also improved the initial sync. It can now be parallelized across tables and within a table, which lets pipelines load existing data much faster before switching into streaming mode.
+We also improved the initial sync. It can now be parallelized across tables and within a table, which lets pipelines load existing data much faster before switching to ongoing replication.
The biggest new feature is **schema change support**.
@@ -75,7 +75,7 @@ When you create a pipeline:
1. You choose the tables you want to replicate.
2. Supabase Pipelines creates an initial sync of the selected tables.
3. The initial sync runs with parallel workers based on the configured parallelism level.
-4. After the sync completes, the pipeline switches to streaming mode.
+4. After the sync completes, the pipeline switches to ongoing replication.
5. New changes are read from the replication slot, batched, and written to the destination.
6. Supported schema changes are detected and applied to the destination schema.
@@ -107,11 +107,11 @@ We're always looking to add more destinations. If there is another warehouse, la
Supabase Pipelines uses a pipeline-based and usage-based pricing model:
-- **$0.053 per hour per active pipeline**
-- **$0.60 per GB** for the initial table copy
-- **$3 per GB** for replicated data after the initial copy
+- **$0.053 per hour** per configured pipeline
+- **$0.60 per GB** of initial sync data
+- **$3 per GB** of ongoing replication data
-A pipeline becomes billable as soon as it is created and is charged hourly, including while replication is paused or inactive. Initial sync usage covers the first load of existing data, while ongoing replication usage covers changes processed after that initial sync. Pricing may change during the public alpha, and we will provide advance notice before any updates take effect.
+A pipeline becomes billable as soon as it is created and is charged hourly, including while replication is paused or inactive. Initial sync data covers the first load of existing data, while ongoing replication data covers changes processed after that initial sync. Pricing may change during the public alpha, and we will provide advance notice before any updates take effect.
## Things to know during public alpha