memvid vs RuVector

Rust-based persistent memory and retrieval projects compared

memvid and RuVector both provide Rust-based tools for persistent AI memory and local retrieval. memvid centers on a portable, searchable single file, while RuVector is a broader toolkit with separate packages for vector search, graph memory, learning, and agent integrations.

memvidRuVector
LanguageRustRust
LicenseApache-2.0MIT
Stars17.3k4.6k
Forks1.5k613
Last analyzedOct 30, 2026Oct 19, 2026

Key differences

  • memvid packages content, metadata, and search structures in `.mv2` files; RuVector provides persistent vector storage and similarity search through its components.
  • memvid combines BM25 full-text search with optional vector search; RuVector emphasizes vector search, metadata filtering, and HNSW or flat indexes.
  • memvid lists Apache-2.0 licensing, while RuVector lists MIT licensing.
  • memvid offers Rust, Python, Node.js, and CLI interfaces; RuVector also has browser/WASM, PostgreSQL, and MCP package surfaces.
  • RuVector is a monorepo whose graph, learning, and MCP components require explicit integration; memvid focuses on memory files and their retrieval capabilities.
  • memvid requires Rust 1.85 or newer for its Rust library; RuVector requires Rust 1.77 or newer for its core workspace, and Node.js 18 or newer for its npm path.

Choose memvid if you…

  • need a portable, searchable memory file without a separate database service.
  • want full-text BM25 retrieval alongside optional vector search in one format.
  • need Python, Node.js, or Rust interfaces to a local memory layer.
Read the memvid analysis →

Choose RuVector if you…

  • want vector search with metadata filtering and HNSW or flat indexes.
  • need to explore separate browser/WASM, PostgreSQL, or MCP package paths.
  • plan to combine vector retrieval with graph or feedback-driven memory components.
Read the RuVector analysis →

Compare the numbers side by side, or add more projects

This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.