alibaba/zvec

A lightweight, lightning-fast, in-process vector database

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 31 minutes ago
Added to GitGenius on February 18th, 2026
Created on December 5th, 2025
Open Issues & Pull Requests: 58 (+0)
Number of forks: 979
Total Stargazers: 15,504 (+0)
Total Subscribers: 70 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 26.6 hours
90th percentile: 16.4 hours
Tracked items: 157

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 62% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Only 6% of issues opened in the past year have been closed. Three people close 59% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 26
New in 7 days: 1
Closed in 7 days: 4
Avg open age: 39 days
Stale 30+ days: 18
Stale 90+ days: 9

Recent activity

Opened in 7 days: 1
Closed in 7 days: 4
Comments in 7 days: 4
Events in 7 days: 26

Top labels

  • bug (36)
  • feature (36)
  • enhancement (27)
  • integration (6)
  • good first issue (5)
  • help wanted (5)
  • info-needed (5)
  • deferred (4)

Detailed Description

Zvec is a lightweight, in-process vector database designed for embedding directly into applications.

The tool addresses the need for fast, low-latency similarity search without requiring a separate database service. It operates entirely within an application's process, eliminating network overhead and deployment complexity. Zvec supports multiple indexing strategies including flat search, HNSW (Hierarchical Navigable Small World), and sparse indexes, allowing developers to trade off between search speed and memory usage based on their requirements. The database includes quantization options to reduce memory footprint and integrates full-text search capabilities alongside vector similarity operations.

Zvec suits applications that need embedded vector search without external dependencies, particularly those prioritizing low latency and minimal operational overhead. It works well for RAG systems, semantic search features, and LLM memory layers where keeping data local to the application is advantageous. The tool is production-tested within Alibaba Group, indicating it has handled real-world workloads at scale. Developers should consider Zvec when they want to avoid managing a separate database service and can accept in-process memory constraints, or when application latency is critical enough to justify avoiding network calls.

The project receives issues from both core maintainers and external users, indicating adoption beyond the original team without creating an unsustainable support burden. Maintainers typically respond to new issues and pull requests within hours. Development activity centers on features, bug fixes, and enhancements, reflecting active evolution of the tool's capabilities.