Skip to content

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

ref(docs): Remove Analytics Buckets destination from docs (#43590)

Riccardo Busetti1201f1cdf900
diff --git a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts
index 94a9dc993dd..38cd600d0be 100644
--- a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts
+++ b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts
@@ -2047,10 +2047,6 @@ export const storage: NavMenuConstant = {
name: 'Iceberg Catalog',
url: '/guides/storage/analytics/connecting-to-analytics-bucket' as `/${string}`,
},
- {
- name: 'Realtime Data-Sync',
- url: '/guides/storage/analytics/replication' as `/${string}`,
- },
{
name: 'Query with Postgres',
url: '/guides/storage/analytics/query-with-postgres' as `/${string}`,
diff --git a/apps/docs/content/guides/database/replication.mdx b/apps/docs/content/guides/database/replication.mdx
index b381e992ad0..737da556b38 100644
--- a/apps/docs/content/guides/database/replication.mdx
+++ b/apps/docs/content/guides/database/replication.mdx
@@ -34,7 +34,15 @@ Replication is currently in private alpha. Access is limited and features may ch
</Admonition>
-Replication powered by [Supabase ETL](https://github.com/supabase/etl) automatically replicates data to supported systems.
+Replication powered by [Supabase ETL](https://github.com/supabase/etl) automatically replicates data to supported systems. Right now, **BigQuery** is the only supported managed destination.
+
+<Admonition type="note" title="Why Analytics Buckets are no longer listed">
+
+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.
+
+At the moment, BigQuery is the only supported destination, but we are actively working on expanding capabilities.
+
+</Admonition>
- [Set up replication](/docs/guides/database/replication/replication-setup)
diff --git a/apps/docs/content/guides/database/replication/replication-faq.mdx b/apps/docs/content/guides/database/replication/replication-faq.mdx
index bb85b14a0c5..967c4022bec 100644
--- a/apps/docs/content/guides/database/replication/replication-faq.mdx
+++ b/apps/docs/content/guides/database/replication/replication-faq.mdx
@@ -14,9 +14,16 @@ Replication is currently in private alpha. Access is limited and features may ch
## What destinations are supported?
-Replication currently supports Analytics Buckets (Iceberg format) and BigQuery. See the destination tabs in the [Setup guide](/docs/guides/database/replication/replication-setup#step-3-add-a-destination) for configuration details.
+Replication currently supports **BigQuery** as the only managed destination. See the [Setup guide](/docs/guides/database/replication/replication-setup#step-3-add-a-destination) for configuration details.
-Availability varies based on the planned roll-out strategy. The destinations you can access depend on your project and access level.
+We are working on adding more destinations in the future. Availability may continue to vary based on the planned roll-out strategy.
+
+{/* supa-mdx-lint-disable-next-line Rule001HeadingCase */}
+## What happened to Analytics Buckets replication?
+
+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 through Supabase ETL is no longer available. Right now, **BigQuery** is the only supported managed destination, and we are actively working on expanding capabilities.
## Why is a table not being replicated?
@@ -66,7 +73,7 @@ Note: Stopping replication will cause changes to queue up in the WAL.
## What happens if a table is deleted at the destination?
-If a table is deleted downstream at the destination (e.g., in your Analytics Bucket or BigQuery dataset), the replication pipeline will automatically recreate it.
+If a table is deleted downstream at the destination (for example, in your BigQuery dataset), the replication pipeline will automatically recreate it.
This behavior is by design to prevent the pipeline from breaking if tables are accidentally deleted. The pipeline ensures that all tables in your publication are always present at the destination.
diff --git a/apps/docs/content/guides/database/replication/replication-setup.mdx b/apps/docs/content/guides/database/replication/replication-setup.mdx
index f0f3ce70a7e..6188318c9f2 100644
--- a/apps/docs/content/guides/database/replication/replication-setup.mdx
+++ b/apps/docs/content/guides/database/replication/replication-setup.mdx
@@ -117,119 +117,15 @@ Once replication is enabled and you have a Postgres publication, you can add a d
#### Choose and configure your destination
-Follow these steps to configure your destination. The specific configuration depends on which destination type you choose. Both Analytics Buckets and BigQuery destinations are supported, though availability varies based on the planned roll-out strategy.
+Follow these steps to configure your destination. Right now, **BigQuery** is the only managed destination available in Replication.
-<Tabs
- scrollable
- size="small"
- type="underlined"
- defaultActiveId="analytics-buckets"
- queryGroup="destination"
->
-<TabPanel id="analytics-buckets" label="Analytics Buckets">
+<Admonition type="note" title="Why Analytics Buckets are no longer listed here">
-[Analytics Buckets](/docs/guides/storage/analytics/introduction) are specialized storage buckets in Supabase Storage designed for analytical workloads. They provide S3-compatible storage and use the [Apache Iceberg](https://iceberg.apache.org/) open table format, making your data accessible via standard tools like DuckDB, Spark, and other analytics platforms.
+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.
-When you replicate to Analytics Buckets, your database changes are automatically written in Iceberg format, creating tables in object storage that you can query for analytics.
+At the moment, BigQuery is the only supported destination, but we are actively working on expanding capabilities.
-##### Step 1: Create an analytics bucket
-
-First, create an analytics bucket to store your replicated data:
-
-1. Navigate to [Storage](/dashboard/project/_/storage/buckets) → **Analytics** in your Supabase Dashboard
-2. Click **New bucket**
-
- <Image
- alt="Create new analytics bucket"
- src="/docs/img/database/replication/replication-iceberg-new-bucket.png"
- width={3560}
- height={2146}
- />
-
-3. Fill in the bucket details:
-
- {' '}
-
- <Image
- alt="Analytics bucket details"
- src="/docs/img/database/replication/replication-iceberg-details.png"
- width={3560}
- height={2146}
- />
-
- - **Name**: A unique name for your bucket (e.g., `analytics_warehouse`)
- - **Region**: Select the region where your data will be stored
-
-4. Click **Create bucket**
-
-5. **Copy the credentials** displayed after bucket creation. You'll need these in the next steps:
- - **Catalog Token**: Authentication token for accessing the Iceberg catalog
- - **S3 Access Key ID**: Access key for S3-compatible storage
- - **S3 Secret Access Key**: Secret key for S3-compatible storage
-
-##### Step 2: Configure analytics buckets as a destination
-
-1. Navigate to [Database](/dashboard/project/_/database/replication) → **replication** in your Supabase Dashboard
-2. Click **Add destination**
-
- <Image
- alt="Add Destination"
- src="/docs/img/database/replication/replication-add-destination.png"
- width={3560}
- height={2146}
- />
-
-3. Configure the general settings:
-
- - **Destination name**: A name to identify this destination (e.g., "Analytics Warehouse")
- - **Publication**: The publication to replicate data from (created in [Step 1](#step-1-create-a-postgres-publication))
- - **Destination type**: Select **Analytics Buckets**
-
-4. Configure Analytics Buckets settings:
-
- - **Bucket**: The name of your analytics bucket from Step 1
- - **Namespace**: The schema name where your tables will be replicated (e.g., `public`)
- - **Catalog Token**: Authentication token from Step 1
- - **S3 Access Key ID**: Access key from Step 1
- - **S3 Secret Access Key**: Secret key from Step 1
-
-5. Configure **Advanced Settings** (optional):
-
- - **Batch wait time (milliseconds)**: How long to wait for more changes before sending a batch. Default is recommended for optimal performance.
-
-6. Click **Create and start** to begin replication
-
-Your replication pipeline will now start copying data from your database to the analytics bucket in Iceberg format.
-
-##### How it works
-
-Once configured, replication to Analytics Buckets:
-
-1. Captures changes from your Postgres database (INSERT, UPDATE, DELETE, TRUNCATE operations)
-2. Batches changes for optimal performance
-3. Creates Iceberg tables automatically to match your Postgres schema
-4. Streams data to Analytics Buckets
-
-##### How tables are structured
-
-Replicated tables use a changelog structure:
-
-- Tables are created with a `_changelog` suffix in the name (e.g., `users_changelog`)
-- Each table contains a `cdc_operation` column indicating the operation type: `INSERT`, `UPDATE`, `DELETE`, or `TRUNCATE`
-- This append-only format preserves the complete history of all changes
-
-##### Limitations
-
-- **Append-only log**: Currently provides an append-only log format rather than a full table representation
-
-##### Additional resources
-
-- [Analytics Buckets documentation](/docs/guides/storage/analytics/introduction) - Learn more about Analytics Buckets and S3-compatible storage
-- [Realtime Data Sync to Analytics Buckets](/docs/guides/storage/analytics/replication) - Step-by-step guide for replicating to Analytics Buckets
-- [Apache Iceberg](https://iceberg.apache.org/) - Official Iceberg documentation
-
-</TabPanel>
-<TabPanel id="bigquery" label="BigQuery">
+</Admonition>
[BigQuery](https://cloud.google.com/bigquery) is Google's fully managed data warehouse. You can replicate your database tables to BigQuery for analytics and reporting.
@@ -323,14 +219,12 @@ This structure handles table truncations seamlessly while maintaining query comp
##### Limitations
- **Row size**: Limited to 10 MB per row due to BigQuery Storage Write API constraints
+- **Table names**: Source table names cannot start or end with `_` when replicating to BigQuery
##### Additional resources
- [BigQuery documentation](https://cloud.google.com/bigquery/docs) - Official Google BigQuery documentation
-</TabPanel>
-</Tabs>
-
### Step 4: Monitor your pipeline
After creating a destination, the replication pipeline will start and appear in the destinations list. You can monitor the pipeline's status and performance from the Dashboard.
@@ -440,7 +334,7 @@ Replication has the following limitations:
- **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?](/docs/guides/database/replication/replication-faq#can-data-duplicates-occur-during-pipeline-operations) for details
-Destination-specific limitations (such as Iceberg's append-only log format or BigQuery's row size limits) are detailed in each destination tab in [Step 3](#step-3-add-a-destination) above.
+Destination-specific limitations, such as BigQuery's row size limits, are documented in [Step 3](#step-3-add-a-destination) above.
### Future work
diff --git a/apps/docs/content/guides/storage/analytics/creating-analytics-buckets.mdx b/apps/docs/content/guides/storage/analytics/creating-analytics-buckets.mdx
index 8d57ae19ccf..fe4fc155ea2 100644
--- a/apps/docs/content/guides/storage/analytics/creating-analytics-buckets.mdx
+++ b/apps/docs/content/guides/storage/analytics/creating-analytics-buckets.mdx
@@ -11,6 +11,12 @@ This feature is in **Private Alpha**. API stability and backward compatibility a
Analytics buckets use [Apache Iceberg](https://iceberg.apache.org/), an open-table format for efficient management of large analytical datasets. You can interact with analytics buckets using tools such as [PyIceberg](https://py.iceberg.apache.org/), [Apache Spark](https://spark.apache.org/), or any client supporting the [Iceberg REST Catalog API](https://editor-next.swagger.io/?url=https://raw.githubusercontent.com/apache/iceberg/main/open-api/rest-catalog-open-api.yaml).
+<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 [Database Replication](/docs/guides/database/replication/replication-setup) with **BigQuery**. If you want to use Analytics Buckets, bring your own ingestion pipeline.
+
+</Admonition>
+
## Creating an Analytics bucket
You can create an analytics bucket using either the Supabase SDK or the Supabase Dashboard.
@@ -73,5 +79,4 @@ print('Analytics bucket created:', response)
Once you've created your analytics bucket, you can:
- [Connect with Iceberg clients](/docs/guides/storage/analytics/connecting-to-analytics-bucket) like PyIceberg or Apache Spark
-- [Set up real-time replication](/docs/guides/storage/analytics/replication) from your Postgres database
- [Query data with Postgres](/docs/guides/storage/analytics/query-with-postgres) using the Iceberg Foreign Data Wrapper
diff --git a/apps/docs/content/guides/storage/analytics/query-with-postgres.mdx b/apps/docs/content/guides/storage/analytics/query-with-postgres.mdx
index de69594ebde..1abd547eb5a 100644
--- a/apps/docs/content/guides/storage/analytics/query-with-postgres.mdx
+++ b/apps/docs/content/guides/storage/analytics/query-with-postgres.mdx
@@ -3,10 +3,16 @@ title: 'Query with PostgreSQL'
subtitle: 'Query analytics bucket data directly from PostgreSQL using SQL.'
---
-Once your data flows into an analytics bucket—either via the [Replication Pipeline](/docs/guides/storage/analytics/replication) or custom pipelines—you can query it directly from Postgres using standard SQL.
+Once your data flows into an analytics bucket through your own ingestion pipeline, you can query it directly from Postgres using standard SQL.
This is made possible by the [Iceberg Foreign Data Wrapper](/docs/guides/database/extensions/wrappers/iceberg), which creates a bridge between your Postgres database and Iceberg tables.
+<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.
+
+</Admonition>
+
## Setup overview
You have two options to enable querying:
diff --git a/apps/docs/content/guides/storage/analytics/replication.mdx b/apps/docs/content/guides/storage/analytics/replication.mdx
deleted file mode 100644
index 30f26ab52b1..00000000000
--- a/apps/docs/content/guides/storage/analytics/replication.mdx
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: 'Realtime Data Sync to Analytics Buckets'
-subtitle: 'Replicate your PostgreSQL data to analytics buckets in real-time.'
----
-
-<Admonition type="caution" title="This feature is in alpha">
-
-Expect rapid changes, limited features, and possible breaking updates. [Share feedback](https://github.com/orgs/supabase/discussions/40116) as the experience is refined and access is expanded.
-
-</Admonition>
-
-By combining replication powered by [Supabase ETL](https://github.com/supabase/etl) with **Analytics Buckets**, you can build an end-to-end data warehouse solution that automatically syncs changes from your Postgres database to Iceberg tables.
-
-This guide provides a quickstart for replicating to Analytics Buckets. For complete replication configuration including other destinations, see the [Replication Setup Guide](/docs/guides/database/replication/replication-setup).
-
-## How it works
-
-The replication pipeline captures changes (INSERT, UPDATE, DELETE) from your Postgres database in real-time using Postgres logical replication and writes them to your analytics bucket. This allows you to maintain an always-up-to-date data warehouse without impacting your production workloads.
-
-## Setup steps
-
-### Step 1: Create an Analytics bucket
-
-First, create a new analytics bucket to store your replicated data:
-
-1. Navigate to **Storage** in the Supabase Dashboard.
-2. Click **Create Bucket**.
-3. Enter a name (e.g., `my-warehouse`).
-4. Select **Analytics Bucket** as the type.
-5. Click **Create**.
-
-<Image
- alt="Creating a new analytics bucket"
- src="/docs/img/database/replication/replication-iceberg-new-bucket.png"
-
-width={3560}
-height={2146}
-/>
-
-### Step 2: Create a publication
-
-A publication defines which tables and change types will be replicated. Create one using SQL in the Supabase SQL Editor:
-
-```sql
--- Create publication for tables you want to replicate
-CREATE PUBLICATION pub_warehouse
- FOR TABLE users, orders, products;
-```
-
-This publication will track all changes (INSERT, UPDATE, DELETE) for the specified tables. For advanced publication options like column filtering and row predicates, see the [Replication Setup Guide](/docs/guides/database/replication/replication-setup#advanced-publication-options).
-
-### Step 3: Create the replication pipeline
-
-Now set up the pipeline to sync data to your analytics bucket:
-
-1. Navigate to **Database > Replication** in the Supabase Dashboard.
-2. Click **Create Pipeline**.
-3. Select the **Publication** you created in Step 2.
-4. Select your **Analytics Bucket** as the destination.
-5. Configure any additional settings as needed.
-6. Click **Create and Start**.
-
-<Image
- alt="Replication pipeline configuration"
- src="/docs/img/database/replication/replication-iceberg-details.png"
-
-width={3560}
-height={2146}
-/>
-
-## Monitoring your pipeline
-
-Once started, you can monitor the pipeline status directly in the **Database > Replication** section:
-
-- **Status** - Shows if the pipeline is running, paused, or encountered errors
-- **Sync Progress** - View the number of records replicated
-- **Logs** - Check detailed logs for troubleshooting
-
-<Admonition type="note">
-
-Deleted tables are automatically recreated by the pipeline. To permanently delete a table, pause the pipeline first or remove it from the publication before deleting. See the [FAQ](/docs/guides/database/replication/replication-faq#what-happens-if-i-delete-a-table-at-the-destination) for details.
-
-</Admonition>
-
-## Next steps
-
-Once data is flowing to your analytics bucket, you can:
-
-- [Query with SQL via Postgres](/docs/guides/storage/analytics/query-with-postgres)
-- [Connect with PyIceberg](/docs/guides/storage/analytics/examples/pyiceberg)
-- [Analyze with Apache Spark](/docs/guides/storage/analytics/examples/apache-spark)
-
-For detailed replication configuration and advanced topics:
-
-- [Replication Setup Guide](/docs/guides/database/replication/replication-setup) - Complete replication configuration including BigQuery and other destinations
-- [Replication Monitoring Guide](/docs/guides/database/replication/replication-monitoring) - Monitor replication pipeline status and health
-- [Replication FAQ](/docs/guides/database/replication/replication-faq) - Common questions about replication
diff --git a/apps/www/lib/redirects.js b/apps/www/lib/redirects.js
index 1eb66f770e4..c8b408a4923 100644
--- a/apps/www/lib/redirects.js
+++ b/apps/www/lib/redirects.js
@@ -2646,6 +2646,11 @@ module.exports = [
source: '/docs/guides/database/replication/etl-destinations',
destination: '/docs/guides/database/replication/replication-setup',
},
+ {
+ permanent: true,
+ source: '/docs/guides/storage/analytics/replication',
+ destination: '/docs/guides/database/replication/replication-setup',
+ },
{
permanent: true,
source: '/docs/guides/auth/server-side-rendering',