Cloudflare Basin Serverless Analytics Reaches General Availability
Nov 10, 2026, 9:15 PM UTC
•Niklas Berg
•3min read
Cloudflare has moved Basin, its serverless analytics platform that uses Apache Iceberg and R2 Object Storage, to general availability. The service combines ingestion, SQL transformation, table management, and distributed querying, with no data egress fees.
Cloudflare announced general availability of Basin, a serverless analytics platform that uses Apache Iceberg and R2 Object Storage. Basin combines data ingestion, SQL-based transformation, managed table maintenance, and distributed SQL queries so developers can analyze large datasets without managing server clusters. The platform carries no data egress fees.
Basin launched in preview as Cloudflare Data Platform more than a year ago. The general availability release renames that product and packages three services under one name.
What Basin includes
Basin Pipelines, renamed from Cloudflare Pipelines, ingests events from Cloudflare Workers, HTTP endpoints, and Logpush. It applies SQL transformations and writes data to Apache Iceberg tables or R2. Basin Catalog manages Iceberg metadata and automates table maintenance. Basin SQL provides a serverless, distributed SQL engine for querying Iceberg tables.
Why open formats matter
The design centers on open formats and portability. Developers can read and write data with any Iceberg-compatible engine, including PyIceberg, DuckDB, Snowflake, and Apache Spark. Marc Selwan, senior product manager at Cloudflare, and Micah Wylde, principal engineer at Cloudflare, tied that portability to the absence of egress charges: “That kind of data portability is only possible with free egress, which allows developers to access their data in Cloudflare from the wide variety of tools in the ecosystem, regardless of region or cloud.” They also explained the name: a basin is where rivers from many sources come together at a single point, and Pipelines brings data into Basin Catalog while Basin SQL makes it queryable.
Basin runs ingestion, preparation, and queries on Cloudflare’s global network. That model targets teams whose data does not justify dedicated infrastructure and exceeds spreadsheet scale. It removes much of the operational work of building and maintaining analytics pipelines, including moving data between services.
Where Basin fits
Basin serves teams that need analytics without a full warehouse stack. Ramin Muradov, lead data analyst at PashaPay, said, “I don’t think it will knock Snowflake off its spot, at least not anytime soon.” Cloudflare positions Basin for a large market layer between spreadsheet-scale data and dedicated warehouse infrastructure. Buyers should compare it with full-featured warehouses when they need complex governance, mature BI ecosystems, or heavy concurrent workloads.
AWS and Google also target unified analytics. AWS acquired DuckLabs and integrated DuckDB into Aurora PostgreSQL, aiming to simplify analytics across transactional and object storage data. Google has repositioned BigQuery as a single, unified AI-ready data platform. Basin’s approach differs: open Iceberg tables on R2, global edge execution, and no egress fees.
What changed since preview
Since preview, Basin has increased ingestion capacity to 3 GB/s per stream, expanded SQL capabilities, improved Iceberg table maintenance, and added Logpush integration and Terraform support. Planned features include real-time processing, support for the latest Iceberg specification, adaptive table maintenance, and additional controls for data sovereignty and access management. Cloudflare has not committed release dates for those features.
How to get started
Cloudflare’s Basin tutorial shows how to ingest events with Basin Pipelines, store them in Iceberg tables managed by Basin Catalog, and query them with Basin SQL. Teams can start there, then connect DuckDB, Snowflake, Spark, or PyIceberg to the same tables.
ble, by Renato Losio, InfoQ, Nov 10, 2026
