Skip to content

SYSTEM Cited by 1 source

Basin (Cloudflare Data Platform)

Basin is Cloudflare's serverless analytics data platform — the GA (2026-10-01) name for what launched at Birthday Week 2025 as the Cloudflare Data Platform. It is built on Apache Iceberg (the open table format standard) and R2 Object Storage, and 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." (Source: sources/2026-10-01-cloudflare-introducing-cloudflare-basin-an-open-serverless-data-platform)

The name is a watershed metaphor: "A basin is where rivers from many sources come together to a single point." Pipelines brings data into Basin Catalog; Basin SQL makes it instantly queryable.

The three products

Basin covers ingestion, storage, and querying, and "will expand over time with more products managing the rest of the analytical data lifecycle."

  • Basin Pipelines (formerly Cloudflare Pipelines) — receives events from Workers, HTTP, or Cloudflare Logpush; transforms them with SQL; writes them as Apache Iceberg tables or files in R2. The ingestion layer.
  • Basin Catalog (formerly R2 Data Catalog) — manages Iceberg metadata and "automatically maintains tables to keep them fast and cost-efficient." The storage / catalog layer.
  • Basin SQL (formerly R2 SQL) — a serverless, distributed SQL engine for querying Apache Iceberg tables directly on Cloudflare. The query layer.

Why Basin exists (the two 2024 shifts)

Cloudflare frames the whole platform as a response to two developments:

  1. Apache Iceberg became the standard open table format, making data "portable across nearly every major query engine" (concepts/open-table-format).
  2. Developers started bringing 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" (concepts/egress-cost).

The three design axes (year-of-beta investment)

  • Speed — "whether it's about getting started or executing large queries." You can create a Basin Catalog, set up a Pipeline, and query with Basin SQL "in seconds" — which matters as more data applications are built from prompts/coding agents that "would otherwise have to wait and poll for resources or data." As datasets grow, Basin Catalog compacts metadata + data files and generates statistics for query planning; Basin SQL uses those statistics to split queries into smaller tasks across Workers (concepts/scatter-gather-query).
  • Openness — "separating the storage layer from the compute layer and allowing you to use the right query engine for the job." Read/write with any Iceberg-compatible engine: PyIceberg, DuckDB, Snowflake, Apache Spark. "That kind of data portability is only possible with free egress" (concepts/compute-storage-separation).
  • Cost efficiency — serverless + usage-based pricing: "You are only billed when Basin ingests, processes, or queries your data." No hourly charges, no separate infrastructure cost; hobby projects run at little to no cost, pricing scales for enterprise (concepts/serverless-compute).

Relationship to the earlier "Town Lake" and K2

  • Town Lake is Cloudflare's internal unified data platform (the lakehouse the billing/infra teams query via Trino); it consumes the same substrate (R2 + managed Iceberg). Basin is the customer-facing productized version of that same thesis — Cloudflare's own billing + infrastructure teams were among the first beta adopters.
  • K2 (the serverless event-streaming primitive) was "initially the ingestion layer for Basin Pipelines" — the durable log that buffers events before Pipelines pulls them.

Caveats

  • GA/rebrand announcement — no independent benchmarks; only the 3 GB/s per-stream ingest figure and the 190+-function count are concrete.
  • "Existing Cloudflare Pipelines, R2 Data Catalog, and R2 SQL configurations will continue to work" — the rename is additive.
  • The "start with questions rather than CREATE statements" fully- abstracted vision is a stated north star, not a shipped capability.

Seen in

Last updated · 766 distilled / 2,225 read