Comparison
tinyvector vs chromem-go
Verdict
Pick tinyvector if lightweight Rust-based embedding storage for efficiency; 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.
Markdown twin · tinyvector alternatives · chromem-go alternatives
GraphCanon updated 1d
vs
Trust & integrity
| Signal | tinyvector | chromem-go |
|---|---|---|
| Maintenance | Dormant (969d since push) As of 1d · github_public_v1 | Slowing (96d since push) As of 3d · github_public_v1 |
| Provenance | Not a fork · Personal account As of 1d · github_public_v1 | Not a fork · Personal account As of 3d · 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
- tinyvector
- A tiny embedding database in pure Rust.
- chromem-go
- Embeddable vector database for Go with Chroma-like interface.
Stars
- tinyvector
- 439
- chromem-go
- 1.0k
Forks
- tinyvector
- 25
- chromem-go
- 75
Open issues
- tinyvector
- 8
- chromem-go
- 18
Language
- tinyvector
- Rust
- chromem-go
- Go
Adopt for
- tinyvector
- Lightweight Rust-based embedding storage for efficiency.
- 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
Persona
- tinyvector
- -
- chromem-go
- -
Runtime
- tinyvector
- -
- chromem-go
- -
License
- tinyvector
- MIT
- chromem-go
- MPL-2.0
Last pushed
- tinyvector
- Dec 28, 2023
- chromem-go
- May 17, 2026
Categories
- tinyvector
- Vector Databases
- chromem-go
- Vector Databases
Trust and health
Maintenance
- tinyvector
- Dormant (18%)
- chromem-go
- Slowing (36%)
Days since push
- tinyvector
- 969d
- chromem-go
- 96d
Open issues (now)
- tinyvector
- 8
- chromem-go
- 18
Stars delta
- tinyvector
- +3 (30d)
- chromem-go
- +14 (30d)
Open issues delta
- tinyvector
- 0 (30d)
- chromem-go
- +1 (30d)
Full report
- tinyvector
- Trust report
- chromem-go
- Trust report
Choose tinyvector if…
- tinyvector is primarily Rust; chromem-go is Go.
- License: tinyvector is MIT, chromem-go is MPL-2.0.
- Tags unique to tinyvector: machine-learning, rust, search-engines, similarity-search.
- tinyvector ships Docker support for self-hosted deployment.
- When developing applications requiring efficient similarity searches over embeddings that are written in Rust or integrate well with Rust systems.
When NOT to use tinyvector
- For heavy-scale distributed vector operations as tinyvector is designed to be lightweight and might not scale as expected compared to larger solutions like Faiss or PQ.
Choose chromem-go if…
- chromem-go is primarily Go; tinyvector is Rust.
- License: chromem-go is MPL-2.0, tinyvector is MIT.
- Requirements: Min 0.5 GB RAM.
- Tags unique to chromem-go: chroma, cosine-similarity, in-memory, llms.
- 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.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (m1guelpf/tinyvector) · observed Aug 23, 2026
- GitHub forks (m1guelpf/tinyvector) · observed Aug 23, 2026
- Last push (m1guelpf/tinyvector) · observed Dec 28, 2023
- License file (MIT) · observed Aug 23, 2026
- Decision facts (enrichment) · observed Jul 12, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- 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 on cards: tinyvector 439 · chromem-go 1.0k (synced Aug 23, 2026).
Common questions
- What is the difference between tinyvector and chromem-go?
- tinyvector: A tiny embedding database in pure Rust.. chromem-go: Embeddable vector database for Go with Chroma-like interface.. See the comparison table for live GitHub stats and shared categories.
- When should I choose tinyvector over chromem-go?
- Choose tinyvector over chromem-go when tinyvector is primarily Rust; chromem-go is Go; License: tinyvector is MIT, chromem-go is MPL-2.0; Tags unique to tinyvector: machine-learning, rust, search-engines, similarity-search; tinyvector ships Docker support for self-hosted deployment; When developing applications requiring efficient similarity searches over embeddings that are written in Rust or integrate well with Rust systems.
- When should I choose chromem-go over tinyvector?
- Choose chromem-go over tinyvector when chromem-go is primarily Go; tinyvector is Rust; License: chromem-go is MPL-2.0, tinyvector is MIT; Requirements: Min 0.5 GB RAM; Tags unique to chromem-go: chroma, cosine-similarity, in-memory, llms; If you are building applications in Go and require an in-memory vector database without additional third-party libraries.
- When should I avoid tinyvector?
- For heavy-scale distributed vector operations as tinyvector is designed to be lightweight and might not scale as expected compared to larger solutions like Faiss or PQ.
- 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.
- Is tinyvector or chromem-go more popular on GitHub?
- chromem-go has more GitHub stars (1,047 vs 439). Stars measure visibility, not whether either tool fits your constraints.
- Are tinyvector and chromem-go open source?
- Yes - both are open-source projects on GitHub (tinyvector: MIT, chromem-go: MPL-2.0).
- Where can I find alternatives to tinyvector or chromem-go?
- GraphCanon lists graph-backed alternatives at tinyvector alternatives and chromem-go alternatives (tinyvector markdown twin, chromem-go 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, tinyvector or chromem-go?
- tinyvector: Dormant. chromem-go: Slowing. 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 tinyvector and chromem-go?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: tinyvector trust report; chromem-go trust report.