Verify before you commit
Use this page to sanity-check Cloudflare D1 quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.
Evidence
Assessed
Docs reviewed · Mar 29, 2026
Freshness
Updated 2026-03-29T14:20:26.607+00:00
Mar 29, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 8.4 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 8.5 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 8.4 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
Docs-backed Built from public docs and product materials.
Test-backed Backed by guided testing or evaluator-run checks.
Runtime-verified Verified from authenticated runtime evidence.
Cloudflare D1 is a serverless SQLite-compatible relational database for Cloudflare Workers. Access via env.DB binding inside Worker code — no connection string, no connection pool management. HTTP REST API for external access. Drizzle ORM and Prisma adapter support for schema management. Wrangler CLI for migrations and seeding. Confidence is docs-derived.
Workers binding: env.DB.prepare(sql).bind(...).run()/.all()/.first()/.raw() for typed results; batch API: env.DB.batch([stmt1, stmt2]) for atomic multi-statement execution; HTTP REST API: POST /client/v4/accounts/{id}/d1/database/{db_id}/query for external queries; Wrangler CLI: wrangler d1 execute for migrations; D1 Sessions API for consistent reads across replicas.
Workers bindings require only the D1 database name in wrangler.toml — no API key in application code; HTTP REST API uses Cloudflare API token with d1:read/d1:write permissions; account-level isolation; D1 databases are private to the account; no row-level security (access control enforced at Worker layer); Wrangler uses the authenticated user's Cloudflare token.
SQLite-compatible dialect supports standard SQL DML/DDL; ACID transactions via env.DB.batch() for atomic multi-statement execution; point-in-time restore (PITR) via Time Travel for recovery; D1 Sessions ensure sequential consistency for read-your-own-writes across Worker instances; structured error responses with SQLite error codes; size limits per database per plan.
Documentation covers Workers binding quickstart, REST API reference, Wrangler CLI migration guide, Drizzle and Prisma integration guides, D1 Sessions consistency model, and pricing/limits page. Tight integration with Cloudflare Workers ecosystem. Confidence is docs-derived.
Trust shortcuts
This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.
Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.
Overall tier
8.4 / 10.0
No alternatives captured yet.