Cloudflare D1

Cloudflare D1 is SQLite running on Cloudflare’s network. There is no wire protocol and no hostname — every statement goes through the Cloudflare API as an HTTP request authenticated with an API token.

Who it is for

D1 suits Workers applications that want a real relational database close to their compute, without running a database server. It is a good fit for per-tenant or per-application data at modest scale, and a poor fit for anything needing long transactions or heavy write concurrency.

Because the connection fields carry Cloudflare identifiers rather than network coordinates, it is worth being precise about what goes where — that is the single most common reason a first connection fails.

Set up the token and identifiers

1. Account ID — in the Cloudflare dashboard sidebar, or via wrangler whoami. This goes in the username field.
2. Database ID — the UUID shown for the database, NOT its display name. The API addresses databases by id. This goes in the database field.
3. API token — create one scoped to D1 (Account → D1 → Edit). This goes in the password field.

wrangler d1 list        # shows each database’s uuid
wrangler whoami         # shows the account id

Connect from AddisDB

1. New Connection → Cloudflare D1.
2. Put the account ID in the username field and the database UUID in the database field.
3. Paste the D1-scoped API token into the password field.
4. Test, then Save. There is no host or port to enter.

What AddisDB gives you

Queries, the schema tree, exports, saved queries and mock data. Introspection reads sqlite_master and PRAGMA table_info, so the tree carries primary keys, nullability and defaults exactly as it would for a local SQLite file.

A real detail about D1’s API: a failing statement comes back as HTTP 200 with success set to false. AddisDB reads that flag rather than the HTTP status, so a typo in your SQL surfaces as the database’s own error message instead of an empty result set.