Documentation / providers

Choose the plane before the provider.

Providers are deliberately split into metadata and immutable blocks. These pages describe what the repository currently implements, how to inspect the backing data, how each schema/keyspace/prefix is laid out, and exactly where the evidence stops.

How to read maturity

Validated means the named surface has current scoped test or live-service evidence. Preview means the integration is useful with meaningful evidence but important deployment gates remain open. Experimental marks a real implementation/checkpoint with material acceptance gaps. Planned means preparation exists but the provider integration is not yet accepted.

Provider / volatile storageValidated

Memory metadata + blocks

Core contract and local differential evidence; volatile by design.

Provider / file-backed relational stateValidated

SQLite

File-backed provider and Linux FUSE hosting have scoped evidence; not universal SQLite safety.

Provider / PostgreSQL wirePreview

PGlite

Real socket-server, fencing, reconnect/restart, split-store, and Rust/Node/CLI matrix evidence, plus hosted cross-platform recovery checks; production persistence, backup, observability, and ownership remain open.

Provider / object storageValidated

Cloudflare R2 / S3-compatible blocks

Authenticated live R2 block, configuration-driven CLI, both metadata-provider composition gates, the public-NAPI benchmark, and a complete budgeted hosted live-R2 workflow passed; broader native and release gates remain separate.

Provider / local S3-compatible serviceValidated

RustFS

Pinned service contract, restart, CAS, range, hosted RustFS checks, and real FoundationDB/TiDB composition checkpoints passed; bounded TiDB/RustFS Node and CLI configuration gates are wired, while replicated topology and credential-gated live consumer coverage remain open.

Provider / distributed SQLPreview

TiDB

Functional qualification is complete for the defined hosted TiDB/RustFS scope, including durable 3PD/3TiKV restart, fencing/ambiguous commit, and Linux/macOS consumer rows; production topology, IAM, DR, SLO/capacity, release, canary, and rollback gates remain open.

Provider / transactional key-value storeExperimental

FoundationDB

Real 7.4.7 provider and RustFS composition checkpoints, protected shared lease-authority code, shared-provider consumer selection, and terminal hosted Linux plus macOS feature-compile qualification now exist; live macOS service/mount, production identity, recovery, capacity, and release evidence remain open.

Provider / remote object storageValidated

AWS S3

The first-class Rust SDK/CLI AWS S3 block provider passed the live myroot private-bucket gate with a prefix-scoped assumed role, composed SQLite metadata, process reopen, and owned-prefix cleanup. The repository now also defines an operations runbook and optional S3Session::stats() telemetry boundary; production identity rotation, metadata ownership, recovery drills, collectors/alerts, canary/rollback, and hosted release gates remain separate.

Provider / S3-compatible gatewayExperimental

Apache Ozone

Pinned 2.2.1 gateway and arm64 block/restart/CAS/range evidence exist; the latest exact-tip hosted packet is diagnostic after hard 1,000-IOPS misses, while customer topology, backup/DR, secure tenancy, and release gates remain external.

The source of truth is the repository's architecture, porting evidence, requirements, and work tracker.