Tabular Foundation Models (TFMs) logopeterindia.net
Knowledge Hub

Serverless Data Platforms

Serverless data platforms: Cloudflare Basin, Apache Iceberg, serverless SQL engines and databases, and streaming ingestion.

44 topics•6 categories•Updated November 2026

Cloudflare Basin: An Open, Serverless Data Platform

11 entries

Cloudflare announced on 1 October 2026 that its Cloudflare Data Platform, introduced during Birthday Week 2025, is generally available under a new name, Cloudflare Basin. Cloudflare describes Basin as a serverless data analytics platform built on Apache Iceberg and R2 Object Storage, made of three products. Basin Pipelines (formerly Cloudflare Pipelines) receives events from Workers, HTTP or Cloudflare Logpush, transforms them with SQL, and writes them as Iceberg tables or as JSON or Parquet files; Cloudflare says it now supports ingesting up to 3GB/s per stream. Basin Catalog (formerly R2 Data Catalog) is a managed Iceberg REST catalog that automatically maintains tables through compaction, snapshot expiration, unreferenced-file cleanup and manifest optimization. Basin SQL (formerly R2 SQL) is a serverless, distributed SQL engine for querying Iceberg tables in Basin Catalog, with no clusters to provision, and Cloudflare lists support for joins, window functions, grouping sets and more than 190 functions. Cloudflare says the design rests on speed, openness and cost efficiency: any Iceberg-compatible engine, including PyIceberg, DuckDB, Snowflake and Apache Spark, can read and write the data; R2 has no data egress fees; and pricing is usage-based, billed when data is ingested, processed or queried. The roadmap it lists includes Iceberg V3 support, custom partitioning, schema migrations, stateful stream processing, finer-grained access control and jurisdiction support. These are Cloudflare's own product claims. This page puts Basin in context with other serverless data options. Descriptions are paraphrased from each source and are not rankings.

1. Cloudflare Basin: Pipelines, Catalog and SQL

5 entries

The three products of Cloudflare Basin and their documentation.

2. Open Table Formats and Storage

7 entries

Open formats make data portable across engines and clouds.

3. Serverless SQL Engines and Warehouses

11 entries

Query data without provisioning clusters.

4. Serverless Databases

5 entries

Operational databases that scale with usage.

5. Streaming and Ingestion

5 entries

Getting events into the platform.

Frequently Asked Questions

What is a serverless data platform?

A data platform where you ingest, store and query data without provisioning or managing clusters, and are typically billed by usage. Cloudflare Basin, described in the announcement this page follows, is one example built on Apache Iceberg and R2.

What is Cloudflare Basin?

Cloudflare's name for its generally available serverless data analytics platform, announced on 1 October 2026. It has three products: Basin Pipelines for ingestion, Basin Catalog for a managed Apache Iceberg catalog, and Basin SQL for serverless queries.

How does Basin relate to Cloudflare Pipelines, R2 Data Catalog and R2 SQL?

Cloudflare says these were the earlier names of Basin Pipelines, Basin Catalog and Basin SQL, and that existing configurations will continue to work.

Why does Apache Iceberg matter for serverless data platforms?

It is an open table format, so data can be read and written by multiple engines. Cloudflare says Basin works with Iceberg-compatible engines such as PyIceberg, DuckDB, Snowflake and Apache Spark.

Does a serverless data platform mean no egress fees?

Not by default. Cloudflare says R2 has no data egress fees, which it presents as enabling portability, but other providers price egress and requests differently. Check each provider's pricing.

Are these Cloudflare claims independently verified?

No. Speed, cost and compatibility statements come from Cloudflare's announcement and were not benchmarked here. Test with your own workload before choosing a platform.

How is serverless SQL different from a traditional data warehouse?

There are no clusters or resources to provision, and capacity scales per query or by usage. Trade-offs include less control over performance tuning and different cost models, so compare on your own workload.

How current is this page?

Links and release facts were checked on 1 November 2026. Descriptions follow each source's own pages and are not rankings or guarantees.