Knowledge Hub
Supabasevs
Cloudflare D1
Timings
Time to First Byte (TTFB) and Load time across different locations. Lower is better.
| Location |  DB Query Time Load |  DB Query Time Load | ||
|---|---|---|---|---|
 us-west-1 | N/A | N/A | ||
| us-east-1 | N/A | N/A | ||
 ca-central-1 | N/A | N/A | ||
 sa-east-1 | N/A | N/A | ||
 eu-central-1 | N/A | N/A | ||
 eu-west-2 | N/A | N/A | ||
 eu-west-3 | N/A | N/A | ||
 eu-north-1 | N/A | N/A | ||
 eu-south-1 | N/A | N/A | ||
 af-south-1 | N/A | N/A | ||
 ap-southeast-1 | N/A | N/A | ||
 ap-northeast-1 | N/A | N/A | ||
 ap-east-1 | N/A | N/A | ||
 ap-southeast-2 | N/A | N/A | ||
 ap-northeast-2 | N/A | N/A | ||
Serverless Database features
Compare the features of the Serverless Database to help you choose the right one for your needs.
| Feature | | | |
|---|---|---|---|
Infrastructure, Underlying technology Cloud Infrastructure, database system and underlying egine | Supabase infrastructure, PostgreSQL, S3 compatible storage object | Cloudflare infrastructure, SQLite | |
Serverless Support Serverless and Edge computing support | |||
API | Deno Edge Function | Cloudflare Workers runtime API interfaces, D1 Client API | |
Edge Functions Serverless functions that run closer to the user, reducing latency and improving performance. | Supabase infrastructure | Cloudflare Workers runtime | |
Developer Experience | |||
Database type | OLTP | OLTP | |
Data model Databases store data in models, such as Relational, Columnar or Document based | Relational, SQL | Relational, SQL | |
CLI Command Line Interface tools that allow developers to perform tasks and manage the tool via the command line. | supabase | Cloudflare Workers runtime | |
Languages, APIs The languages supporting the database and API interface for inter-process communication | TypeScript, JavaScript, supabase-js SDK, Flutter, React Native, React | TypeScript, JavaScript inside Cloudflare worker functions | |
Query language Supported query language such as SQL, MQL, PartiQL, | SQL, PostgreSQL | SQL | |
ACID compliant ACID is a set of properties of database transactions intended to guarantee data validity despite errors, power failures, and other mishaps | ACID compliant | ACID compliant | |
Self-hosting Support for self-hosted Database instance | Docker support | Doesn't have support, Only for local development | |
Backups | Daily basis (Included in Free tier), PITR for paid users | Backups run every hour automatically. Stores backups of your database in R2 | |
Security & Compliance Offerings | |||
SOC2 Service Organization Control 2 compliance for managing customer data. | |||
Multi-factor authentication Support of the cloud-histed database for multi-factor authentication | |||
Encryption Cryptographic security at rest and on transportation level | AES 256 Encryption, TLS v1.2 | N/A | |
SSO | N/A | ||
Monitoring and analytics | |||
Log retention Query log retention usually keeps lofs of operations for debugging and replication purposes | By default disabled, can be enabled with pgAudit extension | N/A | |
Statistics Tools and APIs for analysing and monitoring of Database performance | Web dashboard, provides Prometheus-compatible metrics endpoints to gather health insights | N/A | |
Scalability | |||
Replication and Partitioning | read replicas in early preview | Distributed across Cloudflare Edge network | |