# Database

Quickback treats D1 and Neon/Postgres as first-class database targets. Choose
from the application's data model and query profile; the same Quickback
security definitions compile to either provider.

## Providers

| Provider | Best for | Why choose it |
|----------|----------|---------------|
| [Cloudflare D1](/platform/database/d1) | CRUD-heavy SaaS, content catalogs, internal tools, straightforward workflows | Managed SQLite, no connection strings or pooling, Cloudflare-native operations, FTS5 and JSON functions when needed |
| [Neon](/platform/database/neon) | Data-intensive products and apps designed around PostgreSQL | Native JSONB/arrays, `tsvector` + GIN, PostGIS/extensions, database RLS, advanced indexing and interactive transactions through Hyperdrive |

## Quick decision

- Pick **D1** when simple operations and a low-ops Cloudflare deployment are the
  priority.
- Pick **Neon/Postgres** up front when advanced search, rich data types,
  sustained concurrent writes, Postgres extensions, or database-level RLS are
  product requirements.
- Hyperdrive is optional: Neon HTTP is the lightweight default on Cloudflare;
  Hyperdrive is the full-featured lane for interactive transactions.

## Getting Started

- **[D1 Setup](/platform/database/d1)** — Bindings, wrangler config, migrations
- **[Using D1](/platform/database/using-d1)** — Drizzle queries, dual-DB mode, schema patterns
- **[Neon](/platform/database/neon)** — Serverless Postgres setup and usage