Storage

Choose and operate a backend

Compare durability, search, idempotency and migration limits.

Persistence and capabilities. GovernedStore applies common rules over backends with different capabilities. pgvector is the production reference; memory is volatile; Qdrant is experimental and limited to laboratory use in the reviewed sources.

pgvector: production reference

The default backend uses PostgreSQL with pgvector. It provides durable storage, ranked text search, a unique content index, ACL filtering and database-side ordering. Check the installation’s capabilities before investigating result differences.

orkmind store info

memory: testing and development

memory needs no external service but loses data when the process ends. Text search uses token matching without ranking. Uniqueness is process-local; this backend does not replace production storage.

Qdrant: laboratory use only

The reviewed guide marks Qdrant as experimental and not enabled for production. It records unresolved profile identity and TTL disposal issues. Do not use this backend for production data based on this documentation.

Idempotency is best-effort: concurrent writes may duplicate content because there is no equivalent unique index. Text search is unranked, and the governed layer may warn when the candidate window saturates.

Migrate with declared losses

Export does not remove the source. The format carries entries and embeddings; old versions and snapshots included in a dump are not restored into the destination under the current contract. Loss requires explicit acceptance. Check counts, capabilities and restoration before changing the runtime’s backend.

orkmind store --help