Comparison
chromem-go vs voy
Verdict
Pick chromem-go if chromem-go is an embeddable vector database for Go that provides a Chroma-like interface with no third-party dependencies, suitable for applications needing in-memory persistence and cosine similarity search capabilities; pick voy if voy specializes in Webassembly-based vector similarity searches, coded in Rust, with support for k-d-trees and nearest-neighbor searching.
Markdown twin · chromem-go alternatives · voy alternatives
GraphCanon updated 1d
vs
Trust & integrity
| Signal | chromem-go | voy |
|---|---|---|
| Maintenance | Slowing (96d since push) As of 3d · github_public_v1 | Dormant (1067d since push) As of 1d · github_public_v1 |
| Provenance | Not a fork · Personal account As of 3d · github_public_v1 | Not a fork · Organization account As of 1d · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of 1mo · osv@v1 | No lockfile (source not queried) As of 1mo · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- chromem-go
- Embeddable vector database for Go with Chroma-like interface.
- voy
- A WASM vector similarity search written in Rust
Stars
- chromem-go
- 1.0k
- voy
- 1.1k
Forks
- chromem-go
- 75
- voy
- 41
Open issues
- chromem-go
- 18
- voy
- 22
Language
- chromem-go
- Go
- voy
- Rust
Adopt for
- chromem-go
- Chromem-go is an embeddable vector database for Go that provides a Chroma-like interface with no third-party dependencies, suitable for applications needing in-memory persistence and cosine similarity search capabilities
- voy
- Voy specializes in Webassembly-based vector similarity searches, coded in Rust, with support for k-d-trees and nearest-neighbor searching.
Persona
- chromem-go
- -
- voy
- -
Runtime
- chromem-go
- -
- voy
- -
License
- chromem-go
- MPL-2.0
- voy
- Apache-2.0
Last pushed
- chromem-go
- May 17, 2026
- voy
- Sep 20, 2023
Categories
- chromem-go
- Vector Databases
- voy
- Vector Databases
Trust and health
Maintenance
- chromem-go
- Slowing (36%)
- voy
- Dormant (18%)
Days since push
- chromem-go
- 96d
- voy
- 1067d
Open issues (now)
- chromem-go
- 18
- voy
- 22
Stars delta
- chromem-go
- +14 (30d)
- voy
- +4 (30d)
Open issues delta
- chromem-go
- +1 (30d)
- voy
- 0 (30d)
Owner type
- chromem-go
- User
- voy
- Organization
Full report
- chromem-go
- Trust report
- voy
- Trust report
Choose chromem-go if…
- chromem-go is primarily Go; voy is Rust.
- License: chromem-go is MPL-2.0, voy is Apache-2.0.
- Requirements: Min 0.5 GB RAM.
- Tags unique to chromem-go: chroma, cosine-similarity, embeddings, in-memory.
- If you are building applications in Go and require an in-memory vector database without additional third-party libraries.
When NOT to use chromem-go
- Avoid Chromem-go if you seek a traditional, disk-based persistence model as it primarily supports in-memory operations with optional persistence options.
- Chromem-go is not the best choice if your application requires heavy concurrent load and large-scale data handling which might surpass the in-memory capability limits of this library.
Choose voy if…
- voy is primarily Rust; chromem-go is Go.
- License: voy is Apache-2.0, chromem-go is MPL-2.0.
- Tags unique to voy: k-d-tree, nearest-neighbor-search, rust, similarity-search.
- When you require a Rust implementation of WebAssembly for embedding in web applications or for secure sandboxed execution on the server-side.
When NOT to use voy
- If high availability and extensive fault tolerance features are required, as Voy focuses primarily on vector similarity searches rather than system-wide reliability enhancements.
- When your project demands integration with existing large-scale SQL database systems, since Voy is specialized for a specific type of search operation.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (philippgille/chromem-go) · observed Aug 21, 2026
- GitHub forks (philippgille/chromem-go) · observed Aug 21, 2026
- Last push (philippgille/chromem-go) · observed May 17, 2026
- License file (MPL-2.0) · observed Aug 21, 2026
- Decision facts (enrichment) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (tantaraio/voy) · observed Aug 23, 2026
- GitHub forks (tantaraio/voy) · observed Aug 23, 2026
- Last push (tantaraio/voy) · observed Sep 20, 2023
- License file (Apache-2.0) · observed Aug 23, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: chromem-go 1.0k · voy 1.1k (synced Aug 21, 2026).
Common questions
- What is the difference between chromem-go and voy?
- chromem-go: Embeddable vector database for Go with Chroma-like interface.. voy: A WASM vector similarity search written in Rust. See the comparison table for live GitHub stats and shared categories.
- When should I choose chromem-go over voy?
- Choose chromem-go over voy when chromem-go is primarily Go; voy is Rust; License: chromem-go is MPL-2.0, voy is Apache-2.0; Requirements: Min 0.5 GB RAM; Tags unique to chromem-go: chroma, cosine-similarity, embeddings, in-memory; If you are building applications in Go and require an in-memory vector database without additional third-party libraries.
- When should I choose voy over chromem-go?
- Choose voy over chromem-go when voy is primarily Rust; chromem-go is Go; License: voy is Apache-2.0, chromem-go is MPL-2.0; Tags unique to voy: k-d-tree, nearest-neighbor-search, rust, similarity-search; When you require a Rust implementation of WebAssembly for embedding in web applications or for secure sandboxed execution on the server-side.
- When should I avoid chromem-go?
- Avoid Chromem-go if you seek a traditional, disk-based persistence model as it primarily supports in-memory operations with optional persistence options. Chromem-go is not the best choice if your application requires heavy concurrent load and large-scale data handling which might surpass the in-memory capability limits of this library.
- When should I avoid voy?
- If high availability and extensive fault tolerance features are required, as Voy focuses primarily on vector similarity searches rather than system-wide reliability enhancements. When your project demands integration with existing large-scale SQL database systems, since Voy is specialized for a specific type of search operation.
- Is chromem-go or voy more popular on GitHub?
- voy has more GitHub stars (1,069 vs 1,047). Stars measure visibility, not whether either tool fits your constraints.
- Are chromem-go and voy open source?
- Yes - both are open-source projects on GitHub (chromem-go: MPL-2.0, voy: Apache-2.0).
- Where can I find alternatives to chromem-go or voy?
- GraphCanon lists graph-backed alternatives at chromem-go alternatives and voy alternatives (chromem-go markdown twin, voy markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, chromem-go or voy?
- chromem-go: Slowing. voy: Dormant. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for chromem-go and voy?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: chromem-go trust report; voy trust report.