SPACE 002 / DATABASES & MANAGED STORAGE

Where does your data live?

Relational, document, and vector systems. Compare the engine, the service, and the work you still own.

10targets · 17 dimensions
Ask with your agent ↗

10 matching targets. Models overlap; JSON fields alone do not make a document database. Source access applies to this target, not every component of its hosted service.

Engine / Self-managed

PostgreSQL

RelationalOpen source

Relational SQL engine with JSON types and extensibility.

Operating boundary

Operator manages deployment, backups and upgrades. This target excludes extensions.

Engine / Embedded

SQLite

RelationalOpen source

SQL storage embedded in the application process.

Operating boundary

Application owns the database file, lifecycle and backup procedure; no separate database server.

Engine / Self-managed

MongoDB Community

DocumentSource available

Document engine with transactions, replication and sharding.

Operating boundary

Operator manages the deployment. This target does not include an Atlas service or configured vector-search component.

Composition / Self-managed

PostgreSQL + pgvector

RelationalVectorOpen source

Vector retrieval alongside relational application data.

Operating boundary

PostgreSQL plus an installed and enabled pgvector extension; operator manages both.

Engine / Self-managed

Qdrant

VectorOpen source

Vector search engine with structured payload filtering.

Operating boundary

Self-managed server deployment; Qdrant Cloud and Edge are outside this target.

Managed service / Cloud DBaaS

Cloudflare D1

RelationalNot established

Managed SQLite-compatible SQL with a Workers and HTTP interface.

Operating boundary

Database is a managed service separate from Worker application compute; do not assume arbitrary SQLite extensions.

Composition / Cloud runtime

Durable Objects + SQLite

RelationalNot established

Per-object SQL storage colocated with application logic.

Operating boundary

Each object owns private storage. Application implements Worker routing and cross-object coordination.

Managed service / Cloud DBaaS

Neon Postgres

RelationalVectorNot established

Managed Postgres with branching and optional pgvector.

Operating boundary

Neon hosted Postgres; vector claims require enabling pgvector per database. Other backend services are excluded.

Managed service / Cloud DBaaS

MongoDB Atlas

DocumentVectorNot established

Managed document database with a configurable vector-search service.

Operating boundary

Atlas cluster plus configured search indexes; region, cluster type and search resources must be specified.

Managed service / Cloud DBaaS

Pinecone

VectorNot established

Hosted vector retrieval with metadata and namespace organization.

Operating boundary

Hosted index and namespace configuration; attached metadata is not classified as a general document database.

Public sources checked 14 September 2026. Documentation research only; no database workloads or independent reproductions have been executed.