Supabase documents a DuckLake destination for Pipelines, still in public alpha

Supabase has published documentation for a DuckLake destination in Supabase Pipelines, its managed service for replicating Postgres tables. The company says Pipelines is "currently in public alpha" and that "features and behavior may change". The page describes how to copy published Postgres tables into DuckLake, an open lakehouse format, so they can be queried as current-state tables.

Supabase's documentation says DuckLake keeps its metadata in a Postgres catalog and its data as Parquet files in object storage. The catalog is not a copy of the table data. Pipelines does not include a query endpoint, so readers must connect DuckDB with its ducklake extension, or another compatible engine, to the same catalog and storage path. Supabase also warns that reading raw Parquet files can miss changes and deleted rows, so queries should go through the catalog.

There are two ways to set up the destination. In the first, Pipelines uses the current project's Postgres database as the catalog and a Storage bucket in the same project, and it creates the connection credentials. Users choose the bucket, and can create a private one from the form, and must name an unused metadata schema that Pipelines then creates. In the second, users supply their own Postgres catalog URL and S3-compatible storage credentials, which Supabase says are stored as secrets and not returned after creation.

The requirements for source tables are specific. Insert-only tables need no primary key or replica identity, while tables with updates or deletes need a published row identity. After an initial sync, Pipelines applies published changes and a list of supported schema changes, including adding, renaming and dropping columns. Column names are lowercased, so names differing only by ASCII case should be avoided. The pool allows one to six concurrent DuckDB connections, with four as the default.

What is confirmed is limited to Supabase's own documentation, which is the only source for this article. We found no independent coverage or hands-on testing, so the performance, reliability and cost of the destination are untested outside the company. The page says users see an estimated cost before creating a pipeline but does not state pricing. Because the service is an alpha, behavior may change.

The practical significance is for teams that want analytical copies of Postgres data in an open format without building their own change-capture pipeline. Supabase tells users to treat the replicated tables and catalog as read-only, since outside writes can conflict with replication and background maintenance.

Revised 16 October 2026: Guth re-read the original sources and rewrote this article. Correction: the earlier version said Pipelines automatically creates the storage bucket for the built-in DuckLake option. The source says users choose a Storage bucket (and can create a private one from the destination form), while Pipelines creates the metadata schema, its tables and the connection credentials. The earlier version remains available as revision 1.