The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
feat(replication): Evaluate new product name (#47066)
Riccardo Busettidf7a0ca3f746
diff --git a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.tsindex 3b07a4cf095..a075a475fe6 100644--- a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts+++ b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts@@ -1179,12 +1179,12 @@ export const database: NavMenuConstant = {items: [{ name: 'Overview', url: '/guides/database/replication' },{- name: 'External replication',- url: '/guides/database/replication/external-replication-setup' as `/${string}`,+ name: 'Pipelines',+ url: '/guides/database/replication/pipelines' as `/${string}`,items: [{name: 'Setting up',- url: '/guides/database/replication/external-replication-setup' as `/${string}`,+ url: '/guides/database/replication/pipelines' as `/${string}`,items: [{name: 'BigQuery',@@ -1194,9 +1194,9 @@ export const database: NavMenuConstant = {},{name: 'Monitoring',- url: '/guides/database/replication/external-replication-monitoring' as `/${string}`,+ url: '/guides/database/replication/pipelines-monitoring' as `/${string}`,},- { name: 'FAQ', url: '/guides/database/replication/external-replication-faq' },+ { name: 'FAQ', url: '/guides/database/replication/pipelines-faq' },],},{diff --git a/apps/docs/content/guides/database/postgres/roles.mdx b/apps/docs/content/guides/database/postgres/roles.mdxindex 3286c786e49..9b46fe8ed3f 100644--- a/apps/docs/content/guides/database/postgres/roles.mdx+++ b/apps/docs/content/guides/database/postgres/roles.mdx@@ -113,7 +113,7 @@ Used by the Auth middleware to connect to the database and run migration. Access### `supabase_etl_admin`-`supabase_etl_admin` is used by [Database replication](/docs/guides/database/replication) through Supabase ETL.+`supabase_etl_admin` is used by Supabase Pipelines for [Database replication](/docs/guides/database/replication).This role:diff --git a/apps/docs/content/guides/database/replication.mdx b/apps/docs/content/guides/database/replication.mdxindex 8ff0b26278f..7ad4408b84e 100644--- a/apps/docs/content/guides/database/replication.mdx+++ b/apps/docs/content/guides/database/replication.mdx@@ -1,7 +1,7 @@---id: 'replication'title: 'Database replication'-description: 'Compare read replicas, external replication (ETL), and manual replication.'+description: 'Compare read replicas, Supabase Pipelines, and manual replication.'subtitle: 'An introduction to database replication and change data capture.'sidebar_label: 'Overview'---@@ -18,7 +18,7 @@ You might use database replication for:## Replication methods-Supabase supports three replication methods. Choose based on whether you need another Supabase Postgres database, a managed pipeline to a destination system, or full control over your own logical replication setup.+Supabase supports three replication methods. Choose based on whether you need another Supabase Postgres database, a managed replication pipeline to a destination system, or full control over your own logical replication setup.### Read replicas@@ -26,21 +26,23 @@ Read replicas are additional Supabase Postgres databases kept in sync with your- [Set up read replicas](/docs/guides/platform/read-replicas)-### External replication (ETL) [#external-replication]+{/* supa-mdx-lint-disable-next-line Rule001HeadingCase */}++### Pipelines<Admonition type="caution" title="Private Alpha">-External replication (ETL) is currently in private alpha. Managed pipelines run through Supabase ETL. Access is limited and features may change.+Supabase Pipelines is currently in private alpha. Private alpha features can be unstable and may introduce breaking changes while we evaluate the product direction, refine the feature set, and incorporate customer feedback.</Admonition>-External replication (ETL) is powered by [Supabase ETL](https://github.com/supabase/etl). It uses Postgres logical replication under the hood and provides a managed Dashboard workflow for replicating data from Supabase Postgres to destination systems. In this context, "external" means outside the source database. Destinations can be Supabase-managed or third-party systems as support expands.+Pipelines is a managed CDC feature for creating replication pipelines from Supabase Postgres to destination systems. It uses Postgres logical replication under the hood with the open-source [Supabase ETL engine](https://github.com/supabase/etl). A destination is where your replicated data is stored; the pipeline is the managed process that continuously streams database changes to that destination.-- [Set up external replication (ETL)](/docs/guides/database/replication/external-replication-setup)+- [Set up Pipelines](/docs/guides/database/replication/pipelines)#### Supported destinations-External replication (ETL) currently supports BigQuery as the managed destination. We are working on new destinations, and this table will be updated as support expands.+Pipelines currently supports BigQuery as the managed destination. We are working on new destinations, and this table will be updated as support expands.| Destination | Insert | Update | Delete | Truncate | Schema change | Description || ------------------------------------------------------ | ------------ | ------------ | ------------ | ------------ | ------------- | ------------------------------------------------------------------- |@@ -48,7 +50,7 @@ External replication (ETL) currently supports BigQuery as the managed destinatio### Manual replication-Manual replication uses the same underlying Postgres logical replication features as external replication (ETL), but you configure and operate the pieces yourself. Use this path when you want to connect tools such as Airbyte, Estuary, Fivetran, Materialize, Stitch, AWS DMS, or another system that supports Postgres logical replication.+Manual replication uses the same underlying Postgres logical replication features as Pipelines, but you configure and operate the pieces yourself. Use this path when you want to connect tools such as Airbyte, Estuary, Fivetran, Materialize, Stitch, AWS DMS, or another system that supports Postgres logical replication.- [Set up manual replication](/docs/guides/database/replication/manual-replication-setup)@@ -78,7 +80,7 @@ When setting up logical replication, three key components are involved:- `publication` - A set of tables on your primary database that will be `published`- `replication slot` - A slot used for replicating the data from a single publication. The slot, when created, will specify the output format of the changes-- `subscription` - A subscription is created from an external system (i.e. another Postgres database) and must specify the name of the `publication`. If you do not specify a replication slot, one is automatically created+- `subscription` - A subscription is created from an external system (that is, another Postgres database) and must specify the name of the `publication`. If you do not specify a replication slot, one is automatically created## Logical replication output format@@ -86,7 +88,7 @@ Logical replication is typically output in two forms, `pgoutput` and `wal2json`.## Logical replication configuration-When using logical replication, Postgres keeps WAL files around for longer than it otherwise needs them. If the files are removed too quickly, then your `replication slot` can become inactive or lost if the database receives a large number of changes in a short time.+When using logical replication, Postgres keeps WAL files around for longer than it otherwise needs them. If the files are removed too soon, then your `replication slot` can become inactive or lost if the database receives a large number of changes in a short time.In order to mitigate this, Postgres has many options and settings that can be [tweaked](/docs/guides/database/custom-postgres-config) to manage the WAL usage effectively. Not all of these settings are user configurable as they can impact the stability of your database. For those that are, these should be considered as advanced configuration and not changed without understanding that they can cause additional disk space and resources to be used, as well as incur additional costs.diff --git a/apps/docs/content/guides/database/replication/bigquery.mdx b/apps/docs/content/guides/database/replication/bigquery.mdxindex 12f1ae14fc9..ca96330f844 100644--- a/apps/docs/content/guides/database/replication/bigquery.mdx+++ b/apps/docs/content/guides/database/replication/bigquery.mdx@@ -1,14 +1,14 @@---id: 'bigquery-destination'title: 'BigQuery destination'-description: 'Configure BigQuery as an external replication (ETL) destination.'+description: 'Configure BigQuery as a Supabase Pipelines destination.'subtitle: 'Replicate Supabase Postgres tables to BigQuery.'sidebar_label: 'BigQuery'---<Admonition type="caution" title="Private Alpha">-External replication (ETL) is currently in private alpha. Managed pipelines run through Supabase ETL. Access is limited and features may change.+Supabase Pipelines is currently in private alpha. Private alpha features can be unstable and may introduce breaking changes while we evaluate the product direction, refine the feature set, and incorporate customer feedback.</Admonition>@@ -75,7 +75,7 @@ Required permissions:| **Connection pool size** | `4` connections | Size of the BigQuery Storage Write API connection pool. More connections allow more parallel writes, but consume more resources. || **Maximum staleness** | No staleness limit | Maximum allowed age, in minutes, for BigQuery cached metadata before reading base tables. Lower values improve freshness. Higher values can reduce query cost and latency. |-6. Click **Create and start** to begin replication+6. Click **Create and start pipeline** to begin replicationYour replication pipeline now starts copying data from your database to BigQuery.@@ -90,7 +90,7 @@ Once configured, replication to BigQuery:## Source table requirements-BigQuery replication requires each source table to have a primary key, and the publication must include the primary-key columns. Supabase ETL declares those columns as the BigQuery destination primary key so BigQuery change data capture (CDC) can apply `UPSERT` and `DELETE` rows.+BigQuery replication requires each source table to have a primary key, and the publication must include the primary-key columns. Pipelines declares those columns as the BigQuery destination primary key so BigQuery change data capture (CDC) can apply `UPSERT` and `DELETE` rows.BigQuery primary keys are `NOT ENFORCED`, and BigQuery change data capture (CDC) supports composite primary keys with up to 16 columns. Your source primary key must stay unique and non-null because BigQuery uses it to match CDC rows.@@ -104,7 +104,7 @@ Source tables must also use a BigQuery-compatible Postgres `REPLICA IDENTITY` se| `REPLICA IDENTITY NOTHING` | Not supported | Updates and deletes do not include enough row identity for BigQuery to apply them safely. || `REPLICA IDENTITY DEFAULT` without a primary key | Not supported | BigQuery requires a source primary key. |-For a general explanation of how replica identity affects update and delete events, see [How does replica identity affect updates and deletes?](/docs/guides/database/replication/external-replication-faq#how-does-replica-identity-affect-updates-and-deletes).+For a general explanation of how replica identity affects update and delete events, see [How does replica identity affect updates and deletes?](/docs/guides/database/replication/pipelines-faq#how-does-replica-identity-affect-updates-and-deletes).For updates, Postgres does not always send a complete old row through logical replication. It can also mark unchanged toasted values as `unchanged toast` instead of resending the value. BigQuery change data capture (CDC) upserts require a complete new row because omitted columns are not preserved in the destination. The replication pipeline can reconstruct a complete update when the old row image contains the missing value, which is reliable with `REPLICA IDENTITY FULL`.@@ -145,7 +145,7 @@ This structure handles table truncations while maintaining query compatibility.## Schema change support-Schema change support for BigQuery is currently in beta. Supabase ETL supports a limited set of schema changes for BigQuery while the feature is developed further.+Schema change support for BigQuery is currently in beta. Pipelines supports a limited set of schema changes for BigQuery while the feature is developed further.Supported schema changes:@@ -162,7 +162,7 @@ Unsupported or limited schema changes:- Filling existing rows for `ADD COLUMN ... DEFAULT`- Unsupported default expressions-BigQuery requires added columns to be nullable. When a replicated `ADD COLUMN` includes a default, external replication (ETL) can apply supported default metadata for future rows, but BigQuery does not backfill existing rows through that DDL. Existing destination rows remain `NULL` unless you run a separate backfill.+BigQuery requires added columns to be nullable. When a replicated `ADD COLUMN` includes a default, Pipelines can apply supported default metadata for future rows, but BigQuery does not backfill existing rows through that DDL. Existing destination rows remain `NULL` unless you run a separate backfill.Supported defaults are best-effort translations to BigQuery SQL. Unsupported defaults are skipped with a warning instead of failing replication.diff --git a/apps/docs/content/guides/database/replication/manual-replication-setup.mdx b/apps/docs/content/guides/database/replication/manual-replication-setup.mdxindex 8d5076fedc2..e2d414c8c62 100644--- a/apps/docs/content/guides/database/replication/manual-replication-setup.mdx+++ b/apps/docs/content/guides/database/replication/manual-replication-setup.mdx@@ -6,7 +6,7 @@ subtitle: 'Set up replication with Airbyte, Estuary, Fivetran, and other tools.'sidebar_label: 'Setting up'----This guide covers setting up **manual logical replication** using your own tools. If you prefer a managed solution through Supabase ETL, read the [external replication (ETL) setup guide](/docs/guides/database/replication/external-replication-setup) instead.+This guide covers setting up **manual logical replication** using your own tools. If you prefer a managed solution, read [Set up Pipelines](/docs/guides/database/replication/pipelines) instead.<Admonition type="note">diff --git a/apps/docs/content/guides/database/replication/external-replication-faq.mdx b/apps/docs/content/guides/database/replication/pipelines-faq.mdxsimilarity index 67%rename from apps/docs/content/guides/database/replication/external-replication-faq.mdxrename to apps/docs/content/guides/database/replication/pipelines-faq.mdxindex 6c56a465e64..2b1ee6b92e8 100644--- a/apps/docs/content/guides/database/replication/external-replication-faq.mdx+++ b/apps/docs/content/guides/database/replication/pipelines-faq.mdx@@ -1,26 +1,28 @@----id: 'external-replication-faq'-title: 'External replication (ETL) FAQ'-description: 'Frequently asked questions about external replication (ETL).'-subtitle: 'Common questions and answers about external replication (ETL).'+id: 'pipelines-faq'+title: 'Pipelines FAQ'+description: 'Frequently asked questions about Supabase Pipelines.'+subtitle: 'Common questions and answers about managed replication pipelines.'sidebar_label: 'FAQ'---<Admonition type="caution" title="Private Alpha">-External replication (ETL) is currently in private alpha. Managed pipelines run through Supabase ETL. Access is limited and features may change.+Supabase Pipelines is currently in private alpha. Private alpha features can be unstable and may introduce breaking changes while we evaluate the product direction, refine the feature set, and incorporate customer feedback.</Admonition>## What destinations are supported?-External replication (ETL) currently supports **BigQuery** as the managed destination. See the [BigQuery destination guide](/docs/guides/database/replication/bigquery) for configuration details.+Pipelines currently supports **BigQuery** as the managed destination. See the [BigQuery destination guide](/docs/guides/database/replication/bigquery) for configuration details.-We are working on new destinations. "External" means outside the source database, so supported destinations can be Supabase-managed or third-party systems as support expands. Availability may continue to vary based on the planned roll-out strategy.+We are working on new destinations. Supported destinations can be Supabase-managed or third-party systems as support expands. Availability may continue to vary based on the planned roll-out strategy.-## Which plans support external replication (ETL)? [#which-plans-support-external-replication]+{/* supa-mdx-lint-disable-next-line Rule001HeadingCase */}++## Which plans support Pipelines?-External replication (ETL) is available on the Pro, Team, and Enterprise plans.+Pipelines is available on the Pro, Team, and Enterprise plans.{/* supa-mdx-lint-disable-next-line Rule001HeadingCase */}@@ -28,13 +30,15 @@ External replication (ETL) is available on the Pro, Team, and Enterprise plans.We are currently working on a new Supabase Warehouse product designed to address the limitations of the previous Analytics Buckets. Our goal is to build a solution we can confidently stand behind, rather than continuing to support an approach that does not meet the quality and flexibility we want for our users.-As a result, managed replication to Analytics Buckets is no longer available. Right now, **BigQuery** is the only supported managed destination, and we are actively working on expanding capabilities.+As a result, replication into Analytics Buckets via Pipelines is no longer supported. Right now, **BigQuery** is the only supported managed destination, and we are actively working on expanding capabilities.++{/* supa-mdx-lint-disable-next-line Rule001HeadingCase */}-## What does external replication (ETL) install in the database? [#what-does-external-replication-install-in-the-database]+## What does Pipelines install in the database?-When you enable external replication (ETL), Supabase installs database objects that help Supabase ETL track replication state and support schema changes:+When you enable Pipelines, Supabase installs database objects that help track replication state and support schema changes:-- An event trigger that runs on every `ALTER TABLE` statement. Supabase ETL uses this to support schema change handling.+- An event trigger that runs on every `ALTER TABLE` statement. Supabase uses this to support schema change handling.- A set of tables in the `etl` schema. These tables track replication state for your pipelines.The replication state tables are not updated very often, especially after the initial copy phase is complete.@@ -51,15 +55,17 @@ Supported schema changes:- Dropping a `NOT NULL` constraint- Setting or dropping supported column default metadata-External replication (ETL) does not currently support changing column data types, adding `NOT NULL` with `SET NOT NULL`, or filling existing destination rows for `ADD COLUMN ... DEFAULT`. Supported defaults are applied as destination metadata for future rows where BigQuery can represent them. See [BigQuery schema change support](/docs/guides/database/replication/bigquery#schema-change-support) for details.+Pipelines does not currently support changing column data types, adding `NOT NULL` with `SET NOT NULL`, or filling existing destination rows for `ADD COLUMN ... DEFAULT`. Supported defaults are applied as destination metadata for future rows where BigQuery can represent them. See [BigQuery schema change support](/docs/guides/database/replication/bigquery#schema-change-support) for details.++{/* supa-mdx-lint-disable-next-line Rule001HeadingCase */}-## What happens when you disable external replication (ETL)? [#what-happens-when-you-disable-external-replication]+## What happens when you disable Pipelines?-Disabling external replication (ETL) removes the database objects that were installed in your source database, including the replication state tables in the `etl` schema and the DDL event trigger.+Disabling Pipelines removes the database objects that were installed in your source database, including the replication state tables in the `etl` schema and the DDL event trigger.-To remove external replication (ETL) from a project, delete all replication pipelines first. After all pipelines are deleted, the disable action becomes available. For the Dashboard steps, see [Disabling external replication (ETL)](/docs/guides/database/replication/external-replication-setup#disabling-external-replication).+To remove Pipelines from a project, delete all replication pipelines first. After all pipelines are deleted, the disable action becomes available. For the Dashboard steps, see [Disabling Pipelines](/docs/guides/database/replication/pipelines#disabling-pipelines).-Disabling external replication (ETL) stops Supabase from managing replication for the project. It does not delete tables or data that were already written to your destination.+Disabling Pipelines stops Supabase from managing replication for the project. It does not delete tables or data that were already written to your destination.## Why is a table not being replicated?@@ -75,11 +81,11 @@ Custom data types replicate as strings. Check that your destination can interpre## Why are partitioned tables replicated as separate tables?-Postgres controls this with the publication's `publish_via_partition_root` setting. If the setting is `false`, or if you created the publication manually with SQL and did not set it, Postgres publishes changes from the leaf partitions. External replication (ETL) then creates destination tables for those leaf partitions. If `publish_via_partition_root = true`, Postgres publishes changes as the partition root, so the partition hierarchy is treated as the published partition root.+Postgres controls this with the publication's `publish_via_partition_root` setting. If the setting is `false`, or if you created the publication manually with SQL and did not set it, Postgres publishes changes from the leaf partitions. Pipelines then creates destination tables for those leaf partitions. If `publish_via_partition_root = true`, Postgres publishes changes as the partition root, so the partition hierarchy is treated as the published partition root.Publications created from the Dashboard replication flow use `publish_via_partition_root = true`.-See [Partitioned tables](/docs/guides/database/replication/external-replication-setup#partitioned-tables) for examples and the full behavior.+See [Partitioned tables](/docs/guides/database/replication/pipelines#partitioned-tables) for examples and the full behavior.## How does replica identity affect updates and deletes?@@ -131,24 +137,38 @@ After changing replica identity, restart each pipeline that includes the affecte## Why aren't publication changes reflected after adding or removing tables?-After modifying your Postgres publication, you must restart the replication pipeline for changes to take effect. See [Adding or removing tables](/docs/guides/database/replication/external-replication-setup#adding-or-removing-tables) for instructions.+After modifying your Postgres publication, you must restart the replication pipeline for changes to take effect. See [Adding or removing tables](/docs/guides/database/replication/pipelines#adding-or-removing-tables) for instructions.## Why is a pipeline in failed state?Pipeline failures occur during the streaming phase when an error happens while replicating live data. This prevents data loss. To recover:1. Check the error message by hovering over the **Failed** status-2. Click **View status** for detailed information+2. Click **View pipeline** for detailed information3. Fix the underlying issue (e.g., schema mismatches, destination connectivity)4. Restart the pipeline-See [Handling errors](/docs/guides/database/replication/external-replication-monitoring#handling-errors) for more details.+See [Handling errors](/docs/guides/database/replication/pipelines-monitoring#handling-errors) for more details.++## Why was the pipeline stopped?++Supabase may automatically stop a pipeline if it encounters too many errors in a short period of time. This protects your source database, your destination, and the Pipelines system from a pipeline repeatedly retrying a failing operation.++Automatic stopping is a safety mechanism. It prevents repeated pipeline errors from consuming resources or causing wider instability while preserving the pipeline's replication position so you can investigate the underlying issue.++To recover:++1. Check the pipeline error details and replication logs+2. Fix the underlying issue, such as destination connectivity, schema mismatches, permissions, or rate limits+3. Restart the pipeline manually from the [**Database > Replication**](/dashboard/project/_/database/replication) section of the Dashboard++If the same error continues after restart, the pipeline may stop again. Review [Monitor pipeline status](/docs/guides/database/replication/pipelines-monitoring) for troubleshooting steps.## Why is replication lag increasing?Lag increases when Postgres produces WAL faster than the pipeline can confirm it has processed. Common causes include a slow or rate-limited destination, a pipeline issue, heavy source database activity, long transactions, network latency between the pipeline and source database, or a stopped/disconnected pipeline.-Open [**Database > Replication**](/dashboard/project/_/database/replication), click **View status**, and check **Waiting to sync**, **Room before pausing**, **Last check-in**, **Connected**, and **Slot status**. See [Dealing with replication lag](/docs/guides/database/replication/external-replication-monitoring#dealing-with-replication-lag) for the full investigation and response flow.+Open [**Database > Replication**](/dashboard/project/_/database/replication), click **View pipeline**, and check **Waiting to sync**, **Room before pausing**, **Last check-in**, **Connected**, and **Slot status**. See [Dealing with replication lag](/docs/guides/database/replication/pipelines-monitoring#dealing-with-replication-lag) for the full investigation and response flow.## What does a `Lost` slot status mean?@@ -156,26 +176,26 @@ Open [**Database > Replication**](/dashboard/project/_/database/replication), clYou can recreate the pipeline, or open the pipeline's **Advanced settings**, set **Invalidated slot behavior** to **Recreate**, and restart the pipeline. On restart, the pipeline creates a new replication slot and starts replication from scratch for all tables. This is required for consistency because the old slot can no longer provide every change the pipeline missed.-See [Slot statuses](/docs/guides/database/replication/external-replication-monitoring#slot-statuses) for all slot states and what to do next.+See [Slot statuses](/docs/guides/database/replication/pipelines-monitoring#slot-statuses) for all slot states and what to do next.## Why is a table in error state?-Table errors occur during the copy phase. To recover, click **View status**, find the affected table, and reset the table state. This will restart the table copy from the beginning.+Table errors occur during the copy phase. To recover, click **View pipeline**, find the affected table, and reset the table state. This will restart the table copy from the beginning.## How to verify replication is workingCheck the [**Database > Replication**](/dashboard/project/_/database/replication) section of the Dashboard:1. Verify your pipeline shows **Running** status-2. Click **View status** to check table states+2. Click **View pipeline** to check table states3. Ensure all tables show **Live** state (actively replicating)4. Monitor replication lag metrics-See the [external replication (ETL) monitoring guide](/docs/guides/database/replication/external-replication-monitoring) for comprehensive monitoring instructions.+See [Monitor pipeline status](/docs/guides/database/replication/pipelines-monitoring) for comprehensive monitoring instructions.## How to stop or pause replication-You can manage your pipeline using the actions menu in the destinations list. See [Managing your pipeline](/docs/guides/database/replication/external-replication-setup#managing-your-pipeline) for details on available actions.+You can manage your pipeline using the actions menu in the destinations list. See [Managing your pipeline](/docs/guides/database/replication/pipelines#managing-your-pipeline) for details on available actions.<Admonition type="note">@@ -185,13 +205,13 @@ Stopping replication causes changes to queue up in the WAL.## What happens if a project becomes inactive?-If your project becomes inactive, external replication (ETL) stops any running pipelines and does not automatically resume them after the project is restarted.+If your project becomes inactive, Pipelines stops any running pipelines and does not automatically resume them after the project is restarted.After restarting the project, restart each replication pipeline manually from the [**Database > Replication**](/dashboard/project/_/database/replication) section of the Dashboard.## What happens after a downgrade to the free plan?-When a project is downgraded to the Free Plan, all external replication (ETL) pipelines for that project are deleted.+When a project is downgraded to the Free Plan, all replication pipelines created with Pipelines for that project are deleted.## What happens if a table is deleted at the destination?@@ -245,6 +265,6 @@ Navigate to the [**Logs > Replication**](/dashboard/project/_/logs/explorer) secIf you need assistance:-1. Check the [external replication (ETL) setup guide](/docs/guides/database/replication/external-replication-setup) and [external replication (ETL) monitoring guide](/docs/guides/database/replication/external-replication-monitoring)+1. Check [Set up Pipelines](/docs/guides/database/replication/pipelines) and [Monitor pipeline status](/docs/guides/database/replication/pipelines-monitoring)2. Review this FAQ for common issues3. Contact support with your error details and logsdiff --git a/apps/docs/content/guides/database/replication/external-replication-monitoring.mdx b/apps/docs/content/guides/database/replication/pipelines-monitoring.mdxsimilarity index 89%rename from apps/docs/content/guides/database/replication/external-replication-monitoring.mdxrename to apps/docs/content/guides/database/replication/pipelines-monitoring.mdxindex 789607ce586..f466c8108bd 100644--- a/apps/docs/content/guides/database/replication/external-replication-monitoring.mdx+++ b/apps/docs/content/guides/database/replication/pipelines-monitoring.mdx@@ -1,18 +1,18 @@----id: 'external-replication-monitoring'-title: 'External replication (ETL) monitoring'-description: 'Monitor the status and health of your external replication (ETL) pipelines.'+id: 'pipelines-monitoring'+title: 'Monitor pipeline status'+description: 'Monitor the status and health of pipelines created with Supabase Pipelines.'subtitle: 'Track replication status, view logs, and troubleshoot issues.'sidebar_label: 'Monitoring'---<Admonition type="caution" title="Private Alpha">-External replication (ETL) is currently in private alpha. Managed pipelines run through Supabase ETL. Access is limited and features may change.+Supabase Pipelines is currently in private alpha. Private alpha features can be unstable and may introduce breaking changes while we evaluate the product direction, refine the feature set, and incorporate customer feedback.</Admonition>-After setting up external replication (ETL), you can monitor the status and health of your replication pipelines directly from the Dashboard. The pipeline is the active Postgres replication process that continuously streams changes from your database to your destination.+After setting up Pipelines, you can monitor the status and health of your replication pipelines directly from the Dashboard. The pipeline is the active Postgres replication process that continuously streams changes from your database to your destination.### Viewing pipeline status@@ -43,10 +43,10 @@ Each destination shows its pipeline in one of these states:### Viewing detailed pipeline metrics-For detailed information about a specific pipeline, click **View status** on the destination. This opens the pipeline status page where you can monitor replication performance and table states.+For detailed information about a specific pipeline, click **View pipeline** on the destination. This opens the pipeline status page where you can monitor replication performance and table states.<Image- alt="Pipeline Status View"+ alt="Pipeline status view"src="/docs/img/database/replication/replication-view-status.png"width={3560}@@ -69,7 +69,7 @@ The detailed status page shows:| **Connected** | Whether the pipeline's replication slot is active and currently being used. | `Not connected` while the pipeline should be running usually means you should check pipeline status and logs. || **Slot status** | How safely Postgres is keeping the WAL files the pipeline still needs. | `Unreserved` and `Lost` require action. See [Slot statuses](#slot-statuses). |-External replication (ETL) uses one main pipeline replication slot for ongoing changes. During the initial copy phase, it can also create temporary table-sync replication slots. These temporary slots let multiple tables copy in parallel, make large table copies faster, and allow individual tables to be retried or copied again without restarting the whole pipeline.+Pipelines uses one main pipeline replication slot for ongoing changes. During the initial copy phase, it can also create temporary table-sync replication slots. These temporary slots let multiple tables copy in parallel, make large table copies faster, and allow individual tables to be retried or copied again without restarting the whole pipeline.Temporary table-sync slots show the same kind of lag and slot health metrics while they are active. After a table finishes copying and catches up, its temporary slot is removed and ongoing changes continue through the main pipeline slot. For overall replication health, focus first on the main pipeline slot.@@ -125,7 +125,7 @@ After the affected table finishes copying and catches up, the temporary slot is#### Investigate the lag1. Open [**Database > Replication**](/dashboard/project/_/database/replication) and check the destination's lag column.-2. Click **View status** and check **Waiting to sync**, **Room before pausing**, **Last check-in**, **Connected**, and **Slot status**.+2. Click **View pipeline** and check **Waiting to sync**, **Room before pausing**, **Last check-in**, **Connected**, and **Slot status**.3. Check table states. Tables in **Copying** can create temporary lag while the initial snapshot catches up to live changes. If a table-sync slot is **Unreserved** or **Lost**, tune copy parallelism and retry the affected table copy.4. Open [**Logs > Replication**](/dashboard/project/_/logs/explorer) and look for destination errors, retries, rate limits, schema errors, or repeated restarts.5. Compare the lag trend with recent database activity, such as imports, migrations, bulk updates, or long transactions.@@ -136,7 +136,7 @@ After the affected table finishes copying and catches up, the temporary slot is| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- || **Reserved** | If **Waiting to sync** is stable or decreasing, continue monitoring. If it keeps increasing, check destination write performance, logs, and whether the publication includes more tables or write volume than expected. || **Extended** | Treat it as an early warning. Confirm the pipeline is connected, check logs for retries or destination slowness, and reduce avoidable write bursts if possible until the pipeline catches up. |-| **Unreserved** | Act quickly. The slot is at risk of losing required WAL. Check whether the pipeline is connected and making progress, fix destination or pipeline errors, and contact support if the lag continues to grow. |+| **Unreserved** | Act soon. The slot is at risk of losing required WAL. Check whether the pipeline is connected and making progress, fix destination or pipeline errors, and contact support if the lag continues to grow. || **Lost** | The pipeline cannot continue from the existing slot because required WAL has been removed. Recreate the pipeline, or set **Invalidated slot behavior** to **Recreate** in the pipeline's advanced settings and restart the pipeline. This creates a new slot and starts replication from scratch for all tables. || **Unknown** | Check replication logs for errors or missing slot details. If the status remains unknown while the pipeline should be running, contact support with the pipeline ID and recent log details. |@@ -166,7 +166,7 @@ height={2146}**Viewing table error details:**-1. Click **View status** on your destination+1. Click **View pipeline** on your destination2. Check the table states section to identify tables in **Error** state3. Review the error message for that specific table@@ -185,7 +185,7 @@ When a pipeline error occurs, you'll receive an email notification immediately.</Admonition><Image- alt="Pipeline Error Details"+ alt="Pipeline error details"src="/docs/img/database/replication/replication-pipeline-error.png"width={3560}@@ -195,7 +195,7 @@ height={2146}**Viewing pipeline error details:**1. Hover over the **Failed** status in the destinations list to see a quick error summary-2. Click **View status** for comprehensive error information+2. Click **View pipeline** for comprehensive error information3. Navigate to the [**Logs > Replication**](/dashboard/project/_/logs/explorer) section of the Dashboard for detailed error logs**Recovering from pipeline errors:**@@ -233,7 +233,7 @@ Logs contain diagnostic information that may be too technical for most users. If1. Navigate to the [**Database > Replication**](/dashboard/project/_/database/replication) section of the Dashboard2. Verify your destination shows a "Running" status-3. Click **View status** to check replication lag and table states+3. Click **View pipeline** to check replication lag and table states4. Ensure all tables show a "Live" state#### Investigating errors@@ -241,7 +241,7 @@ Logs contain diagnostic information that may be too technical for most users. IfIf you see a **Failed** status:1. Hover over the status to see the error summary-2. Click **View status** to see detailed error information+2. Click **View pipeline** to see detailed error information3. Check table states to identify which tables are affected4. Navigate to the [**Logs > Replication**](/dashboard/project/_/logs/explorer) section of the Dashboard for full error details5. For table errors, attempt to reset the affected tables@@ -265,9 +265,9 @@ If you notice issues with your replication:4. **Verify publication**: Ensure your Postgres publication is properly configured5. **Monitor replication lag**: High lag may indicate performance issues-For more troubleshooting tips, see the [external replication (ETL) FAQ](/docs/guides/database/replication/external-replication-faq).+For more troubleshooting tips, see the [Pipelines FAQ](/docs/guides/database/replication/pipelines-faq).### Next steps-- [Set up external replication (ETL)](/docs/guides/database/replication/external-replication-setup)-- [View external replication (ETL) FAQ](/docs/guides/database/replication/external-replication-faq)+- [Set up Pipelines](/docs/guides/database/replication/pipelines)+- [View the Pipelines FAQ](/docs/guides/database/replication/pipelines-faq)diff --git a/apps/docs/content/guides/database/replication/external-replication-setup.mdx b/apps/docs/content/guides/database/replication/pipelines.mdxsimilarity index 74%rename from apps/docs/content/guides/database/replication/external-replication-setup.mdxrename to apps/docs/content/guides/database/replication/pipelines.mdxindex 849560ba439..f295c17436c 100644--- a/apps/docs/content/guides/database/replication/external-replication-setup.mdx+++ b/apps/docs/content/guides/database/replication/pipelines.mdx@@ -1,26 +1,26 @@----id: 'external-replication-setup'-title: 'Set up external replication (ETL)'-description: 'Set up external replication (ETL) using Postgres logical replication.'-subtitle: 'Configure publications and destinations for external replication (ETL).'+id: 'pipelines'+title: 'Set up Pipelines'+description: 'Create a managed replication pipeline using Postgres logical replication.'+subtitle: 'Configure publications, destinations, and managed replication pipelines.'sidebar_label: 'Setting up'---<Admonition type="caution" title="Private Alpha">-External replication (ETL) is currently in private alpha. Managed pipelines run through Supabase ETL. Access is limited and features may change.+Supabase Pipelines is currently in private alpha. Private alpha features can be unstable and may introduce breaking changes while we evaluate the product direction, refine the feature set, and incorporate customer feedback.</Admonition>-External replication (ETL) is powered by [Supabase ETL](https://github.com/supabase/etl) and uses **Postgres logical replication** to stream changes from your database to destination systems. It provides a managed interface through the Dashboard to configure and monitor replication pipelines. In this context, "external" means outside the source database; destinations can be Supabase-managed or third-party systems as support expands.+Pipelines is a managed CDC feature for creating replication pipelines from Supabase Postgres to destination systems. It uses **Postgres logical replication** with the open-source [Supabase ETL engine](https://github.com/supabase/etl). You choose a destination in the Dashboard, and Supabase runs the pipeline that streams database changes to that destination.## Setup overview-External replication (ETL) requires two main components: a **Postgres publication** (defines what to replicate) and a **destination** (where data is sent). Supabase ETL runs the managed pipeline that reads from the publication and writes to the destination. Follow these steps to set up your replication pipeline.+Pipelines requires two main components: a **Postgres publication** (defines what to replicate) and a **destination** (where data is sent). Supabase runs the managed pipeline that reads from the publication and writes to the destination. Follow these steps to set up your replication pipeline.<Admonition type="tip">-If you already have a Postgres publication set up, you can skip to [Step 2: Enable external replication (ETL)](#step-2-enable-external-replication).+If you already have a Postgres publication set up, you can skip to [Step 2: Enable Pipelines](#step-2-enable-pipelines).</Admonition>@@ -90,7 +90,7 @@ for table orders where (created_at > '2024-01-01');##### Partitioned tables-External replication (ETL) follows Postgres publication semantics for partitioned tables. The `publish_via_partition_root` publication setting controls whether changes from partitions are emitted as the partition root or as the leaf partitions.+Pipelines follows Postgres publication semantics for partitioned tables. The `publish_via_partition_root` publication setting controls whether changes from partitions are emitted as the partition root or as the leaf partitions.| Publication setting | What gets replicated | Destination shape || ------------------------------------------ | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |@@ -118,7 +118,7 @@ Use `publish_via_partition_root = true` when you want analytics queries to readPublications created from the Dashboard replication flow use `publish_via_partition_root = true`. If you create or alter a publication manually with SQL, set this option explicitly so the destination shape matches what you expect.-On Postgres 15 and newer, row filters on partition publications apply during both the initial copy and streaming phases. External replication (ETL) uses the row filter attached to the effective publication table entry: the published partition root when `publish_via_partition_root = true`, and the published leaf relation when `publish_via_partition_root = false`.+On Postgres 15 and newer, row filters on partition publications apply during both the initial copy and streaming phases. Pipelines uses the row filter attached to the effective publication table entry: the published partition root when `publish_via_partition_root = true`, and the published leaf relation when `publish_via_partition_root = false`.<Admonition type="note">@@ -133,17 +133,19 @@ After creating a publication via SQL, you can view it in the Dashboard:1. Navigate to the [**Database > Publications**](/dashboard/project/_/database/publications) section of the Dashboard2. You'll see all your publications listed with their tables-### Step 2: Enable external replication (ETL) [#step-2-enable-external-replication]+{/* supa-mdx-lint-disable-next-line Rule001HeadingCase */}-Before creating an external replication (ETL) pipeline, enable it for your project:+### Step 2: Enable Pipelines++Before creating a managed replication pipeline, enable Pipelines for your project:1. Navigate to the [**Database > Replication**](/dashboard/project/_/database/replication) section of the Dashboard2. Click **Add destination** to show the replication side panel-3. Select an external replication (ETL) destination, such as **BigQuery**-4. Click **Enable external replication (ETL)**+3. Select a Pipelines destination, such as **BigQuery**+4. Click **Enable Pipelines**<Image- alt="Enable external replication (ETL)"+ alt="Enable Pipelines"src="/docs/img/database/replication/replication-enable-replication.png"width={3560}height={2156}@@ -151,7 +153,7 @@ Before creating an external replication (ETL) pipeline, enable it for your proje### Step 3: Configure a destination-Once external replication (ETL) is enabled and you have a Postgres publication, configure a destination. The destination is where your replicated data will be stored, while the pipeline is the active Postgres replication process that continuously streams changes from your database to that destination.+Once Pipelines is enabled and you have a Postgres publication, configure a destination. The destination is where your replicated data will be stored, while the pipeline is the active Postgres replication process that continuously streams changes from your database to that destination.#### Choose and configure your destination@@ -181,23 +183,23 @@ Follow these steps to configure your destination. Each destination has its own sUse **Invalidated slot behavior** carefully. If **Recreate** is selected and the pipeline restarts after Postgres has invalidated the main replication slot, the pipeline creates a new slot and copies all replicated tables again. This full restart is required for consistency because the old slot can no longer provide every change the pipeline missed.-6. Click **Create and start** to begin replication+6. Click **Create and start pipeline** to begin replicationYour replication pipeline now starts copying data from your database to your destination.### Step 4: Monitor your pipeline-After creating a destination, the replication pipeline starts and appears in the destinations list. You can monitor the pipeline's status and performance from the Dashboard.+After you create and start the pipeline, its destination appears in the destinations list. You can monitor the pipeline's status and performance from the Dashboard.<Image- alt="External replication (ETL) destinations list"+ alt="Replication pipelines destinations list"src="/docs/img/database/replication/replication-destinations-list.png"width={3560}height={2146}/>-For comprehensive monitoring instructions including pipeline states, metrics, and logs, see the [external replication (ETL) monitoring guide](/docs/guides/database/replication/external-replication-monitoring).+For comprehensive monitoring instructions including pipeline states, metrics, and logs, see [Monitor pipeline status](/docs/guides/database/replication/pipelines-monitoring).### Managing your pipeline@@ -213,24 +215,26 @@ You can manage your pipeline from the destinations list using the actions menu.Available actions:-- **Start**: Begin replication for a stopped pipeline+- **Start pipeline**: Begin replication for a stopped pipeline- **Stop**: Pause replication (changes will queue up in the WAL)-- **Restart**: Stop and start the pipeline (required after publication changes)+- **Restart pipeline**: Stop and start the pipeline (required after publication changes)- **Edit destination**: Modify destination settings like credentials or advanced options- **Delete**: Remove the destination and permanently stop replication-### Disabling external replication (ETL) [#disabling-external-replication]+{/* supa-mdx-lint-disable-next-line Rule001HeadingCase */}++### Disabling Pipelines-To turn off external replication (ETL) for a project, delete all replication pipelines first. After all pipelines are removed, open the three-dot actions menu on the Replication page and click **Disable external replication (ETL)**.+To turn off Pipelines for a project, delete all replication pipelines first. After all pipelines are removed, open the three-dot actions menu on the Replication page and click **Disable Pipelines**.<Image- alt="Disable external replication (ETL) from the Replication page actions menu"+ alt="Disable Pipelines from the Replication page actions menu"src="/docs/img/database/replication/replication-disable-external-replication.png"width={3560}height={2156}/>-For cleanup details, see [What happens when you disable external replication (ETL)?](/docs/guides/database/replication/external-replication-faq#what-happens-when-you-disable-external-replication).+For cleanup details, see [What happens when you disable Pipelines?](/docs/guides/database/replication/pipelines-faq#what-happens-when-you-disable-pipelines).### Adding or removing tables@@ -272,7 +276,7 @@ If your Postgres publication uses `FOR ALL TABLES` or `FOR TABLES IN SCHEMA`, ne<Admonition type="note">-When a table is deleted at the destination, the behavior depends on the destination. In general, the pipeline tries to recreate the table so replication can continue. To permanently delete a table, pause the pipeline first or remove it from the publication before deleting. See the [external replication (ETL) FAQ](/docs/guides/database/replication/external-replication-faq#what-happens-if-a-table-is-deleted-at-the-destination) for details.+When a table is deleted at the destination, the behavior depends on the destination. In general, the pipeline tries to recreate the table so replication can continue. To permanently delete a table, pause the pipeline first or remove it from the publication before deleting. See the [Pipelines FAQ](/docs/guides/database/replication/pipelines-faq#what-happens-if-a-table-is-deleted-at-the-destination) for details.</Admonition>@@ -282,13 +286,13 @@ Schema change support depends on the destination. BigQuery is currently the only### How it works-Once configured, external replication (ETL):+Once configured, a replication pipeline:1. **Captures** changes from your Postgres database using Postgres publications and logical replication-2. **Streams** the changes through Supabase ETL+2. **Streams** the changes through the managed pipeline3. **Loads** the data to your destination-External replication (ETL) automatically optimizes how changes are delivered to the destination. Supabase ETL currently performs data extraction and loading only, without transformation - your data is replicated as-is to the destination.+Pipelines automatically optimizes how changes are delivered to the destination. It currently performs data extraction and loading only, without transformation - your data is replicated as-is to the destination.### Troubleshooting@@ -299,11 +303,11 @@ If you encounter issues during setup:- **Pipeline failed to start**: Check the error message in the status view for specific details- **No data being replicated**: Verify your Postgres publication includes the correct tables and event types-For more troubleshooting help, see the [external replication (ETL) FAQ](/docs/guides/database/replication/external-replication-faq).+For more troubleshooting help, see the [Pipelines FAQ](/docs/guides/database/replication/pipelines-faq).### Limitations-External replication (ETL) has the following limitations:+Pipelines has the following limitations:- **Primary keys required**: Tables must have primary keys (Postgres logical replication requirement)- **Custom data types**: Custom values replicate as strings. Check that your destination can interpret those string values correctly.@@ -311,12 +315,12 @@ External replication (ETL) has the following limitations:- **Replica identity**: `REPLICA IDENTITY FULL` is strongly recommended. Updates and deletes need enough row data to apply changes correctly at the destination.- **Schema changes**: Currently in beta and limited to BigQuery- **No data transformation**: Data is replicated as-is without transformation-- **Data duplicates**: Duplicates can occur when stopping a pipeline if your database has transactions that take longer than a few minutes to complete. See [Can data duplicates occur during pipeline operations?](/docs/guides/database/replication/external-replication-faq#can-data-duplicates-occur-during-pipeline-operations) for details+- **Data duplicates**: Duplicates can occur when stopping a pipeline if your database has transactions that take longer than a few minutes to complete. See [Can data duplicates occur during pipeline operations?](/docs/guides/database/replication/pipelines-faq#can-data-duplicates-occur-during-pipeline-operations) for detailsDestination-specific limitations, such as BigQuery's row size limits, are documented in each destination guide.### Next steps- [Set up BigQuery](/docs/guides/database/replication/bigquery)-- [Monitor external replication (ETL)](/docs/guides/database/replication/external-replication-monitoring)-- [View external replication (ETL) FAQ](/docs/guides/database/replication/external-replication-faq)+- [Monitor pipeline status](/docs/guides/database/replication/pipelines-monitoring)+- [View the Pipelines FAQ](/docs/guides/database/replication/pipelines-faq)diff --git a/apps/docs/content/guides/getting-started/features.mdx b/apps/docs/content/guides/getting-started/features.mdxindex d27f2ca8a6d..285be68ead4 100644--- a/apps/docs/content/guides/getting-started/features.mdx+++ b/apps/docs/content/guides/getting-started/features.mdx@@ -34,7 +34,7 @@ Encrypt sensitive data and store secrets using our Postgres extension, Supabase### Replication-Automatically replicate your database to destination systems like data warehouses and analytics platforms with external replication (ETL), powered by Supabase ETL. Read [the documentation](/docs/guides/database/replication/external-replication-setup) for more details.+Automatically replicate your database to destination systems like data warehouses and analytics platforms with Supabase Pipelines. Read [the documentation](/docs/guides/database/replication/pipelines) for more details.## Platformdiff --git a/apps/docs/content/guides/storage/analytics/creating-analytics-buckets.mdx b/apps/docs/content/guides/storage/analytics/creating-analytics-buckets.mdxindex 2dbb3f27a6a..f9a6c7b1fe2 100644--- a/apps/docs/content/guides/storage/analytics/creating-analytics-buckets.mdx+++ b/apps/docs/content/guides/storage/analytics/creating-analytics-buckets.mdx@@ -13,7 +13,7 @@ Analytics buckets use [Apache Iceberg](https://iceberg.apache.org/), an open-tab<Admonition type="note" title="About replication">-Analytics Buckets are still available, but managed replication into Analytics Buckets through Supabase ETL is no longer supported. If you need managed replication today, use [external replication (ETL)](/docs/guides/database/replication/external-replication-setup) with **BigQuery**. If you want to use Analytics Buckets, bring your own ingestion pipeline.+Analytics Buckets are still available, but replication into Analytics Buckets via Supabase Pipelines is no longer supported. If you want to use Analytics Buckets, bring your own ingestion pipeline.</Admonition>diff --git a/apps/docs/content/guides/storage/analytics/query-with-postgres.mdx b/apps/docs/content/guides/storage/analytics/query-with-postgres.mdxindex 41c296a0999..1bba106229b 100644--- a/apps/docs/content/guides/storage/analytics/query-with-postgres.mdx+++ b/apps/docs/content/guides/storage/analytics/query-with-postgres.mdx@@ -9,7 +9,7 @@ This is made possible by the [Iceberg Foreign Data Wrapper](/docs/guides/databas<Admonition type="note" title="About ingestion">-Managed replication into Analytics Buckets through Supabase ETL is no longer supported. This guide assumes your Analytics Bucket is being populated by your own ingestion pipeline. If you need managed replication today, use [external replication (ETL)](/docs/guides/database/replication/external-replication-setup) with **BigQuery**.+Replication into Analytics Buckets via Supabase Pipelines is no longer supported. This guide assumes your Analytics Bucket is being populated by your own ingestion pipeline.</Admonition>diff --git a/apps/docs/next.config.mjs b/apps/docs/next.config.mjsindex 8fa45e13c6d..4da99c4f570 100644--- a/apps/docs/next.config.mjs+++ b/apps/docs/next.config.mjs@@ -156,20 +156,35 @@ const nextConfig = {permanent: false,},- // Redirect old external replication slugs in dev/preview envs+ // Redirect old managed pipeline slugs in dev/preview envs+ {+ source: '/guides/database/replication/external-replication-setup',+ destination: '/guides/database/replication/pipelines',+ permanent: true,+ },+ {+ source: '/guides/database/replication/external-replication-monitoring',+ destination: '/guides/database/replication/pipelines-monitoring',+ permanent: true,+ },+ {+ source: '/guides/database/replication/external-replication-faq',+ destination: '/guides/database/replication/pipelines-faq',+ permanent: true,+ },{source: '/guides/database/replication/replication-setup',- destination: '/guides/database/replication/external-replication-setup',+ destination: '/guides/database/replication/pipelines',permanent: true,},{source: '/guides/database/replication/replication-monitoring',- destination: '/guides/database/replication/external-replication-monitoring',+ destination: '/guides/database/replication/pipelines-monitoring',permanent: true,},{source: '/guides/database/replication/replication-faq',- destination: '/guides/database/replication/external-replication-faq',+ destination: '/guides/database/replication/pipelines-faq',permanent: true,},]diff --git a/apps/studio/components/interfaces/Database/Replication/DeleteDestination.tsx b/apps/studio/components/interfaces/Database/Replication/DeleteDestination.tsxindex 0fddb5a6b18..11bcb9ece73 100644--- a/apps/studio/components/interfaces/Database/Replication/DeleteDestination.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DeleteDestination.tsx@@ -24,8 +24,8 @@ export const DeleteDestination = ({confirmLabel={isLoading ? 'Deleting...' : `Delete destination`}confirmPlaceholder="Type in name of destination"confirmString={name ?? 'Unknown'}- text={`This will delete the destination "${name}".`}- alert={{ title: 'You cannot recover this destination once deleted.' }}+ text={`This will delete the destination "${name}" and stop its replication pipeline.`}+ alert={{ title: 'You cannot recover this destination or pipeline once deleted.' }}onCancel={() => setVisible(!visible)}onConfirm={onDelete}/>diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/DestinationForm.utils.test.ts b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/DestinationForm.utils.test.tsindex 0493ac3a1c3..c5dd01668a9 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/DestinationForm.utils.test.ts+++ b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/DestinationForm.utils.test.ts@@ -71,12 +71,12 @@ const baseSnowflakeFormData = {ducklakeS3UseSsl: undefined,ducklakeMetadataSchema: undefined,snowflakeAccountId: ' MYORG-MYACCOUNT ',- snowflakeUser: ' ETL_USER ',+ snowflakeUser: ' PIPELINES_USER ',snowflakePrivateKey: '-----BEGIN PRIVATE KEY-----\nabc\n-----END PRIVATE KEY-----',snowflakePrivateKeyPassphrase: ' secret passphrase ',snowflakeDatabase: ' ANALYTICS ',snowflakeSchema: ' PUBLIC ',- snowflakeRole: ' ETL_ROLE ',+ snowflakeRole: ' PIPELINES_ROLE ',}describe('DestinationForm.utils DuckLake', () => {@@ -333,7 +333,7 @@ describe('DestinationForm.utils Snowflake', () => {expect(config).toEqual({snowflake: {accountId: 'MYORG-MYACCOUNT',- user: 'ETL_USER',+ user: 'PIPELINES_USER',privateKey: '-----BEGIN PRIVATE KEY-----\nabc\n-----END PRIVATE KEY-----',privateKeyPassphrase: undefined,database: 'ANALYTICS',@@ -358,12 +358,12 @@ describe('DestinationForm.utils Snowflake', () => {expect(config).toEqual({snowflake: {accountId: 'MYORG-MYACCOUNT',- user: 'ETL_USER',+ user: 'PIPELINES_USER',privateKey: '-----BEGIN PRIVATE KEY-----\nabc\n-----END PRIVATE KEY-----',privateKeyPassphrase: ' secret passphrase ',database: 'ANALYTICS',schema: 'PUBLIC',- role: 'ETL_ROLE',+ role: 'PIPELINES_ROLE',},})expect(createS3AccessKey).not.toHaveBeenCalled()diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/NoDestinationsAvailable.tsx b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/NoDestinationsAvailable.tsxindex ba0f19e5198..4bbfaa2dc49 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/NoDestinationsAvailable.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/NoDestinationsAvailable.tsx@@ -1,5 +1,7 @@import { DatabaseZap } from 'lucide-react'+import { InlineLink } from '@/components/ui/InlineLink'+export const NoDestinationsAvailable = () => {return (<div className="flex flex-col items-center justify-center h-full px-8 py-16 text-center">@@ -8,8 +10,9 @@ export const NoDestinationsAvailable = () => {</div><h3 className="text-lg font-medium text-foreground mb-2">No destinations available</h3><p className="text-sm text-foreground-light max-w-lg">- Replication destinations are not currently enabled for this project. Contact support to- enable real-time replication to external destinations.+ No Pipelines destinations are available for this project yet. Request{' '}+ <InlineLink href="https://forms.supabase.com/pg_replicate">alpha access</InlineLink> to use+ managed replication pipelines.</p></div>)diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/ValidationFailuresSection.tsx b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/ValidationFailuresSection.tsxindex 868cbfb6678..01d397501c7 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/ValidationFailuresSection.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/ValidationFailuresSection.tsx@@ -36,7 +36,7 @@ export const ValidationFailuresSection = ({<p className="text-sm text-foreground-light mb-2!">{hasCriticalFailures? `Please fix all required issues below${hasWarnings ? ' and review the others' : ''} before continuing.`- : 'The following issues were identified, although you may still proceed to create the destination.'}+ : 'The following issues were identified, although you may still create the pipeline and start replication to the destination.'}</p><Card><Accordion type="multiple">diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/ValidationWarningsDialog.tsx b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/ValidationWarningsDialog.tsxindex 818a41ce9c8..51cf36f9663 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/ValidationWarningsDialog.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/ValidationWarningsDialog.tsx@@ -32,13 +32,13 @@ export const ValidationWarningsDialog = ({<AlertDialogHeader><AlertDialogTitle>{hasWarnings- ? `Create destination with ${warningCount} ${warningCount === 1 ? 'warning' : 'warnings'}?`- : 'Confirm to create destination'}+ ? `Create and start pipeline with ${warningCount} ${warningCount === 1 ? 'warning' : 'warnings'}?`+ : 'Create and start pipeline?'}</AlertDialogTitle><AlertDialogDescription>{hasWarnings? 'Replication can start, but the warnings listed above may affect how some changes are applied downstream. Review them before proceeding.'- : 'No validation issues were found. Confirm to create the destination and start replication.'}+ : 'No validation issues were found. Confirm to create the pipeline and start replication to the destination.'}</AlertDialogDescription></AlertDialogHeader><AlertDialogFooter>@@ -49,7 +49,7 @@ export const ValidationWarningsDialog = ({loading={isLoading}onClick={onConfirm}>- {hasWarnings ? 'Proceed to create' : 'Create destination'}+ {hasWarnings ? 'Create and start pipeline anyway' : 'Create and start pipeline'}</AlertDialogAction></AlertDialogFooter></AlertDialogContent>diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/index.tsx b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/index.tsxindex ec836107817..d29ce01aee2 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/index.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/index.tsx@@ -193,13 +193,15 @@ export const DestinationForm = ({const getSubmitButtonText = () => {if (editMode) {- return existingDestination?.enabled ? 'Apply and restart' : 'Apply and start'+ return existingDestination?.enabled+ ? 'Apply and restart pipeline'+ : 'Apply and start pipeline'} else {if (hasRunValidation && validationWarnings.length > 0 && !hasValidationFailures) {- return 'Create and start anyway'+ return 'Create and start pipeline anyway'}- return 'Create and start'+ return 'Create and start pipeline'}}@@ -365,7 +367,11 @@ export const DestinationForm = ({<p className="text-foreground-light text-sm">{isValidating? 'Validating destination configuration...'- : `${editMode ? 'Updating' : 'Creating'} destination...`}+ : editMode+ ? existingDestination?.enabled+ ? 'Updating destination and restarting pipeline...'+ : 'Updating destination and starting pipeline...'+ : 'Creating pipeline...'}</p></motion.div>) : (diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/useDestinationForm.ts b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/useDestinationForm.tsindex e12b66aedcd..4455b0342bb 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/useDestinationForm.ts+++ b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationForm/useDestinationForm.ts@@ -243,16 +243,16 @@ export const useDestinationForm = ({ selectedType }: { selectedType: DestinationPipelineStatusRequestStatus.RestartRequested,snapshot)- await restartPipeline({ projectRef, pipelineId: existingDestination.pipelineId })toast.success('Settings applied. Restarting the pipeline...')+ restartPipeline({ projectRef, pipelineId: existingDestination.pipelineId })} else {setRequestStatus(existingDestination.pipelineId,PipelineStatusRequestStatus.StartRequested,snapshot)- await startPipeline({ projectRef, pipelineId: existingDestination.pipelineId })toast.success('Settings applied. Starting the pipeline...')+ startPipeline({ projectRef, pipelineId: existingDestination.pipelineId })}onClose()} else {@@ -268,13 +268,17 @@ export const useDestinationForm = ({ selectedType }: { selectedType: Destination)// Set request status only right before starting, then fire and closesetRequestStatus(pipelineId, PipelineStatusRequestStatus.StartRequested, undefined)- await startPipeline({ projectRef, pipelineId })- toast.success('Destination created. Starting the pipeline...')+ toast.success('Pipeline created. Starting the pipeline...')+ startPipeline({ projectRef, pipelineId })onClose()}} catch (error) {- const action = editMode ? 'apply and run' : 'create and start'- toast.error(`Failed to ${action} destination: ${(error as ResponseError).message}`)+ const action = editMode+ ? existingDestination?.enabled+ ? 'apply changes and restart pipeline'+ : 'apply changes and start pipeline'+ : 'create and start pipeline'+ toast.error(`Failed to ${action}: ${(error as ResponseError).message}`)}}diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationPanel.tsx b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationPanel.tsxindex 6d17a68bc1b..de5192ff12c 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationPanel.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationPanel.tsx@@ -15,7 +15,7 @@ import {SheetTitle,} from 'ui'-import { EnableReplicationCallout } from '../EnableReplicationCallout'+import { EnablePipelinesCallout } from '../EnablePipelinesCallout'import { PipelineStatusName } from '../Replication.constants'import { useDestinationInformation } from '../useDestinationInformation'import { useIsETLPrivateAlpha } from '../useIsETLPrivateAlpha'@@ -100,11 +100,11 @@ export const DestinationPanel = ({ onSuccessCreateReadReplica }: DestinationPane<SheetContent size="lg" showClose={false}><div className="flex flex-col h-full" tabIndex={-1}><SheetHeader>- <SheetTitle>{editMode ? 'Edit destination' : 'Create a new destination'}</SheetTitle>+ <SheetTitle>{editMode ? 'Edit destination' : 'Add destination'}</SheetTitle><SheetDescription>{editMode- ? 'Update the configuration for this destination'- : 'A destination can be a read replica or an external destination that receives your database changes in real time.'}+ ? 'Update the configuration for this destination.'+ : 'A destination can be a read replica or an external destination that receives replicated data in near real time.'}</SheetDescription></SheetHeader>@@ -118,11 +118,11 @@ export const DestinationPanel = ({ onSuccessCreateReadReplica }: DestinationPane<SheetSection><div className={cn('border rounded-md p-6 flex flex-col gap-y-4')}><div className="flex flex-col gap-y-1">- <h4>Replicate data to external destinations in real time</h4>+ <h4>Request Pipelines access</h4><p className="text-sm text-foreground-light">- External destinations are in <span className="text-foreground">alpha</span>{' '}- and are being rolled out gradually. Request access below to join the waitlist.- Read replicas are available now.+ Pipelines is in <span className="text-foreground">alpha</span> and being+ rolled out gradually. Request access below to join the waitlist. Read replicas+ are available now.</p></div><div className="flex gap-x-2">@@ -132,20 +132,20 @@ export const DestinationPanel = ({ onSuccessCreateReadReplica }: DestinationPaneiconRight={<ArrowUpRight size={16} strokeWidth={1.5} />}><Link- href="https://forms.supabase.com/pg_replicate"target="_blank"rel="noreferrer"+ href="https://forms.supabase.com/pg_replicate">Request alpha access</Link></Button>- <DocsButton href={`${DOCS_URL}/guides/database/replication#replication`} />+ <DocsButton href={`${DOCS_URL}/guides/database/replication#pipelines`} /></div></div></SheetSection>) : replicationNotEnabled ? (<SheetSection>- <EnableReplicationCallout+ <EnablePipelinesCalloutclassName="p-6!"type={destinationType}hasAccess={hasETLReplicationAccess}diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationTypeSelection.test.tsx b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationTypeSelection.test.tsxindex 358bda15eac..f5d2d442785 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationTypeSelection.test.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationTypeSelection.test.tsx@@ -64,7 +64,7 @@ describe('DestinationTypeSelection', () => {expect(await screen.findByText('Select a destination type')).toBeInTheDocument()})- test('renders the Within Supabase group with Read Replica when dropdown is opened', async () => {+ test('renders Read Replica in the Other group when dropdown is opened', async () => {mockBigQueryEnabled.mockReturnValue(false)mockIcebergEnabled.mockReturnValue(false)mockDucklakeEnabled.mockReturnValue(false)@@ -75,11 +75,11 @@ describe('DestinationTypeSelection', () => {fireEvent.click(await screen.findByRole('combobox'))- expect(await screen.findByText('Within Supabase')).toBeInTheDocument()+ expect(await screen.findByText('Other')).toBeInTheDocument()expect(screen.getByText('Read Replica')).toBeInTheDocument()})- test('renders the Outside Supabase group with BigQuery when the flag is enabled', async () => {+ test('renders the Pipelines group with BigQuery when the flag is enabled', async () => {mockBigQueryEnabled.mockReturnValue(true)mockIcebergEnabled.mockReturnValue(false)mockDucklakeEnabled.mockReturnValue(false)@@ -90,7 +90,7 @@ describe('DestinationTypeSelection', () => {fireEvent.click(await screen.findByRole('combobox'))- expect(await screen.findByText('Outside Supabase')).toBeInTheDocument()+ expect(await screen.findByText('Pipelines')).toBeInTheDocument()expect(screen.getByText('BigQuery')).toBeInTheDocument()})@@ -105,11 +105,12 @@ describe('DestinationTypeSelection', () => {fireEvent.click(await screen.findByRole('combobox'))- await screen.findByText('Within Supabase')+ expect(await screen.findByText('Other')).toBeInTheDocument()+ expect(screen.getByText('Read Replica')).toBeInTheDocument()expect(screen.queryByText('BigQuery')).not.toBeInTheDocument()expect(screen.queryByText('DuckLake')).not.toBeInTheDocument()expect(screen.queryByText('Analytics Bucket')).not.toBeInTheDocument()- expect(screen.queryByText('Outside Supabase')).not.toBeInTheDocument()+ expect(screen.queryByText('Pipelines')).not.toBeInTheDocument()})test('shows alpha warning when an alpha destination type is selected', async () => {diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationTypeSelection.tsx b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationTypeSelection.tsxindex 2d936058cf0..c528ff2e08e 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationTypeSelection.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DestinationPanel/DestinationTypeSelection.tsx@@ -8,6 +8,7 @@ import {SelectGroup,SelectItem,SelectLabel,+ SelectSeparator,SelectTrigger,} from 'ui'import { FormItemLayout } from 'ui-patterns/form/FormItemLayout/FormItemLayout'@@ -74,7 +75,7 @@ export const DestinationTypeSelection = () => {const groups: DestinationTypeGroup[] = [{- label: 'Within Supabase',+ label: 'Other',options: [{value: 'Read Replica',@@ -85,6 +86,11 @@ export const DestinationTypeSelection = () => {isAlpha: false,enabled: isOptionVisible('Read Replica', infrastructureReadReplicas),},+ ],+ },+ {+ label: 'Pipelines',+ options: [{value: 'Analytics Bucket',label: 'Analytics Bucket',@@ -93,11 +99,6 @@ export const DestinationTypeSelection = () => {isAlpha: true,enabled: isOptionVisible('Analytics Bucket', etlEnableIceberg),},- ],- },- {- label: 'Outside Supabase',- options: [{value: 'BigQuery',label: 'BigQuery',@@ -145,7 +146,8 @@ export const DestinationTypeSelection = () => {description={selectedOption?.isAlpha && (<span className="block text-sm text-foreground-light mb-1">- This destination type is in alpha and may change while we iterate.{' '}+ This destination type is in alpha and may be unstable or introduce breaking changes+ while we iterate based on customer feedback.{' '}<InlineLink href="https://github.com/orgs/supabase/discussions/39416">Leave feedback</InlineLink>@@ -172,8 +174,9 @@ export const DestinationTypeSelection = () => {)}</SelectTrigger><SelectContent align="end">- {visibleGroups.map((group) => (+ {visibleGroups.map((group, index) => (<SelectGroup key={group.label}>+ {index > 0 && <SelectSeparator />}<SelectLabel>{group.label}</SelectLabel>{group.options.map((option) => (<SelectItem key={option.value} value={option.value} className="py-2">diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationRow.tsx b/apps/studio/components/interfaces/Database/Replication/DestinationRow.tsxindex fe72e424989..a07c74aaf09 100644--- a/apps/studio/components/interfaces/Database/Replication/DestinationRow.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DestinationRow.tsx@@ -169,7 +169,7 @@ export const DestinationRow = ({ destinationId }: DestinationRowProps) => {) : (<div><p>- {type} (ID: {pipeline?.id})+ {type} (Pipeline ID: {pipeline?.id})</p><p className="text-foreground-lighter">{destinationName}</p></div>@@ -228,7 +228,7 @@ export const DestinationRow = ({ destinationId }: DestinationRowProps) => {)}<Button asChild variant="default" className="relative"><Link href={`/project/${projectRef}/database/replication/${pipeline?.id}`}>- View replication+ View pipeline</Link></Button><RowMenudiff --git a/apps/studio/components/interfaces/Database/Replication/Destinations.tsx b/apps/studio/components/interfaces/Database/Replication/Destinations.tsxindex d6cc0d79330..69f1c617846 100644--- a/apps/studio/components/interfaces/Database/Replication/Destinations.tsx+++ b/apps/studio/components/interfaces/Database/Replication/Destinations.tsx@@ -26,7 +26,7 @@ import { REPLICA_STATUS } from '../../Settings/Infrastructure/InfrastructureConfimport { DestinationPanel } from './DestinationPanel/DestinationPanel'import { DestinationType } from './DestinationPanel/DestinationPanel.types'import { DestinationRow } from './DestinationRow'-import { DisableExternalReplicationDialog } from './DisableExternalReplicationDialog'+import { DisablePipelinesDialog } from './DisablePipelinesDialog'import { ReadReplicaRow } from './ReadReplicas/ReadReplicaRow'import {useIsETLBigQueryPrivateAlpha,@@ -75,8 +75,7 @@ export const Destinations = () => {const searchInputRef = useRef<HTMLInputElement>(null)const [filterString, setFilterString] = useState<string>('')const [statusRefetchInterval, setStatusRefetchInterval] = useState<number | false>(5000)- const [showDisableExternalReplicationDialog, setShowDisableExternalReplicationDialog] =- useState(false)+ const [showDisablePipelinesDialog, setShowDisablePipelinesDialog] = useState(false)const [_, setDestinationType] = useQueryState('destinationType',@@ -146,7 +145,7 @@ export const Destinations = () => {() => sourcesData?.sources.find((source) => source.name === projectRef),[projectRef, sourcesData?.sources])- const canDisableExternalReplication =+ const canDisablePipelines =isSourcesSuccess &&isDestinationsSuccess &&isPipelinesSuccess &&@@ -259,14 +258,14 @@ export const Destinations = () => {</Button></Shortcut><DocsButton href={`${DOCS_URL}/guides/database/replication`} />- {canDisableExternalReplication && (+ {canDisablePipelines && (<DropdownMenu><DropdownMenuTrigger asChild><Button variant="default" icon={<MoreVertical />} className="w-7" /></DropdownMenuTrigger><DropdownMenuContent align="end" className="w-52">- <DropdownMenuItem onClick={() => setShowDisableExternalReplicationDialog(true)}>- Disable external replication+ <DropdownMenuItem onClick={() => setShowDisablePipelinesDialog(true)}>+ Disable Pipelines</DropdownMenuItem></DropdownMenuContent></DropdownMenu>@@ -356,8 +355,8 @@ export const Destinations = () => {><h4>Replication keeps your data in sync across systems</h4><p className="text-foreground-light text-sm text-balance text-center mt-1">- Deploy read replicas for lower latency and better resource management, or capture- database changes to external destinations for real-time data pipelines.+ Deploy Read Replicas for lower latency and workload isolation, or add a Pipelines+ destination for analytics workloads.</p><Buttonicon={<Plus />}@@ -374,9 +373,9 @@ export const Destinations = () => {<DestinationPanel onSuccessCreateReadReplica={() => setStatusRefetchInterval(5000)} />- <DisableExternalReplicationDialog- open={showDisableExternalReplicationDialog}- setOpen={setShowDisableExternalReplicationDialog}+ <DisablePipelinesDialog+ open={showDisablePipelinesDialog}+ setOpen={setShowDisablePipelinesDialog}/></>)diff --git a/apps/studio/components/interfaces/Database/Replication/DisableExternalReplicationDialog.tsx b/apps/studio/components/interfaces/Database/Replication/DisablePipelinesDialog.tsxsimilarity index 83%rename from apps/studio/components/interfaces/Database/Replication/DisableExternalReplicationDialog.tsxrename to apps/studio/components/interfaces/Database/Replication/DisablePipelinesDialog.tsxindex 90d235cf975..d9bab23243e 100644--- a/apps/studio/components/interfaces/Database/Replication/DisableExternalReplicationDialog.tsx+++ b/apps/studio/components/interfaces/Database/Replication/DisablePipelinesDialog.tsx@@ -16,22 +16,19 @@ import { Admonition } from 'ui-patterns/admonition'import { useDeleteReplicationTenantMutation } from '@/data/replication/delete-tenant-mutation'-interface DisableExternalReplicationDialogProps {+interface DisablePipelinesDialogProps {open: booleansetOpen: (value: boolean) => void}-export const DisableExternalReplicationDialog = ({- open,- setOpen,-}: DisableExternalReplicationDialogProps) => {+export const DisablePipelinesDialog = ({ open, setOpen }: DisablePipelinesDialogProps) => {const { ref: projectRef } = useParams()const [error, setError] = useState<string | null>(null)const { mutateAsync: deleteReplicationTenant, isPending: isSubmitting } =useDeleteReplicationTenantMutation({onSuccess: () => {- toast.success('External replication has been disabled')+ toast.success('Pipelines has been disabled')setOpen(false)},onError: () => {},@@ -53,12 +50,12 @@ export const DisableExternalReplicationDialog = ({<AlertDialog open={open} onOpenChange={(open) => !isSubmitting && setOpen(open)}><AlertDialogContent size="small"><AlertDialogHeader>- <AlertDialogTitle>Disable external replication</AlertDialogTitle>+ <AlertDialogTitle>Disable Pipelines</AlertDialogTitle><AlertDialogDescription className="space-y-2 text-sm"><p>This will remove the <code className="text-code-inline">etl</code> schema and all- connected resources from your database. Any active pipelines sending changes to- external destinations will stop.+ connected resources from your database. Any active replication pipelines sending+ changes to external destinations will stop.</p><p>Read replicas are not affected.</p></AlertDialogDescription>@@ -67,7 +64,7 @@ export const DisableExternalReplicationDialog = ({<AlertDialogBody><Admonitiontype="destructive"- title="Unable to disable external replication"+ title="Unable to disable Pipelines"description={error}/></AlertDialogBody>diff --git a/apps/studio/components/interfaces/Database/Replication/EnableReplicationCallout.tsx b/apps/studio/components/interfaces/Database/Replication/EnablePipelinesCallout.tsxsimilarity index 68%rename from apps/studio/components/interfaces/Database/Replication/EnableReplicationCallout.tsxrename to apps/studio/components/interfaces/Database/Replication/EnablePipelinesCallout.tsxindex 8c088ab212b..ed1f13a1fca 100644--- a/apps/studio/components/interfaces/Database/Replication/EnableReplicationCallout.tsx+++ b/apps/studio/components/interfaces/Database/Replication/EnablePipelinesCallout.tsx@@ -21,22 +21,22 @@ import { UpgradePlanButton } from '@/components/ui/UpgradePlanButton'import { useCreateTenantSourceMutation } from '@/data/replication/create-tenant-source-mutation'import { DOCS_URL } from '@/lib/constants'-const EnableReplicationModal = () => {+const EnablePipelinesModal = () => {const { ref: projectRef } = useParams()const [open, setOpen] = useState(false)const { mutate: createTenantSource, isPending: creatingTenantSource } =useCreateTenantSourceMutation({onSuccess: () => {- toast.success('External replication has been successfully enabled!')+ toast.success('Pipelines has been successfully enabled!')setOpen(false)},onError: (error) => {- toast.error(`Failed to enable external replication: ${error.message}`)+ toast.error(`Failed to enable Pipelines: ${error.message}`)},})- const onEnableReplication = async () => {+ const onEnablePipelines = async () => {if (!projectRef) return console.error('Project ref is required')createTenantSource({ projectRef })}@@ -45,27 +45,27 @@ const EnableReplicationModal = () => {<Dialog open={open} onOpenChange={setOpen}><DialogTrigger asChild><Button variant="primary" className="w-min">- Enable external replication+ Enable Pipelines</Button></DialogTrigger><DialogContent><DialogHeader>- <DialogTitle>Enable external replication</DialogTitle>+ <DialogTitle>Enable Pipelines</DialogTitle></DialogHeader><DialogSectionSeparator /><DialogSection className="flex flex-col gap-y-2 p-0!"><Admonitiontype="warning"className="rounded-none border-0"- title="Replication is currently in alpha"+ title="Pipelines is currently in alpha"><p className="text-sm leading-normal!">- External replication streams database changes to destinations outside your Supabase- project. The feature is in active development and may change as we gather feedback.+ Alpha features can be unstable and may introduce breaking changes while we evaluate+ the product direction, refine the feature set, and incorporate customer feedback.</p><p className="text-sm leading-normal!">- Pricing is not finalized. You can enable external replication now; we'll announce- pricing later and notify you before any charges apply.+ Pricing is not finalized. You can enable Pipelines now; we'll announce pricing later+ and notify you before any charges apply.</p></Admonition></DialogSection>@@ -73,8 +73,8 @@ const EnableReplicationModal = () => {<Button variant="default" disabled={creatingTenantSource} onClick={() => setOpen(false)}>Cancel</Button>- <Button variant="primary" loading={creatingTenantSource} onClick={onEnableReplication}>- Enable external replication+ <Button variant="primary" loading={creatingTenantSource} onClick={onEnablePipelines}>+ Enable Pipelines</Button></DialogFooter></DialogContent>@@ -82,7 +82,7 @@ const EnableReplicationModal = () => {)}-export const EnableReplicationCallout = ({+export const EnablePipelinesCallout = ({type,className,hasAccess,@@ -94,19 +94,21 @@ export const EnableReplicationCallout = ({return (<div className={cn('border rounded-md p-4 md:p-12 flex flex-col gap-y-4', className)}><div className="flex flex-col gap-y-1">- <h4>Replicate data to external destinations in real time</h4>+ <h4>Enable Pipelines</h4><p className="text-sm text-foreground-light">- {hasAccess ? 'Enable external replication' : 'Upgrade to the Pro plan'} to start- replicating your database changes to {type ?? 'data warehouses and analytics platforms'}.+ Pipelines creates managed replication pipelines that stream database changes to+ destination systems.{' '}+ {hasAccess ? 'Enable Pipelines for your project' : 'Upgrade to the Pro plan'} to stream+ database changes to {type ?? 'data warehouses and analytics platforms'}.</p></div><div className="flex gap-x-2">{hasAccess ? (- <EnableReplicationModal />+ <EnablePipelinesModal />) : (<UpgradePlanButton source="replication" featureProposition="use replication" />)}- <DocsButton href={`${DOCS_URL}/guides/database/replication#replication`} />+ <DocsButton href={`${DOCS_URL}/guides/database/replication#pipelines`} /></div></div>)diff --git a/apps/studio/components/interfaces/Database/Replication/ReadReplicas/ReadReplicaRow.tsx b/apps/studio/components/interfaces/Database/Replication/ReadReplicas/ReadReplicaRow.tsxindex 6838cdaa3b5..53ff9cfbbb4 100644--- a/apps/studio/components/interfaces/Database/Replication/ReadReplicas/ReadReplicaRow.tsx+++ b/apps/studio/components/interfaces/Database/Replication/ReadReplicas/ReadReplicaRow.tsx@@ -118,7 +118,7 @@ export const ReadReplicaRow = ({ replica, onUpdateReplica }: ReadReplicaRow) =>disabled={status === 'GOING_DOWN'}><Link href={`/project/${ref}/database/replication/replica/${replica.identifier}`}>- View replication+ View replica</Link></Button><DropdownMenu>diff --git a/apps/studio/components/interfaces/Database/Replication/ReplicationPipelineStatus/ReplicationPipelineStatus.utils.tsx b/apps/studio/components/interfaces/Database/Replication/ReplicationPipelineStatus/ReplicationPipelineStatus.utils.tsxindex 68ebf1d39e2..9ab2ebcd4c2 100644--- a/apps/studio/components/interfaces/Database/Replication/ReplicationPipelineStatus/ReplicationPipelineStatus.utils.tsx+++ b/apps/studio/components/interfaces/Database/Replication/ReplicationPipelineStatus/ReplicationPipelineStatus.utils.tsx@@ -12,8 +12,8 @@ export const getStatusConfig = (state: TableState['state']) => {case 'queued':return {badge: <Badge variant="warning">Queued</Badge>,- description: 'Table is waiting for ETL to pick it up for replication.',- tooltip: 'Table is waiting for ETL to pick it up for replication.',+ description: 'Table is waiting for the pipeline to pick it up for replication.',+ tooltip: 'Table is waiting for the pipeline to pick it up for replication.',color: 'text-warning',}case 'copying_table':diff --git a/apps/studio/components/interfaces/Database/Replication/ReplicationPipelineStatus/SlotStatus.tsx b/apps/studio/components/interfaces/Database/Replication/ReplicationPipelineStatus/SlotStatus.tsxindex e1d8f0c24d7..70a1397f20a 100644--- a/apps/studio/components/interfaces/Database/Replication/ReplicationPipelineStatus/SlotStatus.tsx+++ b/apps/studio/components/interfaces/Database/Replication/ReplicationPipelineStatus/SlotStatus.tsx@@ -91,7 +91,7 @@ export const SlotStatusLegend = () => {</ul><div className="border-t border-overlay px-4 py-2.5"><InlineLink- href={`${DOCS_URL}/guides/database/replication/external-replication-monitoring`}+ href={`${DOCS_URL}/guides/database/replication/pipelines-monitoring`}className="text-xs text-foreground-light">Learn more about monitoring replicationdiff --git a/apps/studio/components/interfaces/Database/Replication/useIsETLPrivateAlpha.ts b/apps/studio/components/interfaces/Database/Replication/useIsETLPrivateAlpha.tsindex 71643eda753..3f9c695be9f 100644--- a/apps/studio/components/interfaces/Database/Replication/useIsETLPrivateAlpha.ts+++ b/apps/studio/components/interfaces/Database/Replication/useIsETLPrivateAlpha.ts@@ -3,9 +3,9 @@ import { useFlag } from 'common'import { useSelectedOrganizationQuery } from '@/hooks/misc/useSelectedOrganization'/**- * Organization level opt in for ETL private alpha, there's 2 flags we're using which controls- * the individual destination types. Access to the ETL UI (`useIsETLPrivateAlpha`) will just- * check if the org has access to at least one of the destination types+ * Organization-level access for Pipelines alpha destinations. The flag names still use+ * the original ETL identifiers, but the UI checks whether the org has access to at least one+ * destination type.*/const useIsCurrentOrgInFlagList = (flag: string) => {const flagValue = useFlag(flag)@@ -16,7 +16,7 @@ const useIsCurrentOrgInFlagList = (flag: string) => {? (flagValue as string).split(',').map((x: string) => x.trim()): []- // [Joshen] Override for to enable for all organizations by setting the flag value as `all`+ // [Joshen] Override to enable for all organizations by setting the flag value as `all`if (allowedOrgSlugs.includes('all')) return true// [Joshen] Otherwise fallback to checking against org slugdiff --git a/apps/studio/components/interfaces/Storage/AnalyticsBuckets/AnalyticsBucketDetails/NamespaceWithTables/TableRowComponent.tsx b/apps/studio/components/interfaces/Storage/AnalyticsBuckets/AnalyticsBucketDetails/NamespaceWithTables/TableRowComponent.tsxindex e96f0ae1688..a4e936a0d5d 100644--- a/apps/studio/components/interfaces/Storage/AnalyticsBuckets/AnalyticsBucketDetails/NamespaceWithTables/TableRowComponent.tsx+++ b/apps/studio/components/interfaces/Storage/AnalyticsBuckets/AnalyticsBucketDetails/NamespaceWithTables/TableRowComponent.tsx@@ -345,7 +345,7 @@ export const TableRowComponent = ({ table, schema, namespace }: TableRowComponenhref={`/project/${projectRef}/database/replication/${pipeline?.id}?search=${inferredPostgresTable.schema}.${inferredPostgresTable.name}`}><Eye size={12} className="text-foreground-lighter" />- <p>View replication</p>+ <p>View pipeline</p></Link></DropdownMenuItem>)}diff --git a/apps/studio/components/interfaces/Storage/AnalyticsBuckets/AnalyticsBucketDetails/index.tsx b/apps/studio/components/interfaces/Storage/AnalyticsBuckets/AnalyticsBucketDetails/index.tsxindex 4a19e1a2d7a..3691ec70213 100644--- a/apps/studio/components/interfaces/Storage/AnalyticsBuckets/AnalyticsBucketDetails/index.tsx+++ b/apps/studio/components/interfaces/Storage/AnalyticsBuckets/AnalyticsBucketDetails/index.tsx@@ -248,7 +248,7 @@ export const AnalyticBucketDetails = () => {<Linkhref={`/project/${projectRef}/database/replication/${pipeline.replicator_id}`}>- View replication+ View pipeline</Link></Button>{isPipelineStopped && (diff --git a/apps/studio/data/replication/delete-tenant-mutation.ts b/apps/studio/data/replication/delete-tenant-mutation.tsindex d7696c6225c..26033fae249 100644--- a/apps/studio/data/replication/delete-tenant-mutation.ts+++ b/apps/studio/data/replication/delete-tenant-mutation.ts@@ -55,7 +55,7 @@ export const useDeleteReplicationTenantMutation = ({},async onError(data, variables, context) {if (onError === undefined) {- toast.error(`Failed to disable external replication: ${data.message}`)+ toast.error(`Failed to disable Pipelines: ${data.message}`)} else {onError(data, variables, context)}diff --git a/apps/studio/pages/project/[ref]/database/replication/index.tsx b/apps/studio/pages/project/[ref]/database/replication/index.tsxindex 3c5c2797df3..f96dd1d7c90 100644--- a/apps/studio/pages/project/[ref]/database/replication/index.tsx+++ b/apps/studio/pages/project/[ref]/database/replication/index.tsx@@ -30,8 +30,8 @@ const DatabaseReplicationPage: NextPageWithLayout = () => {<h3 className="text-foreground text-xl prose">Replication</h3></div><p className="prose text-sm max-w-full">- Deploy read replicas across multiple regions, or replicate database changes to- external data warehouses and analytics platforms+ Deploy Read Replicas across multiple regions, or use Pipelines to replicate database+ changes to analytics destinations.</p></div></ScaffoldSection>diff --git a/apps/www/_blog/2025-05-26-open-data-standards-postgres-otel-iceberg.mdx b/apps/www/_blog/2025-05-26-open-data-standards-postgres-otel-iceberg.mdxindex 9f58868e8d4..f79f7a11ccf 100644--- a/apps/www/_blog/2025-05-26-open-data-standards-postgres-otel-iceberg.mdx+++ b/apps/www/_blog/2025-05-26-open-data-standards-postgres-otel-iceberg.mdx@@ -69,7 +69,7 @@ These standards start as a grass-roots movement and commercial entities are comp- if they _don't_ adopt the standard, they will miss out on the growing trend.- if they _do_ adopt the standard, they lower the lock-in for their own tool/platform.-This is a _fantastic_ dynamic for the developer community, and one that we [strongly believe in](https://supabase.com/docs/guides/getting-started/architecture#everything-is-portable): _portability forces companies to compete on experience_.+This is a _fantastic_ dynamic for the developer community, and one that we [strongly believe in](/docs/guides/getting-started/architecture#everything-is-portable): _portability forces companies to compete on experience_.Diving deeper into each of these tools:@@ -111,11 +111,11 @@ The tooling for S3 interoperability differs slightly depending on the use-case:Supabase is now relatively well-known as a Postgres provider. We've spent 5 years building a delightful database platform for developers and that will continue to be our focus.-What's unique about Supabase is that we're not _just_ a Postgres provider (despite the [memes](https://itsjustpostgres.com/)). We also offer [Supabase Storage](https://supabase.com/storage), an S3-compatible object store. Where we're going is less about a database, and more about data. This includes:+What's unique about Supabase is that we're not _just_ a Postgres provider (despite the [memes](https://itsjustpostgres.com/)). We also offer [Supabase Storage](/storage), an S3-compatible object store. Where we're going is less about a database, and more about data. This includes:- Adding OTel to all of the open source tools we maintain.- Adding Iceberg support in Supabase Storage.-- Adding Iceberg support to [Supabase ETL](https://github.com/supabase/supabase_etl) for zero-ETL between Postgres and Iceberg.+- Exploring managed paths for moving Postgres data into analytical systems while preserving open formats and operational isolation.- Adding Iceberg read/write capabilities to Postgres via extensions and FDWs.Our focus from here is the three Open Data Standards: Postgres, OTel, and Iceberg.diff --git a/apps/www/_blog/2025-05-29-building-on-open-table-formats.mdx b/apps/www/_blog/2025-05-29-building-on-open-table-formats.mdxindex f175b01bd3e..097ab333beb 100644--- a/apps/www/_blog/2025-05-29-building-on-open-table-formats.mdx+++ b/apps/www/_blog/2025-05-29-building-on-open-table-formats.mdx@@ -69,6 +69,6 @@ This means the traditional ETL model—extract, transform, and load—starts toSupabase has always been more than just a Postgres host. We are the platform for building modern applications. Supabase starts with [a Postgres database](/database) and includes products for [Authentication](/auth), [Storage](/storage), [Edge Functions](/edge-functions), [Realtime](/realtime), [Vectors](/modules/vector), and more. As the industry moves toward open table formats like Iceberg and S3 as the default storage layer, Supabase’s role evolves with it to be less about a database, and more about data.-Postgres remains the core of the Supabase platform: the system of record for operational data. [As we’ve written](/blog/open-data-standards-postgres-otel-iceberg), we are also building first-class support for OpenTelemetry across our services, enabling developers to collect observability data (logs, metrics, and traces) without managing additional infrastructure. And with [Supabase ETL](https://github.com/supabase/etl), we will provide a lightweight, Postgres-native way to move data into S3 and more, where it can be queried at scale using Iceberg and your choice of analytics engines.+Postgres remains the core of the Supabase platform: the system of record for operational data. [As we’ve written](/blog/open-data-standards-postgres-otel-iceberg), we are also building first-class support for OpenTelemetry across our services, enabling developers to collect observability data (logs, metrics, and traces) without managing additional infrastructure. We are also exploring managed data-movement paths that keep operational Postgres workloads separate from analytical systems while preserving the open-format direction described here.Our goal is to make Supabase the developer’s data cloud: Postgres for transactions, OpenTelemetry for observability, and Iceberg for analytics, all connected by simple, open tools. To do so, we remain focused on what developers need: a backend that starts simple, grows with your product, and keeps your data open and portable at every stage.diff --git a/apps/www/_blog/2025-07-15-analytics-buckets.mdx b/apps/www/_blog/2025-07-15-analytics-buckets.mdxindex 35f5483cd0e..448b64223d0 100644--- a/apps/www/_blog/2025-07-15-analytics-buckets.mdx+++ b/apps/www/_blog/2025-07-15-analytics-buckets.mdx@@ -33,7 +33,7 @@ Analytics buckets are integrated into Supabase Studio, power table-level views iApache Iceberg is a high-performance, open table format for large-scale analytics on object storage. It brings the performance and features of a database to the flexibility of flat files.-We chose Iceberg for its bottomless data model (append-only, immutable history), built-in snapshotting and versioning (time travel), and support for schema evolution. Iceberg is also an open standard widely supported across the ecosystem. Supabase is committed to [**open standards and portability**](https://supabase.com/blog/open-data-standards-postgres-otel-iceberg), and Iceberg aligns with that goal by enabling users to move data in and out without being locked into proprietary formats.+We chose Iceberg for its bottomless data model (append-only, immutable history), built-in snapshotting and versioning (time travel), and support for schema evolution. Iceberg is also an open standard widely supported across the ecosystem. Supabase is committed to [**open standards and portability**](/blog/open-data-standards-postgres-otel-iceberg), and Iceberg aligns with that goal by enabling users to move data in and out without being locked into proprietary formats.## Setting up Analytics Buckets@@ -131,9 +131,9 @@ from market_analytics.prices;## Writing to Analytics Buckets-Writing is a work in progress. We're actively building [**Supabase ETL**](https://github.com/supabase/etl), which will allow you to write directly from Postgres into Iceberg-backed buckets. We'll also add write capability to the Supabase Iceberg Wrapper as soon as write support lands in the upstream [iceberg-rust client library](https://github.com/apache/iceberg-rust). This will complete the workflow of **write → store → query**, all inside Supabase.+Writing is a work in progress. For now, populate Analytics Buckets with your own ingestion pipeline or Iceberg-compatible tooling. We'll also add write capability to the Supabase Iceberg Wrapper as soon as write support lands in the upstream [iceberg-rust client library](https://github.com/apache/iceberg-rust). This will complete the workflow of **write → store → query**, all inside Supabase.-Once live, that enables bottomless Postgres storage through shifting records into Analytics Buckets, all using open formats. As a bonus, Iceberg gets us time travel for free.+Once live, this gives you analytical storage using open formats. As a bonus, Iceberg gets us time travel for free.## Alpha Launch Limitsdiff --git a/apps/www/_blog/2025-12-02-introducing-analytics-buckets.mdx b/apps/www/_blog/2025-12-02-introducing-analytics-buckets.mdxindex d62ab4e9198..f8ec8169e58 100644--- a/apps/www/_blog/2025-12-02-introducing-analytics-buckets.mdx+++ b/apps/www/_blog/2025-12-02-introducing-analytics-buckets.mdx@@ -115,22 +115,6 @@ Analytics Buckets require authentication with two services:You authenticate using your Supabase service key for the catalog and S3 credentials for storage.-## Streaming data with Supabase ETL--Analytics Buckets work hand in hand with [Supabase ETL](/blog/introducing-supabase-etl). ETL captures changes from your Postgres database and streams them to Analytics Buckets in near real time.--This gives you:--- Automatic replication of your Postgres tables--- Near real-time data in your analytics bucket--- Complete changelog with every insert, update, and delete--- No manual data movement or scheduled jobs--To set up replication, create a Postgres publication for the tables you want to replicate, then add an Analytics Buckets destination in the Replication section of the Dashboard.-## Querying from PostgresYou can query Analytics Buckets directly from Postgres using Foreign Data Wrappers. This lets you join hot data in Postgres with historical data in Analytics Buckets.@@ -161,7 +145,7 @@ A common architecture is data tiering: keeping recent data in Postgres and archi1. Partition tables by time in Postgres, keeping a rolling window like the last 90 days-2. Stream all data to Analytics Buckets using Supabase ETL+2. Populate Analytics Buckets with your ingestion pipeline3. Drop old partitions from Postgres@@ -203,7 +187,7 @@ To request access, fill out the form at [forms.supabase.com/analytics-buckets](h3. Connect using PyIceberg, Spark, or your tool of choice-4. Set up ETL to stream data from Postgres automatically+4. Populate the bucket with your ingestion pipelineSeparate your transactional and analytical workloads. Keep Postgres fast. Store history at S3 prices. Query from any tool.diff --git a/apps/www/_blog/2025-12-02-introducing-supabase-etl.mdx b/apps/www/_blog/2025-12-02-introducing-supabase-etl.mdxdeleted file mode 100644index e1f76d1e868..00000000000--- a/apps/www/_blog/2025-12-02-introducing-supabase-etl.mdx+++ /dev/null@@ -1,151 +0,0 @@-----title: 'Introducing Supabase ETL'-description: 'A change-data-capture pipeline that replicates your Postgres tables to analytical destinations like Analytics Buckets and BigQuery in near real time.'-author: riccardo_busetti-imgSocial: 2025-12-02-introducing-supabase-etl/og.png-imgThumb: 2025-12-02-introducing-supabase-etl/thumb.png-categories:- - product- - launch-week-date: '2025-12-02T11:00'-toc_depth: 2------Today we're introducing **Supabase ETL**: a change-data-capture pipeline that replicates your Postgres tables to analytical destinations in near real time.--Supabase ETL reads changes from your Postgres database and writes them to external destinations. It uses logical replication to capture inserts, updates, deletes and truncates as they happen. **Setup takes minutes in the Supabase Dashboard.**--The first supported destination is Google BigQuery.--Supabase ETL is open source. You can find the code on GitHub at [github.com/supabase/etl](http://github.com/supabase/etl).--## Why separate OLTP and OLAP?--Postgres is excellent for transactional workloads like reading a single user record or inserting an order. But when you need to scan millions of rows for analytics, Postgres slows down.--Column-oriented systems like BigQuery, or those built on open formats like Apache Iceberg, are designed for this. They can aggregate massive datasets **orders of magnitude faster**, compress data more efficiently, and handle complex analytical queries that would choke a transactional database.--**Supabase ETL gives you the best of both worlds**: keep your app fast on Postgres while unlocking powerful analytics on purpose-built systems.--## How it works--Supabase ETL captures every change in your Postgres database and delivers it to your analytics destination in near real time.--Here's how:--1. You create a Postgres publication that defines which tables to replicate--2. You configure ETL to connect a publication to a destination--3. ETL reads changes from the publication through a logical replication slot--4. Changes are batched and written to your destination--5. Your data is available for querying in the destination--The pipeline starts with an initial copy of your selected tables, then switches to streaming mode. **Your analytics stay fresh with latency measured in milliseconds to seconds.**--## Setting up ETL--You configure ETL entirely through the Supabase Dashboard. **No code required.**--### Step 1: Create a publication--A publication defines which tables to replicate. You create it with SQL or via the UI:--```sql--- Replicate specific tables-create publication analytics_pub-for table events, orders, users;---- Or replicate all tables in a schema-create publication analytics_pub-for tables in schema public;-```--### Step 2: Enable replication--Navigate to `Database` in your Supabase Dashboard. Select the `Replication` tab and click `Enable Replication`.--### Step 3: Add a destination--Click `Add Destination` and choose your destination.--### Step 4: Monitor your pipeline--The Dashboard shows pipeline status and lag. You can start, stop, restart, or delete pipelines from the actions menu.--## Available destinations--Our goal with Supabase ETL is to let you connect your existing data systems to Supabase. We're actively expanding the list of supported destinations. Right now, the official destination is Google BigQuery.--BigQuery is Google's serverless data warehouse, built for large-scale analytics. It handles petabytes of data and integrates well with existing BI tools and data pipelines.--When you replicate to BigQuery, Supabase ETL creates a view for each table and uses an underlying versioned table to support all operations efficiently. You query the view, and ETL handles the rest.--## Adding and removing tables--You can modify which tables are replicated after your pipeline is running.--To add a table:--```sql-alter publication analytics_pub add table products;-```--To remove a table:--```sql-alter publication analytics_pub drop table orders;-```--After changing your publication, restart the pipeline from the Dashboard actions menu for the changes to take effect.--**Note:** ETL does not remove data from your destination when you remove a table from a publication. This is by design to prevent accidental data loss.--## When to use ETL vs read replicas--Read replicas and ETL solve different problems.--Read replicas help when you need to scale concurrent queries, but they're still Postgres. They don't make analytics faster.--ETL moves your data to systems built for analytics. You get **faster queries on large datasets**, **lower storage costs** through compression, and **complete separation** between your production workload and analytics.--You can use both: read replicas for application read scaling, ETL for analytics.--## Things to know--Replication with Supabase ETL has a few constraints to be aware of:--- Tables must have primary keys (this is a Postgres logical replication requirement)-- Generated columns are not supported-- Custom data types are replicated as strings-- Schema changes are not automatically propagated to destinations-- Data is replicated as-is, without transformation-- During the initial copy phase, changes accumulate in the WAL and are replayed once streaming begins--We're working on schema change support and additional destinations, and evaluating different streaming techniques to improve flexibility and performance.--## Pricing--Supabase ETL is usage-based:--- **$25 per connector per month**-- **$15 per GB** of change data processed after the initial sync-- **Initial copy is free**--## Get started--**Supabase ETL is in private alpha.** To request access, contact your account manager or fill out the form in the Dashboard.--If you want to dive into the code, **the ETL framework is open source** and written in Rust. Check out the repository at [github.com/supabase/etl](http://github.com/supabase/etl).--<div className="video-container">- <iframe- className="w-full"- src="https://www.youtube-nocookie.com/embed/NqtPnND32sE"- title="Introducing Supabase ETL"- allow="accelerometer; autoplay; clipboard-write; encrypted-media; fullscreen; gyroscope; picture-in-picture; web-share"- allowfullscreen- />-</div>diff --git a/apps/www/_blog/2025-12-02-introducing-supabase-pipelines.mdx b/apps/www/_blog/2025-12-02-introducing-supabase-pipelines.mdxnew file mode 100644index 00000000000..ca850205ce2--- /dev/null+++ b/apps/www/_blog/2025-12-02-introducing-supabase-pipelines.mdx@@ -0,0 +1,149 @@+---+title: 'Introducing Supabase Pipelines'+description: 'Managed change-data-capture pipelines that replicate your Postgres tables to analytical destinations like BigQuery in near real time.'+author: riccardo_busetti+imgSocial: 2025-12-02-introducing-supabase-pipelines/og.png+imgThumb: 2025-12-02-introducing-supabase-pipelines/thumb.png+categories:+ - product+ - launch-week+date: '2025-12-02T11:00'+toc_depth: 2+---++Today we're introducing **Supabase Pipelines**: managed change-data-capture pipelines that replicate your Postgres tables to analytical destinations in near real time.++Pipelines reads changes from your Postgres database and writes them to external destinations. It uses logical replication to capture inserts, updates, deletes, and truncates as they happen. **Setup takes minutes in the Supabase Dashboard.**++The first supported destination is Google BigQuery.++Pipelines is powered by the open-source Supabase ETL engine. You can find the code on GitHub at [github.com/supabase/etl](https://github.com/supabase/etl).++## Why separate OLTP and OLAP?++Postgres is excellent for transactional workloads like reading a single user record or inserting an order. But when you need to scan millions of rows for analytics, Postgres slows down.++Analytical systems are designed for this. They can aggregate massive datasets **orders of magnitude faster**, compress data more efficiently, and handle complex analytical queries that would choke a transactional database.++**Pipelines gives you the best of both worlds**: keep your app fast on Postgres while unlocking analytics on purpose-built systems.++## How it works++Pipelines captures every change in your Postgres database and delivers it to your analytics destination in near real time.++Here's how:++1. You create a Postgres publication that defines which tables to replicate++2. You add a destination that connects the publication to an analytical system++3. The pipeline reads changes from the publication through a logical replication slot++4. Changes are batched and written to your destination++5. Your data is available for querying in the destination++The pipeline starts with an initial copy of your selected tables, then switches to streaming mode. **Your analytics stay fresh with latency measured in milliseconds to seconds.**++## Setting up Pipelines++You configure Pipelines entirely through the Supabase Dashboard. **No code required.**++### Step 1: Create a publication++A publication defines which tables to replicate. You create it with SQL or via the UI:++```sql+-- Replicate specific tables+create publication analytics_pub+for table events, orders, users;++-- Or replicate all tables in a schema+create publication analytics_pub+for tables in schema public;+```++### Step 2: Enable Pipelines++Navigate to `Database` in your Supabase Dashboard. Select the `Replication` tab, click `Add destination`, choose a Pipelines destination, and click `Enable Pipelines`.++### Step 3: Configure the destination++Configure your destination details, choose a publication, and click `Create and start pipeline`.++### Step 4: Monitor your pipeline++The Dashboard shows pipeline status and lag. You can start, stop, restart, or delete pipelines from the actions menu.++## Available destinations++Our goal with Pipelines is to let you connect your existing data systems to Supabase. We're actively expanding the list of supported destinations. The first supported destination is Google BigQuery.++BigQuery is Google's serverless data warehouse, built for large-scale analytics. It handles petabytes of data and integrates well with existing BI tools and data pipelines.++When you replicate to BigQuery, Pipelines handles the ongoing change delivery so your analytical system stays up to date.++## Adding and removing tables++You can modify which tables are replicated after your pipeline is running.++To add a table:++```sql+alter publication analytics_pub add table products;+```++To remove a table:++```sql+alter publication analytics_pub drop table orders;+```++After changing your publication, restart the pipeline from the Dashboard actions menu for the changes to take effect.++**Note:** The pipeline does not remove data from your destination when you remove a table from a publication. This is by design to prevent accidental data loss.++## When to use Pipelines vs read replicas++Read replicas and Pipelines solve different problems.++Read replicas help when you need to scale concurrent queries, but they're still Postgres. They don't make analytics faster.++Pipelines moves your data to systems built for analytics. You get **faster queries on large datasets**, **lower storage costs** through compression, and **complete separation** between your production workload and analytics.++You can use both: read replicas for application read scaling, Pipelines for analytics.++## Things to know++Replication with Pipelines has a few constraints to be aware of:++- Tables must have primary keys (this is a Postgres logical replication requirement)+- Generated columns are not supported+- Custom data types are replicated as strings+- Schema changes are not automatically propagated to destinations+- Data is replicated as-is, without transformation+- During the initial copy phase, changes accumulate in the WAL and are replayed once streaming begins++We're working on schema change support and additional destinations, and evaluating different streaming techniques to improve flexibility and performance.++## Pricing++Pipelines pricing is still being finalized during alpha. You can request access now; we'll announce pricing later and notify you before any charges apply.++## Get started++**Pipelines is currently in alpha.** Alpha features can be unstable and may introduce breaking changes while we evaluate the product direction, refine the feature set, and incorporate customer feedback. To request access, contact your account manager or fill out the form in the Dashboard.++If you want to dive into the code, **the underlying Supabase ETL engine is open source** and written in Rust. Check out the repository at [github.com/supabase/etl](https://github.com/supabase/etl).++**Note:** Supabase ETL is now Supabase Pipelines. This video was recorded before the rename; Supabase ETL now refers to the underlying engine that powers Pipelines.++<div className="video-container">+ <iframe+ className="w-full"+ src="https://www.youtube-nocookie.com/embed/NqtPnND32sE"+ title="Introducing Supabase Pipelines"+ allow="accelerometer; autoplay; clipboard-write; encrypted-media; fullscreen; gyroscope; picture-in-picture; web-share"+ allowfullscreen+ />+</div>diff --git a/apps/www/_blog/2026-01-15-read-replicas-vs-bigger-compute.mdx b/apps/www/_blog/2026-01-15-read-replicas-vs-bigger-compute.mdxindex 323ddb75be8..0e626148e93 100644--- a/apps/www/_blog/2026-01-15-read-replicas-vs-bigger-compute.mdx+++ b/apps/www/_blog/2026-01-15-read-replicas-vs-bigger-compute.mdx@@ -41,7 +41,7 @@ The rest of this post explains how to diagnose your specific situation and make## First, diagnose the actual problem-Before choosing a scaling strategy, figure out what is actually causing the slowdown. Throwing hardware at the wrong problem wastes money. The [database performance guide](https://supabase.com/docs/guides/database/debugging-performance) covers diagnostics in depth. Here are the essentials.+Before choosing a scaling strategy, figure out what is actually causing the slowdown. Throwing hardware at the wrong problem wastes money. The [database performance guide](/docs/guides/database/debugging-performance) covers diagnostics in depth. Here are the essentials.### Check your query patterns@@ -103,7 +103,7 @@ Read Replicas cannot help with writes. All INSERT, UPDATE, and DELETE operations### You have headroom in the compute tiers-Supabase offers [compute tiers](https://supabase.com/docs/guides/platform/compute-and-disk) from Micro ($10/month) to 16XL ($3,730/month). If you are on Medium and experiencing slowdowns, upgrading to Large or XL is straightforward and immediate.+Supabase offers [compute tiers](/docs/guides/platform/compute-and-disk) from Micro ($10/month) to 16XL ($3,730/month). If you are on Medium and experiencing slowdowns, upgrading to Large or XL is straightforward and immediate.| Current tier | Next tier | Monthly cost increase | What you get || ------------ | ------------ | --------------------- | --------------------- |@@ -116,7 +116,7 @@ Supabase offers [compute tiers](https://supabase.com/docs/guides/platform/computBefore scaling hardware, check that your queries use indexes effectively. An index is like the index at the back of a book. Instead of reading every page to find a topic, you look it up in the index and jump straight to the right page. Postgres works the same way. Without an index, Postgres reads every row in a table to find matching data. This is called a sequential scan. With an index, Postgres looks up which rows match and jumps directly to them. The difference can be dramatic: a query that takes 30 seconds without an index might take 30 milliseconds with one.-Run `EXPLAIN ANALYZE` on slow queries to see if Postgres is using indexes or doing sequential scans. If you see "Seq Scan" on a large table, you probably need an index. The [Database Advisor](https://supabase.com/docs/guides/database/database-advisors) in your Supabase Dashboard can also identify missing indexes and other performance issues automatically.+Run `EXPLAIN ANALYZE` on slow queries to see if Postgres is using indexes or doing sequential scans. If you see "Seq Scan" on a large table, you probably need an index. The [Database Advisor](/docs/guides/database/database-advisors) in your Supabase Dashboard can also identify missing indexes and other performance issues automatically.**Quick index guidelines:**@@ -151,7 +151,7 @@ Vertical scaling requires no code changes. No connection string updates. No rout## When Read Replicas are the right choice-[Read Replicas](https://supabase.com/blog/introducing-read-replicas) add complexity but unlock capabilities that vertical scaling cannot provide. Choose Read Replicas when:+[Read Replicas](/blog/introducing-read-replicas) add complexity but unlock capabilities that vertical scaling cannot provide. Choose Read Replicas when:### Analytics queries are hurting production@@ -210,7 +210,7 @@ A 4XL primary with a 2XL replica ($960 + $410 = $1,370) costs less than an 8XL p### You want redundancy-Read Replicas provide a warm standby. If your primary has issues, your replica has a recent copy of your data. This is not automatic failover (that is coming with [Multigres](https://supabase.com/blog/multigres-vitess-for-postgres)), but it reduces your blast radius.+Read Replicas provide a warm standby. If your primary has issues, your replica has a recent copy of your data. This is not automatic failover (that is coming with [Multigres](/blog/multigres-vitess-for-postgres)), but it reduces your blast radius.## The decision framework@@ -256,7 +256,7 @@ flowchart TD**Situation:** IoT platform on 4XL ($960/month). Devices send telemetry every second. CPU at 80%. Workload is 60% writes.-**Recommendation:** Upgrade to 8XL ($1,870/month). Write-heavy workloads need a bigger primary. Read Replicas would only help with the 40% that is reads. Consider [Supabase Queues](https://supabase.com/docs/guides/queues) to batch and process writes asynchronously.+**Recommendation:** Upgrade to 8XL ($1,870/month). Write-heavy workloads need a bigger primary. Read Replicas would only help with the 40% that is reads. Consider [Supabase Queues](/docs/guides/queues) to batch and process writes asynchronously.## What about other scaling options?@@ -266,43 +266,42 @@ Read Replicas and compute upgrades are not the only tools:If you are hitting connection limits but CPU is fine, enable connection pooling. Supavisor multiplexes many client connections across fewer database connections. This is free and built into every Supabase project.-### Supabase ETL and Analytics Buckets+### Supabase PipelinesRead Replicas isolate analytics from production, but the replica is still Postgres. It still uses row-based storage optimized for transactions. If your analytics queries scan tens of millions of rows, even a dedicated replica will feel slow.-This is where [Supabase ETL](https://supabase.com/blog/introducing-supabase-etl) and [Analytics Buckets](https://supabase.com/blog/introducing-analytics-buckets) come in. They solve a different problem: not just isolating analytics, but running analytics on infrastructure designed for analytical workloads.+This is where [Supabase Pipelines](/blog/introducing-supabase-pipelines) comes in. It solves a different problem: not just isolating analytics, but moving data into infrastructure designed for analytical workloads.**How it works:**-1. Supabase ETL captures changes from your Postgres tables using change-data-capture (CDC)-2. Changes stream in near real-time to Analytics Buckets (or BigQuery)-3. Analytics Buckets store your data in columnar Parquet format on S3, built on Apache Iceberg-4. You query the data with tools like DuckDB, PyIceberg, or Apache Spark+1. Pipelines captures changes from your Postgres tables using change-data-capture (CDC)+2. Changes stream in near real time to a supported analytical destination+3. The destination stores the data for large scans and aggregations+4. You query the data with BI tools or downstream analytics workflows-Columnar storage is dramatically faster for analytical queries. A query that scans a single column across 100 million rows only reads that column, not the entire row. Compression ratios are higher. Query times drop from minutes to seconds.+Analytical systems are optimized for large scans and aggregations. They keep heavy reporting workloads away from your production database and give data teams a better place to run long-running queries.-**When to use ETL and Analytics Buckets instead of Read Replicas:**+**When to use Pipelines instead of Read Replicas:**- Your analytical queries scan millions of rows regularly- You need to retain historical data for years without bloating your database-- You want 30-90% storage cost savings on large datasets-- You need a complete audit trail with time-travel capabilities-- Your data team wants to use specialized analytics tools (Spark, DuckDB, Python notebooks)+- You need a complete downstream copy for reporting, audit trails, or data warehousing+- Your data team wants to use dedicated analytics and BI tools**When Read Replicas are still the right choice:**- Your analytics queries are moderately heavy but not massive- You want your data team to use the same SQL they already know- You need the simplest possible setup with no new tools-- You also need geo-distribution, which ETL does not provide+- You also need geo-distribution, which Pipelines does not provide-**A common pattern: use both.** Keep 90 days of data in Postgres for fast operational queries. Stream everything to Analytics Buckets for long-term retention and heavy analytics. Your application queries Postgres. Your data team queries Analytics Buckets for historical trends. You get speed where you need it and cost efficiency where you need that.+**A common pattern: use both.** Keep 90 days of data in Postgres for fast operational queries. Stream everything to a supported analytical destination for long-term retention and heavy analytics. Your application queries Postgres. Your data team queries the analytical destination for historical trends. You get speed where you need it and cost efficiency where you need that.### Multigres: the future of horizontal write scalingRead Replicas scale reads. Bigger compute scales everything, but only so far. What happens when you max out the largest compute tier and your workload is write-heavy?-This is the problem [Multigres](https://supabase.com/blog/multigres-vitess-for-postgres) is designed to solve. Multigres is a database proxy layer that brings Vitess-style horizontal scaling to Postgres. Vitess powers some of the largest MySQL deployments in the world (YouTube, Slack, GitHub). Multigres adapts that architecture for Postgres.+This is the problem [Multigres](/blog/multigres-vitess-for-postgres) is designed to solve. Multigres is a database proxy layer that brings Vitess-style horizontal scaling to Postgres. Vitess powers some of the largest MySQL deployments in the world (YouTube, Slack, GitHub). Multigres adapts that architecture for Postgres.**What Multigres enables:**@@ -326,7 +325,7 @@ If you have decided Read Replicas are right for your workload:The replica provisions in a few minutes. You will get a dedicated connection string. For analytics tools, use that connection string directly. For application traffic, the API load balancer handles routing automatically.-Read the full setup guide in [the documentation](https://supabase.com/docs/guides/platform/read-replicas).+Read the full setup guide in [the documentation](/docs/guides/platform/read-replicas).## Summarydiff --git a/apps/www/_blog/2026-05-05-realtime-or-etl-how-to-choose-the-right-tool.mdx b/apps/www/_blog/2026-05-05-realtime-or-pipelines-how-to-choose-the-right-tool.mdxsimilarity index 52%rename from apps/www/_blog/2026-05-05-realtime-or-etl-how-to-choose-the-right-tool.mdxrename to apps/www/_blog/2026-05-05-realtime-or-pipelines-how-to-choose-the-right-tool.mdxindex fa52d0ef776..9aff7c84fb0 100644--- a/apps/www/_blog/2026-05-05-realtime-or-etl-how-to-choose-the-right-tool.mdx+++ b/apps/www/_blog/2026-05-05-realtime-or-pipelines-how-to-choose-the-right-tool.mdx@@ -1,6 +1,6 @@----title: 'Realtime or ETL? How to choose the right tool'-description: 'Both Supabase Realtime and Supabase ETL read changes from your Postgres database using logical replication. But they solve very different problems. Here is how to pick the right one.'+title: 'Realtime or Pipelines? How to choose the right tool'+description: 'Both Realtime and Pipelines read changes from your Postgres database using logical replication. But they solve very different problems. Here is how to pick the right one.'author: eduardo_gurgel, riccardo_busettidate: '2026-05-05'categories:@@ -8,14 +8,14 @@ categories:tags:- realtime- postgres- - etl+ - pipelines- database-imgSocial: 'https://zhfonblqamxferhoguzj.supabase.co/functions/v1/generate-og?template=announcement&layout=horizontal©=Realtime+or+ETL%0A%5BHow+to+choose+the+right+tool%5D&icon=icon-realtime.svg'-imgThumb: 'https://zhfonblqamxferhoguzj.supabase.co/functions/v1/generate-og?template=ruler&layout=icon-only©=Realtime+or+ETL%0A%5BHow+to+choose+the+right+tool%5D&icon=icon-realtime.svg'+imgSocial: 'https://zhfonblqamxferhoguzj.supabase.co/functions/v1/generate-og?template=announcement&layout=horizontal©=Realtime+or+Pipelines%0A%5BHow+to+choose+the+right+tool%5D&icon=icon-realtime.svg'+imgThumb: 'https://zhfonblqamxferhoguzj.supabase.co/functions/v1/generate-og?template=ruler&layout=icon-only©=Realtime+or+Pipelines%0A%5BHow+to+choose+the+right+tool%5D&icon=icon-realtime.svg'toc_depth: 2----Both [Supabase Realtime](https://supabase.com/docs/guides/realtime) and [Supabase ETL](https://supabase.com/features/supabase-etl) read changes from your Postgres database. They both use [logical replication](https://supabase.com/docs/guides/database/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.+Both [Supabase Realtime](/docs/guides/realtime) and [Supabase Pipelines](/docs/guides/database/replication/pipelines) read changes from your Postgres database. They both use [logical replication](/docs/guides/database/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.@@ -24,27 +24,27 @@ This post explains what each product does, how they differ, and when you shouldHere 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.-- **ETL** sends database changes in near real-time to analytical destinations like BigQuery and Analytics Buckets. It is built for reliable data movement.+- **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?"-ETL answers the question: "How do I get my production data into my analytics warehouse?"+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-[Supabase Realtime](https://supabase.com/docs/guides/realtime) is three features in one product:+[Realtime](/docs/guides/realtime) is three features in one product:-1. [**Broadcast.**](https://supabase.com/docs/guides/realtime/broadcast) Send messages between connected clients in real time. No database required. Think cursor positions, typing indicators, or game state.-2. [**Presence.**](https://supabase.com/docs/guides/realtime/presence) Track who is online and what they are doing. Also no database required. Think "3 users are editing this document" or "Jane is typing..."-3. [**Postgres Changes.**](https://supabase.com/docs/guides/realtime/postgres-changes) Listen to INSERT, UPDATE, and DELETE events on your database tables and deliver them to subscribed clients over WebSocket.+1. [**Broadcast.**](/docs/guides/realtime/broadcast) Send messages between connected clients in real time. No database required. Think cursor positions, typing indicators, or game state.+2. [**Presence.**](/docs/guides/realtime/presence) Track who is online and what they are doing. Also no database required. Think "3 users are editing this document" or "Jane is typing..."+3. [**Postgres Changes.**](/docs/guides/realtime/postgres-changes) Listen to INSERT, UPDATE, and DELETE events on your database tables and deliver them to subscribed clients over WebSocket.-Two of these three features, Broadcast and Presence, can work without any database interaction. Client-to-client Broadcast sends messages purely over WebSocket with nothing stored. However, [Broadcast from Database](https://supabase.com/blog/realtime-broadcast-from-database) lets you trigger broadcasts from database changes using triggers, giving you control over which events reach which channels. This matters because Realtime is not just a database change listener. It is a real-time communication layer for your application.+Two of these three features, Broadcast and Presence, can work without any database interaction. Client-to-client Broadcast sends messages purely over WebSocket with nothing stored. However, [Broadcast from Database](/blog/realtime-broadcast-from-database) lets you trigger broadcasts from database changes using triggers, giving you control over which events reach which channels. This matters because Realtime is not just a database change listener. It is a real-time communication layer for your application.### How Postgres Changes works-When a client subscribes to a table, Realtime uses a PostgreSQL replication slot to read changes from the Write-Ahead Log (WAL). For each change, it checks [Row Level Security (RLS)](https://supabase.com/docs/guides/database/postgres/row-level-security) policies against every subscribed user. If a user is authorized to see the change, Realtime sends it over their WebSocket connection.+When a client subscribes to a table, Realtime uses a PostgreSQL replication slot to read changes from the Write-Ahead Log (WAL). For each change, it checks [Row Level Security (RLS)](/docs/guides/database/postgres/row-level-security) policies against every subscribed user. If a user is authorized to see the change, Realtime sends it over their WebSocket connection.This is designed for live UI updates. A user inserts a message into a chat table. Other users see it appear instantly. A row updates in a dashboard table. The chart refreshes automatically.@@ -52,7 +52,7 @@ This is designed for live UI updates. A user inserts a message into a chat tableRealtime's Postgres Changes feature does not guarantee delivery. If a client disconnects for 30 seconds and reconnects, the changes that happened during those 30 seconds are gone. Realtime does not queue them and does not track how far each client has read.-[Broadcast Replay](https://supabase.com/blog/realtime-broadcast-replay) offers limited catch-up for Broadcast from Database messages: clients can request up to 25 messages from the last 3 days using a `since` timestamp. But this only works on private channels, only for database-sourced broadcasts, and is currently in public alpha. It is not a general-purpose replay mechanism for all Realtime events.+[Broadcast Replay](/blog/realtime-broadcast-replay) offers limited catch-up for Broadcast from Database messages: clients can request up to 25 messages from the last 3 days using a `since` timestamp. But this only works on private channels, only for database-sourced broadcasts, and is currently in public alpha. It is not a general-purpose replay mechanism for all Realtime events.Postgres Changes uses temporary replication slots. When no clients are subscribed, it stops replicating data entirely. When clients subscribe again, a new slot is created.@@ -60,54 +60,54 @@ The Realtime team built it this way on purpose. Guaranteed delivery requires perIf you need every change to arrive at its destination, no matter what, Realtime is not the right tool.-## What ETL does+## What Pipelines does-Supabase ETL is a change-data-capture (CDC) pipeline. It reads every INSERT, UPDATE, DELETE, and TRUNCATE from your Postgres tables and writes them to a destination. Right now, the supported destinations are [Analytics Buckets](https://supabase.com/docs/guides/storage/analytics/introduction) (built on Apache Iceberg) and BigQuery.+Pipelines creates managed change-data-capture (CDC) pipelines. A pipeline reads every INSERT, UPDATE, DELETE, and TRUNCATE from your Postgres tables and writes them to a supported destination.-ETL replicates your data 1-to-1 in near real-time. If your destination disconnects or has problems, ETL does not skip over data.+Pipelines replicates your data 1-to-1 in near real time. If your destination disconnects or has problems, the pipeline does not skip over data.-### How ETL works+### How Pipelines works-When you create an ETL pipeline, it connects to your database through a permanent replication slot. First, it performs a full copy of your existing data. Then it switches to streaming mode and captures every change as it happens, with latency measured in milliseconds to seconds (based on configuration parameters, data size, and destination type).+When you create a pipeline, it connects to your database through a permanent replication slot. First, it performs a full copy of your existing data. Then it switches to streaming mode and captures every change as it happens, with latency measured in milliseconds to seconds based on configuration parameters, data size, and destination type.-It's important to note that Supabase ETL doesn't respect Row-Level Security. Supabase ETL reads every piece of data. If you need to filter data, you should use publication filters.+It's important to note that Pipelines doesn't respect Row-Level Security. A pipeline reads every piece of data in its publication. If you need to filter data, you should use publication filters.Changes are batched and written to your destination. If the pipeline crashes, it restarts from the last acknowledged position. No data changes are lost. Note that schema changes (adding or removing columns) do not propagate automatically and require manual handling.-### What ETL guarantees+### What Pipelines guarantees-ETL provides at-least-once delivery. Every change that happens in your database will reach the destination at least once. In rare cases (like a crash during a long-running transaction), a change might be delivered more than once. Exactly-once processing is handled by the destination. Some destinations like BigQuery deduplicate automatically, while others may not.+Pipelines provides at-least-once delivery. Every change that happens in your database will reach the destination at least once. In rare cases (like a crash during a long-running transaction), a change might be delivered more than once. Exactly-once processing is handled by the destination.-ETL uses permanent replication slots. This means Postgres holds onto WAL data until ETL confirms it has been processed. If you stop the pipeline for maintenance and restart it later, it picks up exactly where it left off. Be aware that while the pipeline is paused, Postgres continues to retain WAL data. Extended pauses can lead to significant disk growth, and depending on your Postgres configuration, the pipeline may fail if the WAL retention limit is exceeded.+Pipelines uses permanent replication slots. This means Postgres holds onto WAL data until the pipeline confirms it has been processed. If you stop the pipeline for maintenance and restart it later, it picks up exactly where it left off. Be aware that while the pipeline is paused, Postgres continues to retain WAL data. Extended pauses can lead to significant disk growth, and depending on your Postgres configuration, the pipeline may fail if the WAL retention limit is exceeded.-This is the opposite of Realtime's approach. ETL trades speed for reliability. It may not deliver changes to your warehouse in the same millisecond they happen, but it will deliver every single one.+This is the opposite of Realtime's approach. Pipelines trades speed for reliability. It may not deliver changes to your warehouse in the same millisecond they happen, but it will deliver every single one.## The key differences### Delivery guarantees-| | **Realtime** | **ETL** |+| | **Realtime** | **Pipelines** || ----------------------- | ------------ | --------------------- || Guarantee | Best effort | At-least-once || Missed changes | Lost forever | Replayed on reconnect || Replication slot | Temporary | Permanent || Resume after disconnect | No | Yes |-This is the most important difference. If you need every change to arrive, use ETL. If you need changes to arrive fast and can tolerate occasional gaps, use Realtime.+This is the most important difference. If you need every change to arrive, use Pipelines. If you need changes to arrive fast and can tolerate occasional gaps, use Realtime.### Where data goesRealtime sends data to client applications over WebSocket connections. Your users' browsers and mobile apps are the destination.-ETL sends data to analytical systems. BigQuery, Analytics Buckets, and eventually other data warehouses are the destination.+Pipelines sends data to supported analytical systems.These are fundamentally different targets with fundamentally different needs. Client apps need low latency. Analytical systems need completeness.### Database dependency-Realtime's Broadcast and Presence features can work without touching the database. You can build an entire collaborative experience (cursors, presence indicators, ephemeral messaging) without writing a single database query. However, Postgres Changes and [Broadcast from Database](https://supabase.com/blog/realtime-broadcast-from-database) both require database interaction.+Realtime's Broadcast and Presence features can work without touching the database. You can build an entire collaborative experience (cursors, presence indicators, ephemeral messaging) without writing a single database query. However, Postgres Changes and [Broadcast from Database](/blog/realtime-broadcast-from-database) both require database interaction.-ETL is entirely database-driven. Every byte of data it moves comes from your Postgres tables.+Pipelines is entirely database-driven. Every byte of data it moves comes from your Postgres tables.### Scale characteristics@@ -115,7 +115,7 @@ Realtime's Broadcast and Presence features are built for high throughput and lowPostgres Changes works differently. It processes changes sequentially to maintain ordering. For each change, it runs an RLS authorization check against every subscribed client. With 100 subscribers watching a table, one INSERT generates 100 authorization queries. This is a deliberate design choice that prioritizes correctness and low latency for typical workloads over raw throughput.-ETL processes changes in configurable batches with tunable parallelism. It does not need to authorize individual users because it is moving data to a system, not to end users.+Pipelines processes changes in configurable batches with tunable parallelism. It does not need to authorize individual users because it is moving data to a system, not to end users.## When to use Realtime@@ -130,12 +130,12 @@ Use Realtime when you need to push live updates to your users:The common thread: a human is watching and needs to see changes as they happen.-## When to use ETL+## When to use Pipelines-Use ETL when you need reliable data movement to analytical systems:+Use Pipelines when you need reliable data movement to analytical systems:-- **Analytics and reporting.** Move production data to BigQuery or Iceberg for querying without impacting your production database.-- **Audit trails.** Analytics Buckets stores an append-only changelog of every INSERT, UPDATE, and DELETE. Nothing is lost.+- **Analytics and reporting.** Move production data to an analytical destination for querying without impacting your production database.+- **Audit trails.** Maintain a complete changelog of every INSERT, UPDATE, and DELETE. Nothing is lost.- **Data warehousing.** Replicate your operational data to a columnar format optimized for analytical queries.- **Compliance.** Maintain a complete, verifiable history of all data changes.- **ML pipelines.** Feed fresh data to training or feature stores without querying production.@@ -151,36 +151,36 @@ It works great in development. It even works fine in production for a while. TheThe problem is not that Realtime is broken. The problem is that Realtime was not designed for this job.-If you are piping database changes into another system and you need every change to arrive, use ETL. That is exactly what it was built for.+If you are piping database changes into another system and you need every change to arrive, use Pipelines. That is exactly what it was built for.## Can I use both?Yes. In fact, many applications should.-Consider an e-commerce platform. You might use Realtime to push order status updates to customers in real time ("Your order has shipped!"). At the same time, you use ETL to replicate all order data to BigQuery for daily sales reports and trend analysis.+Consider an e-commerce platform. You might use Realtime to push order status updates to customers in real time ("Your order has shipped!"). At the same time, you use Pipelines to replicate all order data to a supported analytical destination for daily sales reports and trend analysis.Same database. Same tables. Different tools for different jobs.-Realtime handles the live experience. ETL handles the analytical pipeline. Each does what it was designed to do.+Realtime handles the live experience. Pipelines handles the analytical pipeline. Each does what it was designed to do.## Quick reference-| | **Realtime** | **ETL** |-| ------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------- |-| Purpose | Live updates to client apps | Reliable data movement to analytics |-| Delivery | Best effort | At-least-once |-| Destinations | Browsers, mobile apps (WebSocket) | BigQuery, Analytics Buckets |-| Replication slot | Temporary | Permanent |-| Resume on reconnect | No | Yes |-| Database required | Only for Postgres Changes and Broadcast from Database | Yes, always |-| Processing | Sequential per-change with per-subscriber authorization | Batched with configurable parallelism |-| Latency | Typically under 100ms | Seconds (batched) |-| Best for | Human users watching live data | Systems consuming complete data |-| Built with | Elixir (Phoenix) | Rust |-| Open source | [github.com/supabase/realtime](https://github.com/supabase/realtime) | [github.com/supabase/etl](https://github.com/supabase/etl) |+| | **Realtime** | **Pipelines** |+| ------------------- | -------------------------------------------------------------------- | ------------------------------------------------------ |+| Purpose | Live updates to client apps | Reliable data movement to analytics |+| Delivery | Best effort | At-least-once |+| Destinations | Browsers, mobile apps (WebSocket) | Supported analytical destinations |+| Replication slot | Temporary | Permanent |+| Resume on reconnect | No | Yes |+| Database required | Only for Postgres Changes and Broadcast from Database | Yes, always |+| Processing | Sequential per-change with per-subscriber authorization | Batched with configurable parallelism |+| Latency | Typically under 100ms | Seconds (batched) |+| Best for | Human users watching live data | Systems consuming complete data |+| Built with | Elixir (Phoenix) | Rust |+| Open source | [github.com/supabase/realtime](https://github.com/supabase/realtime) | [Supabase ETL engine](https://github.com/supabase/etl) |## Getting started-Supabase Realtime is available on all Supabase projects. Check out the [Realtime documentation](https://supabase.com/docs/guides/realtime) to get started.+Realtime is available on all Supabase projects. Check out the [Realtime documentation](/docs/guides/realtime) to get started.-Supabase ETL is currently in private alpha. You can request access through the Supabase Dashboard or contact your account manager. Read the [ETL blog post](https://supabase.com/blog/introducing-supabase-etl) for more details on how it works.+Pipelines is currently in alpha. Alpha features can be unstable and may introduce breaking changes while we evaluate the product direction, refine the feature set, and incorporate customer feedback. You can request access through the Supabase Dashboard or contact your account manager. Read the [Pipelines announcement](/blog/introducing-supabase-pipelines) for more details on how it works.diff --git a/apps/www/_customers/phoenix-energy.mdx b/apps/www/_customers/phoenix-energy.mdxindex 7211d9f4a77..1d11adc45d2 100644--- a/apps/www/_customers/phoenix-energy.mdx+++ b/apps/www/_customers/phoenix-energy.mdx@@ -130,11 +130,11 @@ for both the business and engineering team.With a reliable Supabase foundation in place, Phoenix Energy is focused on expanding its datacapabilities and responsibly exploring AI:-- **Analytics infrastructure:** The team plans to use upcoming Supabase ETL features to build an end-to-end analytics stack without introducing new syncing layers.+- **Analytics infrastructure:** The team plans to use upcoming Supabase Pipelines features to build an end-to-end analytics stack without introducing new syncing layers.- **AI workloads:** Engineers are testing vector databases and MCP servers in isolated Supabase environments, ensuring compliance with SEC regulations before production rollout.<Quote img="kris-woods-phoenix-energy.jpg" caption="Kris Woods, CTO, Phoenix Energy">- Supabase ETL is going to be really interesting for us. I'd love for everything to live in the same- place so the team can focus on building impactful tools. It really does feel like Supabase is just- getting started and I am excited about how we can grow with them from here.+ Supabase Pipelines is going to be really interesting for us. I'd love for everything to live in+ the same place so the team can focus on building impactful tools. It really does feel like+ Supabase is just getting started and I am excited about how we can grow with them from here.</Quote>diff --git a/apps/www/components/Pricing/PricingTableRow.tsx b/apps/www/components/Pricing/PricingTableRow.tsxindex 4ab9be68b6a..e1868d3b264 100644--- a/apps/www/components/Pricing/PricingTableRow.tsx+++ b/apps/www/components/Pricing/PricingTableRow.tsx@@ -40,7 +40,7 @@ export const pricingTooltips: PricingTooltips = {main: 'Billing is based on the total sum of all outgoing traffic (includes Database, Storage, Realtime, Auth, API, Edge Functions, Supavisor, Log Drains) in GB throughout your billing period. Excludes cache hits.',},'database.replication': {- main: 'External Replication (ETL) is available as an add-on for paid plans. ETL provides change-data-capture pipelines that replicate your Postgres tables to analytical destinations in near real time.\nYou are billed for each active pipeline, the replicated bytes and for initial copies/backfills. Initial copies/backfills are billed at a lower rate.',+ main: 'Supabase Pipelines is available as an add-on for paid plans. It provides change-data-capture pipelines that replicate your Postgres tables to analytical destinations in near real time.\nYou are billed for each active pipeline, the replicated bytes, and initial copies/backfills. Initial copies/backfills are billed at a lower rate.',},'storage.cachedEgress': {main: 'Billing is based on the total sum of outgoing Storage traffic in GB throughout your billing period that is served from our CDN cache.',diff --git a/apps/www/components/Wrapped/Pages/ProductAnnouncements.tsx b/apps/www/components/Wrapped/Pages/ProductAnnouncements.tsxindex 1f265ade5d7..1736bf4ab8d 100644--- a/apps/www/components/Wrapped/Pages/ProductAnnouncements.tsx+++ b/apps/www/components/Wrapped/Pages/ProductAnnouncements.tsx@@ -1,5 +1,6 @@import Link from 'next/link'import { cn } from 'ui'+import { AnimatedGridBackground } from '../AnimatedGridBackground'type Announcement = {@@ -290,8 +291,8 @@ const months: Month[] = [isLaunchWeek: true,announcements: [{- title: 'Supabase ETL',- url: 'https://supabase.com/blog/introducing-supabase-etl',+ title: 'Supabase Pipelines',+ url: 'https://supabase.com/blog/introducing-supabase-pipelines',},{title: 'Analytics Buckets',diff --git a/apps/www/content/md/database.md b/apps/www/content/md/database.mdindex 4f0774421f9..83c071abf4e 100644--- a/apps/www/content/md/database.md+++ b/apps/www/content/md/database.md@@ -17,7 +17,7 @@ Supabase Database gives you a full Postgres database with no compromises. It is- **Read Replicas**: distribute read traffic across replicas in multiple regions for lower latency and higher throughput- **Realtime**: subscribe to INSERT, UPDATE, DELETE, and other changes via WebSockets- **Database Webhooks**: trigger Edge Functions or external HTTP endpoints on table events-- **Supabase ETL**: stream Postgres changes to external data warehouses in real time, with no pipelines+- **Supabase Pipelines**: create managed replication pipelines that stream Postgres changes to external data warehouses in near real time## Technical Detailsdiff --git a/apps/www/data/features.tsx b/apps/www/data/features.tsxindex 9e293d7c7c4..a8046ee69f7 100644--- a/apps/www/data/features.tsx+++ b/apps/www/data/features.tsx@@ -642,22 +642,22 @@ Foreign Data Wrappers simplify data integration by bringing external data into y},},{- title: 'Supabase ETL',+ title: 'Supabase Pipelines',subtitle: 'Real-time data replication to analytical destinations.',- description: `Supabase ETL is a change-data-capture pipeline built in Rust that replicates your Postgres tables to analytical destinations in near real-time. Reading directly from the Postgres Write Ahead Log, ETL ensures your analytics data stays synchronized with your production database.+ description: `Supabase Pipelines creates managed change-data-capture pipelines that replicate your Postgres tables to analytical destinations in near real time. Reading directly from the Postgres Write Ahead Log, each pipeline keeps your analytics data synchronized with your production database.## Key benefits1. Real-time replication: Near real-time data synchronization using Postgres logical replication.-2. Analytics Buckets support: Replicate to Iceberg format for large-scale analytics.-3. BigQuery integration: Direct replication to Google's data warehouse.+2. BigQuery integration: Direct replication to Google's data warehouse.+3. Managed destinations: Start with BigQuery while more destinations are evaluated.4. Complete change history: Captures INSERT, UPDATE, DELETE, and TRUNCATE operations.5. Optimized for analytics: Faster queries and lower storage costs through compression.6. Production isolation: Complete separation of analytics and production workloads.## How it works-ETL uses Postgres logical replication to capture changes. Each replicated table includes a \`cdc_operation\` column tracking the type of change. For Analytics Buckets, data is stored in append-only changelog format using Parquet files. For BigQuery, a view is created for each table backed by versioned tables.+Pipelines uses Postgres logical replication to capture changes. For BigQuery, a view is created for each table backed by versioned tables.-## Supabase ETL is valuable for:+## Pipelines is valuable for:- Data warehousing and business intelligence- Historical analysis and audit trails- Large-scale analytics requiring separation from production@@ -666,14 +666,14 @@ ETL uses Postgres logical replication to capture changes. Each replicated table## LimitationsTables require primary keys. DDL support (schema changes) is currently in development.-Supabase ETL provides a powerful alternative to Read Replicas for analytics workloads, optimizing performance while reducing costs.`,+Pipelines provides a powerful alternative to Read Replicas for analytics workloads, optimizing performance while reducing costs.`,icon: CloudCog,products: [PRODUCT_SHORTNAMES.DATABASE],heroImage: '',- docsUrl: 'https://supabase.github.io/etl/',- slug: 'supabase-etl',+ docsUrl: 'https://supabase.com/docs/guides/database/replication/pipelines',+ slug: 'supabase-pipelines',status: {- stage: PRODUCT_STAGES.PRIVATE_ALPHA,+ stage: PRODUCT_STAGES.PUBLIC_ALPHA,availableOnSelfHosted: false,},},@@ -1609,7 +1609,7 @@ Supabase Storage simplifies adding robust file management to your applications,2. Automatic compaction: S3 Tables merges small files automatically for optimal performance.3. Built-in time travel: Query historical data using snapshots.4. Schema evolution: Evolve schema over time without breaking queries.-5. Integrated with ETL: Real-time replication from Postgres via Supabase ETL.+5. Open ingestion: Populate buckets with your own Iceberg-compatible ingestion pipeline.6. Query from Postgres: Use Iceberg Foreign Data Wrapper to join with operational data.## Query tools supported@@ -2835,17 +2835,17 @@ OrioleDB is a PostgreSQL storage extension built on its pluggable storage framew{title: 'Replication',subtitle: 'Replicate database changes to external destinations.',- description: `Replication uses Postgres logical replication to replicate database changes to external destinations like Analytics Buckets and BigQuery. Changes are captured from the Write Ahead Log and delivered in near real-time to analytical systems.+ description: `Supabase Pipelines uses Postgres logical replication to replicate database changes to external destinations like BigQuery. Changes are captured from the Write Ahead Log and delivered in near real time to analytical systems.## Key benefits1. Near real-time sync: Changes replicated as they occur using WAL reading.-2. Analytics Buckets support: Append-only changelog format in Iceberg.-3. BigQuery integration: Direct replication to Google's data warehouse.+2. BigQuery integration: Direct replication to Google's data warehouse.+3. Managed pipeline: Monitor status, lag, and errors in dashboard.4. Complete change capture: INSERT, UPDATE, DELETE, and TRUNCATE operations.-5. Managed pipeline: Monitor status, lag, and errors in dashboard.+5. Production isolation: Keep analytical workloads away from your primary database.## Destinations-Analytics Buckets create append-only changelog with \`cdc_operation\` column, preserving complete change history in Iceberg format. BigQuery creates views backed by versioned tables for efficient querying.+BigQuery creates views backed by versioned tables for efficient querying. Additional managed destinations are being evaluated as Pipelines develops.## SetupCreate Postgres publication for tables to replicate. Add destination in Replication section of dashboard. Configure destination-specific settings. Monitor pipeline in dashboard.@@ -2863,11 +2863,11 @@ Tables must have primary keys. Logical replication must be enabled.## LimitationsNo DDL support yet (ALTER TABLE, ADD COLUMN). Destination-specific constraints may apply.-Replication provides the real-time data pipeline required for modern analytics architectures.`,+Pipelines provides the real-time data pipeline required for modern analytics architectures.`,icon: DatabaseZap,products: [PRODUCT_SHORTNAMES.DATABASE],heroImage: '',- docsUrl: 'https://supabase.com/docs/guides/database/replication/external-replication-setup',+ docsUrl: 'https://supabase.com/docs/guides/database/replication/pipelines',slug: 'replication',status: {stage: PRODUCT_STAGES.PRIVATE_ALPHA,diff --git a/apps/www/data/products/database/etl-visual.tsx b/apps/www/data/products/database/pipelines-visual.tsxsimilarity index 99%rename from apps/www/data/products/database/etl-visual.tsxrename to apps/www/data/products/database/pipelines-visual.tsxindex 2b70ce8969f..9fb39db43ab 100644--- a/apps/www/data/products/database/etl-visual.tsx+++ b/apps/www/data/products/database/pipelines-visual.tsx@@ -1,6 +1,6 @@import { ComponentProps } from 'react'-export const ETLVisual = (props: ComponentProps<'svg'>) => (+export const PipelinesVisual = (props: ComponentProps<'svg'>) => (<svgxmlns="http://www.w3.org/2000/svg"width="591"diff --git a/apps/www/lib/redirects.js b/apps/www/lib/redirects.jsindex df951603836..a5876e07cd9 100644--- a/apps/www/lib/redirects.js+++ b/apps/www/lib/redirects.js@@ -4,6 +4,26 @@ module.exports = [source: '/blog/pricing',destination: '/pricing',},+ {+ permanent: true,+ source: '/blog/introducing-supabase-etl',+ destination: '/blog/introducing-supabase-pipelines',+ },+ {+ permanent: true,+ source: '/blog/supabase-etl',+ destination: '/blog/introducing-supabase-pipelines',+ },+ {+ permanent: true,+ source: '/blog/realtime-or-etl-how-to-choose-the-right-tool',+ destination: '/blog/realtime-or-pipelines-how-to-choose-the-right-tool',+ },+ {+ permanent: true,+ source: '/features/supabase-etl',+ destination: '/features/supabase-pipelines',+ },{permanent: true,source: '/ui/docs/ai-editors-rules/prompts',@@ -2704,27 +2724,42 @@ module.exports = [{permanent: true,source: '/docs/guides/database/replication/etl-destinations',- destination: '/docs/guides/database/replication/external-replication-setup',+ destination: '/docs/guides/database/replication/pipelines',},{permanent: true,source: '/docs/guides/storage/analytics/replication',- destination: '/docs/guides/database/replication/external-replication-setup',+ destination: '/docs/guides/database/replication/pipelines',+ },+ {+ permanent: true,+ source: '/docs/guides/database/replication/external-replication-setup',+ destination: '/docs/guides/database/replication/pipelines',+ },+ {+ permanent: true,+ source: '/docs/guides/database/replication/external-replication-monitoring',+ destination: '/docs/guides/database/replication/pipelines-monitoring',+ },+ {+ permanent: true,+ source: '/docs/guides/database/replication/external-replication-faq',+ destination: '/docs/guides/database/replication/pipelines-faq',},{permanent: true,source: '/docs/guides/database/replication/replication-setup',- destination: '/docs/guides/database/replication/external-replication-setup',+ destination: '/docs/guides/database/replication/pipelines',},{permanent: true,source: '/docs/guides/database/replication/replication-monitoring',- destination: '/docs/guides/database/replication/external-replication-monitoring',+ destination: '/docs/guides/database/replication/pipelines-monitoring',},{permanent: true,source: '/docs/guides/database/replication/replication-faq',- destination: '/docs/guides/database/replication/external-replication-faq',+ destination: '/docs/guides/database/replication/pipelines-faq',},{permanent: true,diff --git a/apps/www/pages/database.tsx b/apps/www/pages/database.tsxindex 35302fcb3a3..d2139076bf3 100644--- a/apps/www/pages/database.tsx+++ b/apps/www/pages/database.tsx@@ -19,9 +19,9 @@ import ProductsNav from '@/components/Products/ProductsNav'import ProductHeader from '@/components/Sections/ProductHeader'import MainProducts from '@/data/MainProducts'import ApiExamplesData from '@/data/products/database/api-examples'-import { ETLVisual } from '@/data/products/database/etl-visual'import ExtensionsExamplesData from '@/data/products/database/extensions-examples'import HighlightsCards from '@/data/products/database/highlight-cards'+import { PipelinesVisual } from '@/data/products/database/pipelines-visual'import SqlViewCarouselData from '@/data/products/database/sql-view-carousel.json'import TableViewCarouselData from '@/data/products/database/table-view-carousel.json'import { breadcrumbs } from '@/lib/breadcrumbs'@@ -284,11 +284,11 @@ function Database() {<SectionContainer><div className="grid grid-cols-12 lg:gap-16"><div className="col-span-12 mb-8 lg:col-span-6 xl:col-span-5">- <h2 className="h2">Supabase ETL</h2>+ <h2 className="h2">Supabase Pipelines</h2><p className="p text-lg">Stream your Postgres data to external systems.</p><p className="p">Automatically replicate your database changes to external data warehouses and- analytics platforms in real-time, without pipelines.+ analytics platforms in near real time with managed replication pipelines.</p><div className="my-8">@@ -308,13 +308,13 @@ function Database() {<Link href="/docs/guides/database/replication">Read the docs</Link></Button><Button asChild size="small" variant="default" icon={<ArrowUpRight />}>- <Link href="/blog/supabase-etl">Read the blog post</Link>+ <Link href="/blog/introducing-supabase-pipelines">Read the blog post</Link></Button></div></div><div className="col-span-12 lg:col-span-6 lg:col-start-7">- {/* TODO: Add ETL illustration */}- <ETLVisual className="w-full" />+ {/* TODO: Add Pipelines illustration */}+ <PipelinesVisual className="w-full" /></div></div></SectionContainer>diff --git a/apps/www/pages/storage.tsx b/apps/www/pages/storage.tsxindex 4b597c27aff..f55b78e815a 100644--- a/apps/www/pages/storage.tsx+++ b/apps/www/pages/storage.tsx@@ -260,7 +260,7 @@ function StoragePage() {<Link href="/docs/guides/storage/analytics/introduction">Read the docs</Link></Button><Button asChild size="small" variant="default" icon={<ArrowUpRight />}>- <Link href="/blog/analytics-buckets">Read the blog post</Link>+ <Link href="/blog/introducing-analytics-buckets">Read the blog post</Link></Button></div></div>diff --git a/apps/www/public/images/blog/2025-12-02-introducing-supabase-etl/og.png b/apps/www/public/images/blog/2025-12-02-introducing-supabase-pipelines/og.pngsimilarity index 100%rename from apps/www/public/images/blog/2025-12-02-introducing-supabase-etl/og.pngrename to apps/www/public/images/blog/2025-12-02-introducing-supabase-pipelines/og.pngdiff --git a/apps/www/public/images/blog/2025-12-02-introducing-supabase-etl/thumb.png b/apps/www/public/images/blog/2025-12-02-introducing-supabase-pipelines/thumb.pngsimilarity index 100%rename from apps/www/public/images/blog/2025-12-02-introducing-supabase-etl/thumb.pngrename to apps/www/public/images/blog/2025-12-02-introducing-supabase-pipelines/thumb.pngdiff --git a/packages/shared-data/pricing.ts b/packages/shared-data/pricing.tsindex 56362e1bdf5..ea94e7380e8 100644--- a/packages/shared-data/pricing.ts+++ b/packages/shared-data/pricing.ts@@ -197,7 +197,7 @@ export const pricing: Pricing = {},{key: 'database.replication',- title: 'External Replication (ETL)',+ title: 'Pipelines',plans: {free: false,pro: [