Cloudflare is turning its infrastructure toward a new target: the data platform. Basin, a serverless system built on Apache Iceberg and Cloudflare’s R2 object storage, became generally available at the beginning of October 2026 with a promise built around open tables, usage-based pricing, and zero egress fees.
That combination gives Basin a clear mission. It aims to help developers and teams ingest, store, and query data without paying for idle compute or moving data out of R2. Could an open, serverless stack change how smaller teams approach analytics? Cloudflare is betting that lower costs and fewer infrastructure decisions will bring more users into the data platform market.
A Serverless Data Stack With Storage at the Center
Basin connects several parts of the data workflow into one platform. Pipelines handles ingestion, Catalog manages Iceberg tables, and SQL provides querying. R2 serves as the storage layer, while Apache Iceberg gives customers an open table format that existing tools can read.
For teams without an existing warehouse, Basin offers a complete path from incoming data to useful answers. Developers can ingest data with Pipelines, manage Iceberg tables with Catalog, and query those tables with SQL. The serverless design removes the need to provision or manage resources before work begins.
Meagan Gamache, Director of Product Management of Developer Platforms at Cloudflare, describes the architecture in direct terms: “Basin’s architecture is what allows it to be economical.” She explains that developers and agents can move from getting started to getting answers from their data in seconds, without provisioning or managing resources.
The platform’s economics also depend on Cloudflare’s globally distributed network and infrastructure. Gamache says, “The combination of our serverless architecture, global infrastructure, and zero egress fees allows us to provide developers with a low-cost, purely usage-based billing model without any hourly or idle compute costs.”
Pricing Built Around Usage, Not Idle Capacity
Basin’s pricing separates the platform into usage-based services instead of hourly warehouse fees. Pipelines includes free ingress and 50GB free for transforms and sinks. After that free allowance, SQL costs $0.04 per GB, while sink egress costs $0.03-0.06 per GB.
Basin SQL costs $2.50 per TB of compressed data scanned after a 10GB free tier. Data stored in R2 carries zero egress fees from R2, and Basin also connects to Cloudflare’s developer platform, which includes free usage.
- Pipelines includes free ingress.
- Transforms and sinks include 50GB free.
- SQL costs $0.04/GB after the applicable free usage.
- Sink egress costs $0.03-0.06/GB.
- Basin SQL costs $2.50/TB of compressed data scanned after a 10GB free tier.
- R2 provides zero egress fees.
Those price points create room for hobbyists and smaller teams to test data workflows without committing to an hourly warehouse. Gamache says, “This allows hobbyists and smaller teams to get started and operate at little-to-no cost.” The model also links spending to actual ingestion and query activity, rather than leaving customers to pay for capacity that sits unused.
That approach puts the cost of movement at the center of the pitch. Teams can write open Iceberg tables to R2 and query data without egress fees from R2, keeping storage and access within the same platform.
Basin Does Not Need to Replace Existing Engines
Cloudflare’s position is that Basin does not need to replace existing engines to be useful. Gamache describes it as both an end-to-end platform and an open infrastructure layer for customers who already use other tools.
Teams using Snowflake or Spark can treat Basin as a storage and ingestion layer. Basin writes open Iceberg tables to R2, and those tables remain readable by Snowflake or Spark without a copy or egress fees. That gives existing data stacks a way to connect with Basin instead of forcing a full migration.
This interoperability is central to Cloudflare’s view of open data systems. Gamache says, “Our view is that open wins over time because it gives customers more choice, more portability, and more control over their data, rather than forcing everything into one closed system.”
The same idea shapes Cloudflare’s broader internet vision: “Rather, we see value when the Internet is more open, interoperable, and resilient.” Basin carries that position into data infrastructure by combining open Iceberg tables, R2 storage, serverless services, and usage-based billing.
Basin became generally available at the beginning of October 2026, bringing that model into reach for teams that want a complete data stack and for customers that already rely on Snowflake or Spark. Its next test is clear: whether zero egress fees, open storage, and serverless pricing can turn a data platform into infrastructure that more teams can use without carrying the cost of idle capacity.
