Databases

Fabric uses databases for durable runtime state and exposes separate, policy-gated tools for agent data access. Do not give the model raw database credentials.

Database	Runtime use	Agent data access
libSQL	Unified local or remote bundle through `libsqlPersistence()`.	Scoped tool guide.
MongoDB	Unified bundle through `mongodbPersistence()`.	First-party collection-bound find tools.
MySQL	Unified bundle through `mysqlPersistence()`.	First-party fixed-statement tools.
Postgres	Unified session, submission, stream, attachment, run/event, and cost persistence through `postgresPersistence()`.	First-party fixed-statement tools.
Redis	Project-owned coordination/store implementation.	First-party namespaced get/set tools.
Supabase	Reuse `postgresPersistence()` with the direct Postgres connection.	RLS-aware table/RPC tool guide.
Turso	Reuse `libsqlPersistence()` with a remote URL/token.	Parameterized libSQL tool guide.
Valkey	Reuse `redisPersistence()` with a Redis-protocol client.	Namespaced command tool guide.
Databricks Lakebase	Sessions, submissions, conversation streams, and attachments for Databricks Apps.	Use governed Databricks SQL and Unity Catalog tools separately.
SQLite	Local durable sessions through Node configuration.	First-party fixed-statement tools.

See Session stores for the complete persistence contract.

Install governed data tools with pnpm add @fabric-harness/databases or scaffold a complete provider module with fh add database postgres, mysql, mongodb, redis, or sqlite. Postgres and Lakebase, MySQL, MongoDB, libSQL/Turso, Redis/Valkey, SQLite, and Supabase/Postgres provide durable Fabric stores. Data tools and session persistence remain separate so model-facing access never receives runtime-store credentials implicitly.