Cloudflare Announces General Availability of Cloudflare Basin Serverless Data Platform

Cloudflare Announces General Availability of Cloudflare Basin Serverless Data Platform Cloudflare has released Cloudflare Basin, formerly the Cloudflare Data Platform, into general availability as a serverless data analytics suite built on Apache Iceberg and R2 Object Storage. Cloudflare Basin leverages Apache Iceberg and R2 Object Storage to offer an open analytics environment with zero egress fees and usage-based pricing. The platform combines three core products: Basin Pipelines for data ingestion, Basin Catalog for table management, and Basin SQL for distributed querying. Basin Pipelines supports ingestion rates up to 3GB/s per stream, while Basin SQL divides queries into smaller tasks distributed across Cloudflare Workers. Open Architecture and Cost Efficiency Basin operates on the open Apache Iceberg table format coupled with R2 Object Storage, decoupling compute from storage and allowing data to be queried by outside engines such as DuckDB, Snowflake, PyIceberg, and Apache Spark. By removing egress fees and applying a serverless, usage-based model, Cloudflare bills users strictly when data is ingested, processed, or queried, eliminating baseline hourly infrastructure charges. Core Components: Pipelines, Catalog, and SQL The platform functions through three primary tools. Basin Pipelines accepts events via HTTP endpoints or Workers bindings, transforms data through SQL queries, and scales up to 3GB/s per stream. Basin Catalog serves as a managed Iceberg REST catalog that performs automatic data and metadata compaction. Basin SQL provides distributed querying across Cloudflare's edge network, utilizing generated table statistics to run complex SQL operations such as joins, common table expressions, window functions, and rollups. General Availability and Backward Compatibility Basin Pipelines, Basin Catalog, and Basin SQL are generally available to deploy together or adopt modularly into existing stacks. Cloudflare confirmed that existing configurations for Cloudflare Pipelines, R2 Data Catalog, and R2 SQL will continue functioning under the newly unified Basin naming.

Cloudflare Basin 正式商用：基于 Apache Iceberg 的无服务器数据平台 Cloudflare 宣布原 Cloudflare Data Platform 正式进入全面商用（GA）阶段，并更名为 Cloudflare Basin。该平台基于 Apache Iceberg 开放表格式与 R2 对象存储构建，提供涵盖摄取、存储和查询的端到端无服务器分析能力。 原 Cloudflare 数据平台正式更名为 Cloudflare Basin 并全面商用。 平台由负责摄取的 Pipelines、元数据管理的 Catalog 和分布式查询引擎 SQL 三大核心产品组成。 依托 R2 实现零出站费用（zero egress fees），并与 PyIceberg、DuckDB、Snowflake 等 Iceberg 兼容生态无缝互通。 采用全无服务器架构与按使用量计费模式，无固定基础设施或按小时运行成本。 三大核心组件：Pipelines、Catalog 与 SQL Basin 由三个产品组成以覆盖分析数据的生命周期。Basin Pipelines 负责数据摄取与预处理，支持通过 HTTP 端点或 Workers 绑定接收事件，按 SQL 查询清洗并交付，当前每条流最高支持 3GB/s 的摄取吞吐；Basin Catalog 是全托管的 Apache Iceberg REST 目录，支持自动合并压缩元数据与数据文件；Basin SQL 作为全球分布式的无服务器查询引擎，无需预配集群，可将查询拆解并在 Workers 网络中分布式执行，且支持复杂连接与窗口函数等操作。 开放标准、零出站费与成本效益 Basin 强调存储与计算分离，用户数据以 Apache Iceberg 格式存储，允许通过 DuckDB、Snowflake、Apache Spark 等多种查询引擎自由访问。得益于 Cloudflare R2 的零出站费用，跨云与跨工具的数据流转不会产生额外流量成本。计费方面，Basin 仅在执行摄取、处理或查询时按量计费，无需承担闲置资源的闲置费用。原有的 Pipelines、R2 Data Catalog 及 R2 SQL 配置将继续保持有效。

During Birthday Week 2025, we announced the [Cloudflare Data Platform](https://blog.cloudflare.com/cloudflare-data-platform/), a suite of products that ingest, store, and query your analytical data. Today, we’re announcing that the platform is generally available, and we’re giving it a new name: **Cloudflare Basin**. Basin is a serverless data analytics platform built on [Apache Iceberg](https://iceberg.apache.org/), the open standard for data lakes, and [R2 Object Storage](https://developers.cloudflare.com/r2/). The Basin family includes: Basin brings an end-to-end analytics platform to the Developer Platform, enabling you to collect data from a variety of sources, such as apps, infrastructure, devices, and other Cloudflare services, then query it to answer analytical questions. We set out to build a data platform last year when we saw two fundamental developments that changed how modern data applications were being built. First, Apache Iceberg emerged as the standard open table format, making data portable across nearly every major query engine. Second, we started seeing developers bring their analytics data to R2 where the lack of egress charges made it practical and cost-efficient to actually access their data from different tools, teams, regions, and cloud providers. So, when we launched Basin in open beta, developers — including our billing and infrastructure teams at Cloudflare — immediately started adopting these services for a variety of use cases including using real-time data to optimize e-commerce sites, long-term storage and reporting of billing metrics, and ingesting and querying telemetry from Cloudflare’s infrastructure to measure and improve utilization and efficiency. *“We moved our entire company's data pipeline to Basin Pipelines, Catalog, and SQL, replacing a complex AWS S3 and Athena setup with a cleaner, serverless architecture that reliably handles all of our event data. -Dax Raad, Co-Founder, Anomaly* Our early adopters taught us a great deal about what it means to run an analytics platform on the edge. We spent the past year improving Basin around three specific areas that hone in on what makes analytics in Developer Platform unique: speed, openness, and cost efficiency. Basin is built for speed — whether it’s about getting started or executing large queries. You can create a Basin Catalog, set up a Pipeline to ingest data, and query it with Basin SQL in seconds. This matters as we see more data applications being built from prompts to coding agents, which would otherwise have to wait and poll for resources or data. As datasets grow, Basin Catalog compacts metadata and data files to reduce I/O and generates statistics for query planning. Basin SQL uses those statistics to split queries into smaller tasks and distribute them across Workers, keeping queries fast and consistent as datasets scale. A large driving force in the development and adoption of Basin is the continued growth we are seeing in the open Apache Iceberg ecosystem. Developers have been rallying around the radical idea that you should own and be in control of your own data — separating the storage layer from the compute layer and allowing you to use the right query engine for the job. With Basin, you can read and write your data using any Iceberg-compatible engine, including PyIceberg, DuckDB, Snowflake, and Apache Spark. 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. “Bobsled is a data product platform that the world's most advanced data teams use to build and distribute AI-ready data to partners, vendors and customers," said Julien Grobbelaar, Head of Platform at Bobsled. "Basin allows us to build data products that can be made accessible in any region of every major data and AI platform, all at production-grade reliability and a fraction of the cost thanks to zero egress fees.” In addition to free egress, our serverless architecture allows us to offer further cost efficiencies to our customers with usage-based pricing. You are only billed when Basin ingests, processes, or queries your data. Developers can build out analytics for hobby projects at little to no cost, while our pricing scales economically for larger enterprise use cases. There are no hourly charges or separate infrastructure costs to worry about. If you are ready to get started, refer to the [Basin tutorial](http://developers.cloudflare.com/basin/get-started/guide/) for a step-by-step guide on how to use Basin Pipelines to deliver events to an Apache Iceberg table managed by Basin Catalog, and query them with Basin SQL. Read on to learn more about Basin and where we are going next. We launched these products last year as the Cloudflare Data Platform, which has served us well for the first year of availability. For our GA launch, we decided we needed a new name that encompasses our ambitions for the platform, links together all the products, and is a bit punchier. A basin is where rivers from many sources come together to a single point. We felt that Basin perfectly captures how the platform is used: Pipelines brings data into Basin Catalog while Basin SQL makes it instantly queryable. A fun fact: roughly 20% of Earth’s land drains into endorheic basins, much like over 20% of the web sits behind Cloudflare’s network. Today, Basin is made up of three products: Pipelines, Catalog, and SQL, covering ingestion, storage, and querying, and will expand over time with more products managing the rest of the analytical data lifecycle. Before you can query your data, your events need to be ingested, structured to a schema, and written to object storage. This is the role of [Basin Pipelines](http://developers.cloudflare.com/basin-pipelines/). It accepts events through HTTP endpoints or Workers bindings, processes them according to a SQL query, and delivers them to Basin Catalog as Apache Iceberg tables or R2 as JSON or Parquet files. Since our beta launch, users have created tens of thousands of Pipelines for a wide variety of use cases. For example, a common pattern we see is using Pipelines to transform Cloudflare HTTP logs before storing them: Doing this work during ingestion can significantly reduce the storage footprint, reduce noise from dynamic data sources, and can help prevent sensitive or unnecessary values from being written. Since the beta, we have greatly expanded the scalability of Pipelines: we now support ingesting up to 3GB/s per stream. We’ve also expanded the feature set and integration with other Cloudflare systems: `wrangler types` generates TypeScript types from a stream's schema, catching missing fields and type mismatches before deployment. Next we plan to expand Pipelines capabilities even further, including: Basin Catalog was the first product we launched in the family last year. Since then, we’ve seen thousands of developers use Basin Catalog for simple use cases such as giving DuckDB a structured way to access analytics data in R2, all the way to developers building complete enterprise data sharing platforms, fully taking advantage of zero egress fees and easy-to-use APIs. [Basin Catalog](http://developers.cloudflare.com/basin-catalog/) is the easiest way to get started with Apache Iceberg. Just run: You instantly get a fully managed Apache Iceberg REST catalog that automatically performs routine maintenance required to keep those tables performant and healthy. When we announced the Data Platform, Basin Catalog had just added automatic compaction. Since then, it has evolved to maintain healthy tables as your data scales: We have some exciting features in the works for Basin Catalog including: [Basin SQL](http://developers.cloudflare.com/basin-sql/) is our serverless, distributed query engine for Apache Iceberg tables stored in Basin Catalog. It’s designed for reading large datasets and automatically scales across Cloudflare's global network. There are no clusters or resources to provision, just a readily available API for you and your agents to immediately start querying your data. At beta launch, Basin SQL was great at filtering and exploring large event and time-series tables. Over the last year, Basin SQL has evolved to support hundreds of functions including: `GROUP BY`, `HAVING`, and schema-discovery commands`CASE` expressions, common table expressions, casting, arithmetic, and `EXPLAIN``DISTINCT`, `UNION`, `INTERSECT`, and `EXCEPT``QUALIFY`, grouping sets, rollups, and cubes Suppose your Pipeline delivers application events into one table and account data into another. You can now join those tables, aggregate activity by customer, rank the results with a window function, and filter the ranking in one query: You can run Basin SQL from Wrangler or the API, or open the built-in editor in the Cloudflare dashboard. The editor provides syntax highlighting and autocomplete, a browser for namespaces and tables, query statistics and plans, and exportable results. It makes the path from a new table to a useful answer a matter of seconds. The team isn’t stopping here and is currently working on: Our future vision is that data infrastructure is completely abstracted away. Storage formats, products, and resources are just implementation details — important ones that help enable the important outcomes — but tend to get in the way. We’re building towards a platform where developers start with questions rather than `CREATE` statements or CLI commands. We’ve laid the foundation for that vision, and now we’re building towards that vision including: We will continue to build with open standards: using open formats and protocols, contributing improvements to the projects we depend on, and making sure your data remains available to the broader ecosystem. Basin Pipelines, Basin Catalog, and Basin SQL are generally available today. You can use them together as an end-to-end platform or adopt the parts that fit your existing architecture. Follow the [getting started tutorial](http://developers.cloudflare.com/basin/get-started/guide/) to ingest events, create an Apache Iceberg table in Basin Catalog, and query it with Basin SQL. Visit the [Basin documentation](http://developers.cloudflare.com/basin/) for product guides, pricing, limits, and integrations. Existing Cloudflare Pipelines, R2 Data Catalog, and R2 SQL configurations will continue to work. We are excited to see what you build. Share your feedback with us in the [Cloudflare Developer Discord](https://discord.com/invite/cloudflaredev).