Cloudflare made Basin generally available on October 1, 2026. The change brings the former Cloudflare Data Platform under one name and organizes data ingestion, table management and SQL querying as a connected product family. Source
What changes for existing users
Cloudflare Pipelines is now Basin Pipelines, R2 Data Catalog is now Basin Catalog, and R2 SQL is now Basin SQL. Cloudflare says existing resources and configurations will continue to work. The former product names and related interfaces will be deprecated over time, so new documentation and commands should be located under the Basin names. The announcement does not give a specific deprecation deadline. Source
That means an existing pipeline, catalog or SQL setup does not need to be rebuilt immediately on account of the rename. Teams should still check which names their automation scripts and operating documents use when those files are next revised. This is a distinction between compatibility for current setups and the naming that Cloudflare will use going forward, not a claim that compatibility ends at once. Source
The role of each component
Basin Pipelines receives events from Workers, HTTP endpoints and Cloudflare Logpush, transforms them with SQL, and sends them to Iceberg tables or files on R2. Basin Catalog manages the metadata and maintenance of Iceberg tables. Basin SQL is a distributed engine for querying large tables in the catalog without operating query servers directly. The central change is that collection, table management and analysis now sit in one Basin product family instead of being discovered as three separately named products. Source
How a new project starts
Cloudflare points to npx wrangler basin pipelines setup as the command for beginning an end-to-end data pipeline. It uses the new Basin command path. Existing users can keep their current resources while matching old names to the new documentation; new users can read the workflow as ingestion in Pipelines, table management in Catalog and querying in SQL. Source