D1 opens its doors: Cloudflare’s serverless database enters alpha

Cloudflare has made its D1 database available to everyone as an open alpha. Announced two years ago as part of the company’s push into serverless infrastructure, D1 aims to deliver a relational database that requires none of the usual operational overhead—no provisioning, no patching, no capacity planning. Today, developers can register a database through the Cloudflare dashboard, start issuing SQL within minutes, and wire that database directly into a Worker or Pages Function.

Cloudflare is being explicit that D1 is not production-ready at this stage. The open alpha term is deliberate: it signals that core components for replication and transactional JavaScript support are still under active development and testing. The point is to let developers break things early — with hobby apps and side projects — and tell the team what they need before a more polished public beta is shipped.

What’s live in the alpha

Despite the early status, there is a practical surface area to try out. Three entry points are available for interacting with D1:

  • Dashboard UI: Create and manage databases visually. Any changes made in the interface are reflected in attached Workers immediately; no redeploy step is necessary.
  • Wrangler CLI: Run SQL from the terminal, bootstrap a fresh database from an existing .sql file, or version schema changes with migrations stored in a migrations folder.
  • Worker and Pages bindings: Attach a D1 instance to a project through wrangler.toml or the Pages dashboard, then execute queries directly in application code via the binding API.

Community tooling arrives early

Even before general availability, D1 has attracted a small ecosystem of community-written libraries. Cloudflare singled out four projects that extend the developer experience around the new database:

d1-orm is a JavaScript ORM from a Discord Community Champion targeting a strictly typed workflow. It sits on top of D1’s HTTP API and provides a model-oriented way to work with the database without abandoning the type system.

workers-qb takes a different stance: zero dependencies, no ORM semantics, just a lightweight query builder with a consistent interface that still exposes raw SQL when you need it.

d1-console removes the need to repeatedly fire off wrangler d1 execute. It’s a dedicated non-interactive terminal experience with multi-line query support, command history, and formatted table output. Cloudflare says it plans to offer a native D1 console eventually.

Kysely adapter: For developers attached to a typed SQL query builder, there’s an adapter that lets Kysely talk to D1 over its natively supported interface, preserving autocompletion and compile-time correctness.

Current limitations

The alpha intentionally puts some pieces on hold while they’re stress-tested behind the scenes. The most significant constraints right now are architectural:

  • Fixed location: each D1 database is single-instance and resides in the region baked in at creation time. It won’t migrate based on traffic patterns, so Workers in far-flung regions will incur network latency to reach it.
  • Queued under load: sustained high concurrency will queue read and write queries rather than spinning up replicas. Cloudflare explicitly warns that throughput figures from the alpha period won’t represent the finished product’s characteristics.
  • Hitches during backups: running backups temporarily block access to the database; requests made in that window queue until the snapshot finishes.

A more granular, changeable rundown of these caveats will be kept in the D1 alpha limitations documentation.

Where feedback goes

Feedback channels are broadly open: the #d1-open-alpha Discord channel for live discussion with other alpha users and the team, and the D1 category in the official Cloudflare community forums for concrete bug reports and feature proposals — outlandish ideas welcome. The idea is that every issue filed now shapes the public beta roadmap, so Cloudflare wants to get as diverse a developer base as possible poking at the early product rather than waiting until it’s polish at the edges.

First steps

The quickest path into D1 right now runs through the official documentation, or the example path: clone the D1 Northwind demo, which walks through building and deploying a sample Electron business application, and gives newcomers a ready-derived tour of the dashboard, migrations, the SQL execution flow, and the binding side of the service.