Cloudflare renames its data platform Basin and makes it generally available

Basin is what Cloudflare calls a serverless data analytics platform. In plain words, it collects data, stores it, and lets you ask questions about it, without you running any servers.

Think of the data a company generates every second: clicks, purchases, logs, sensor readings. Basin is meant to gather all of that in one place so a team can answer questions like "which customers were most active last week?"

Cloudflare says it set out to build Basin after spotting two shifts. Apache Iceberg became the standard open table format, so data could move between nearly every major query engine. And developers started storing analytics data in R2, where the lack of egress charges made it practical to reach that data from different tools and clouds.

Cloudflare first announced it as the Cloudflare Data Platform during its Birthday Week in 2025. Now it's out of beta, with three products under one name:

• Basin Pipelines (formerly Cloudflare Pipelines): takes in events, cleans them up with SQL, and writes them to storage.
• Basin Catalog (formerly R2 Data Catalog): keeps track of the tables and maintains them so they stay fast and cheap.
• Basin SQL (formerly R2 SQL): the engine that runs queries over those tables.

Cloudflare says it wanted a name that ties the products together and is "a bit punchier." A basin is where rivers from many sources meet at one point. Pipelines brings data in, Catalog stores it, and SQL makes it queryable.

The company adds a fun fact: roughly 20% of Earth's land drains into basins with no outlet to the sea, much like over 20% of the web sits behind Cloudflare's network.

Not everyone loves it. The Register called the new branding "bland" and noted that it doesn't match Cloudflare's more literal product names, like Workers and Sandboxes.

Basin is built on Apache Iceberg, an open standard for storing big tables of data as files, plus Cloudflare's own R2 storage.

Why that matters: your data isn't locked to Cloudflare's tools. Cloudflare says you can read and write Basin data with any Iceberg-compatible engine, including PyIceberg, DuckDB, Snowflake and Apache Spark. The Register adds StarRocks and Trino to that list.

It's like keeping your photos in a standard JPEG format instead of a format only one app can open. You can switch apps without losing anything.

Cloudflare's CTO, Dane Knecht, put it this way, according to The Register: "no clusters to manage, no unnecessary data movement, and open standards that keep customers in control of their data."

Pricing is usage-based. Cloudflare says you're billed only when Basin ingests, processes or queries your data. There are no hourly charges or separate infrastructure costs.

The other big selling point is egress, the fees cloud providers charge when you move data out. Cloudflare says querying data from other clouds, platforms or regions carries no transfer fees. The Register notes that rivals Amazon S3, Google Cloud Storage and Azure Blob Storage do charge egress fees.

The catch: The Register points out that "no fees" has fine print. Cloudflare's own docs say reading directly from R2 is free, but other metered services connected to an R2 bucket may charge. And when Basin Pipelines loads streaming data into storage, Cloudflare charges for that delivery after an included allowance. Cloudflare labels this pricing line "Sinks (egress)."

Cloudflare says it spent the past year working on speed, openness and cost. Some highlights from its announcement:

• Bigger pipelines: ingestion now goes up to 3GB/s per stream, and users have created tens of thousands of Pipelines since the beta.
• Easier setup: one command, npx wrangler basin catalog create, gives you a fully managed Iceberg catalog.
• Cleaner tables: Catalog now handles compaction policies per table, removes old snapshots and cleans up unused files automatically.
• Richer SQL: Basin SQL now supports more than 190 functions, plus joins, subqueries and window functions.
• Better visibility: the dashboard shows dropped events and why they failed, like missing fields or type mismatches.
• Cloudflare logs built in: Logpush can now send Cloudflare's own logs through Pipelines, cleaned up with SQL and stored as Parquet files or Iceberg tables.
• Setup as code: the whole path, from catalog to stream to the SQL that connects them, can be defined in Terraform.
• A query editor: Basin SQL has a built-in editor in the Cloudflare dashboard, with autocomplete, a table browser, query plans and exportable results.

Cloudflare says thousands of developers already use Basin Catalog. Uses range from simply giving DuckDB a tidy way to read analytics data in R2, all the way to full enterprise data-sharing platforms.

Cloudflare also says speed matters more now that apps are being built from prompts by coding agents, which would otherwise have to wait for resources to spin up.

In real life A small online store wants to know which products people view but don't buy. With Basin, its developer sends click events through a Pipeline, stores them as tables, and runs one SQL query to rank the products, without renting a database server.

Cloudflare quotes two early customers.

Dax Raad, co-founder of Anomaly, says his company "moved our entire company's data pipeline" to Basin, replacing "a complex AWS S3 and Athena setup with a cleaner, serverless architecture."

Julien Grobbelaar, head of platform at Bobsled, says Basin lets the company build data products accessible "in any region of every major data and AI platform," at "a fraction of the cost thanks to zero egress fees."

Cloudflare also uses Basin itself. Its billing and infrastructure teams run it for things like long-term billing reports and measuring how efficiently Cloudflare's own servers are used.

Cloudflare lists plenty of planned features. Among them:

• Pipelines: custom partitioning, schema changes, and streaming joins and aggregations.
• Catalog: smarter sorting for faster queries, finer access controls, and support for data sovereignty rules.
• SQL: full table-definition commands and support for the newer Iceberg V3 spec.

The big picture: Cloudflare says its long-term goal is for data infrastructure to disappear from view. Developers would start with questions, not setup commands.

• If you're a developer: you can now use Basin in production. Try the one-command catalog setup and query your data with tools you already know.
• If you're comparing cloud costs: no egress fees on R2 reads can save money, but check the Pipelines delivery charges in Cloudflare's pricing.
• If you worry about lock-in: Basin's use of Apache Iceberg means you can move your data to other engines later.
• If you don't build software: this changes little day to day, though it may shape the apps you use behind the scenes.