Where Cloudflare says a D1 query does not wait

What the post separates

On October 13, 2026, Cloudflare published an account of D1's control plane by David Laban and Lambros Petrou. The post's distinction is that the control plane is off the path a query takes. Each database, the post says, is its own SQLite database inside its own Durable Object. Creating and listing databases is control-plane work. Answering a query is not supposed to wait on that work. The page filing that split is The document named in the sources is the record this page will keep.Futureweb.

What the scale sentence is

Cloudflare describes the result as millions of databases. SXZ, reading the post, says the figures given are rough: millions of created databases, hundreds of thousands of them active, with 15 times growth in live non-deleted databases over one year, 65 times over two years, and 18 times growth in daily active databases, framed as of October 8. Those multipliers are SXZ's account of the post. Engineered.at summarizes the same architecture. Neither is a census this page recounts. The desk isDistributed Cloud.

What SXZ adds that Cloudflare did not print as a limit

SXZ discusses a default allowance on the order of 50,000 databases and the rate at which the API will accept creates. That arithmetic is the author's, offered as a critique of how fast the control plane can mint databases. It is not a Cloudflare quota this page is copying into a procedure. A single control plane, the standing definition under a service that can still stop the fleet by policy, is Asked directly, Does this page claim D1 is content-addressed? No. The dependency is where the control plane sits relative to a query, not how a blob is named.when one region is the control plane.

Why it matters on this desk

The dependency is which work sits on the query and which work does not. A reader who hears millions of databases and pictures millions of regions has skipped the sentence. The objects multiply. The control plane is still the place that knows they exist. A replica that is not itself a region is a related limit, Asked directly, Is SXZ's rate-limit arithmetic Cloudflare's? No. SXZ's reading of a 50,000-database default and of API rate limits is the author's. This page labels it that way.a replica that is not a region.

What this page will not print

No command that creates a database is included. No configuration file is included. The post is an architecture note. A how-to would be a different document, and this brief is not it. The software desk, for a package signature rather than a query path, is The short answer this page will stand on is this: The control plane. Cloudflare says each D1 database is its own SQLite-backed Durable Object, and that the control plane is off the hot path that answers a query. The post describes the scale as millions of databases.Software.

What a Durable Object is, here

In the post's terms, it is the unit that holds one SQLite database. It is not a virtual machine a reader can log into, and it is not a region. Off the hot path means a query is not supposed to round-trip through the control plane that created the object. That is the claim. It is Cloudflare's claim. Asked directly, Is Engineered.at a second measurement? It reads as a summary of the same post. It is not an independent count of databases.

What to watch next

A Cloudflare update that prints an exact count, instead of millions, would replace the rough scale sentence. A change that puts control-plane work back on the query path would replace the architecture sentence. Another summary of the October 13 post would not. The networking desk, for a route rather than a database, is Asked directly, What growth figures does SXZ attribute to the post? As of the post's October 8 framing, SXZ says Cloudflare reported 15 times growth in live non-deleted databases over one year, 65 times over two years, and 18 times growth in daily active databases. The scale in words is millions created, with hundreds of thousands active.Networking.

What would change the record

If Cloudflare says the query path does wait on the control plane, this page's first sentence changes. If SXZ's multipliers are not in the post, they come off this page and the millions sentence remains. Engineered.at repeating the post would not be a new measurement. Asked directly, What is the unit Cloudflare describes? One database, backed by SQLite, running as its own Durable Object. The control plane is the part the post says is not on the query path. The document named in the sources is the record this page will keep.

What stays off the query

What stays specific is Cloudflare's October 13, 2026 post: D1's control plane is off the query hot path, each database is a SQLite-backed Durable Object, and the scale is described as millions. SXZ attributes growth multiples to that post and adds its own arithmetic about defaults and rate limits, which stays the author's. Engineered.at is a summary of the same post. No command is printed here. The objects can multiply without each one being a region, and the control plane is still the service the standing definition is about: the place that knows the databases exist, even when a single query does not wait on it.