Comparison
chromem-go vs VectorChord
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 VectorChord if __VectorChord__ - Scalable and disk-friendly vector search in PostgreSQL.
Markdown twin · chromem-go alternatives · VectorChord alternatives
GraphCanon updated 2w
vs
Trust & integrity
| Signal | chromem-go | VectorChord |
|---|---|---|
| Maintenance | Steady (65d since push) As of 1mo · github_public_v1 | Very active (3d since push) As of 2w · github_public_v1 |
| Provenance | Not a fork · Personal account As of 1mo · github_public_v1 | Not a fork · Personal account As of 2w · 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.
- VectorChord
- Scalable, fast, and disk-friendly vector search in Postgres
Stars
- chromem-go
- 1.0k
- VectorChord
- 1.8k
Forks
- chromem-go
- 71
- VectorChord
- 71
Open issues
- chromem-go
- 17
- VectorChord
- 17
Language
- chromem-go
- Go
- VectorChord
- 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
- VectorChord
- __VectorChord__ - Scalable and disk-friendly vector search in PostgreSQL.
Persona
- chromem-go
- -
- VectorChord
- -
Runtime
- chromem-go
- -
- VectorChord
- -
License
- chromem-go
- MPL-2.0
- VectorChord
- Other
Last pushed
- chromem-go
- May 17, 2026
- VectorChord
- Jul 30, 2026
Categories
- chromem-go
- Vector Databases
- VectorChord
- Vector Databases
Trust and health
Maintenance
- chromem-go
- Steady (60%)
- VectorChord
- Very active (96%)
Days since push
- chromem-go
- 65d
- VectorChord
- 3d
Full report
- chromem-go
- Trust report
- VectorChord
- Trust report
Choose chromem-go if…
- chromem-go is primarily Go; VectorChord is Rust.
- License: chromem-go is MPL-2.0, VectorChord is Other.
- 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 VectorChord if…
- VectorChord is primarily Rust; chromem-go is Go.
- License: VectorChord is Other, chromem-go is MPL-2.0.
- Tags unique to VectorChord: artificial-intelligence, llmops, postgresql.
- - When you need efficient vector searches within a PostgreSQL database with compatibility to existing systems using pgvector
When NOT to use VectorChord
- - If you cannot use PostgreSQL or if your application already uses another database system with specific vector search capabilities
- - When detailed customization beyond what VectorChord provides, such as deep integration with unique machine learning frameworks not natively supported by the extension, is required
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 Jul 22, 2026
- GitHub forks (philippgille/chromem-go) · observed Jul 22, 2026
- Last push (philippgille/chromem-go) · observed May 17, 2026
- License file (MPL-2.0) · observed Jul 22, 2026
- Decision facts (enrichment) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (supervc-stack/VectorChord) · observed Aug 2, 2026
- GitHub forks (supervc-stack/VectorChord) · observed Aug 2, 2026
- Last push (supervc-stack/VectorChord) · observed Jul 30, 2026
- License file (Other) · observed Aug 2, 2026
- Decision facts (enrichment) · observed Jul 12, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: chromem-go 1.0k · VectorChord 1.8k (synced Jul 22, 2026).
Common questions
- What is the difference between chromem-go and VectorChord?
- chromem-go: Embeddable vector database for Go with Chroma-like interface.. VectorChord: Scalable, fast, and disk-friendly vector search in Postgres. See the comparison table for live GitHub stats and shared categories.
- When should I choose chromem-go over VectorChord?
- Choose chromem-go over VectorChord when chromem-go is primarily Go; VectorChord is Rust; License: chromem-go is MPL-2.0, VectorChord is Other; 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 VectorChord over chromem-go?
- Choose VectorChord over chromem-go when VectorChord is primarily Rust; chromem-go is Go; License: VectorChord is Other, chromem-go is MPL-2.0; Tags unique to VectorChord: artificial-intelligence, llmops, postgresql; - When you need efficient vector searches within a PostgreSQL database with compatibility to existing systems using pgvector.
- 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 VectorChord?
- - If you cannot use PostgreSQL or if your application already uses another database system with specific vector search capabilities - When detailed customization beyond what VectorChord provides, such as deep integration with unique machine learning frameworks not natively supported by the extension, is required
- Is chromem-go or VectorChord more popular on GitHub?
- VectorChord has more GitHub stars (1,758 vs 1,033). Stars measure visibility, not whether either tool fits your constraints.
- Are chromem-go and VectorChord open source?
- Yes - both are open-source projects on GitHub (chromem-go: MPL-2.0, VectorChord: Other).
- Where can I find alternatives to chromem-go or VectorChord?
- GraphCanon lists graph-backed alternatives at chromem-go alternatives and VectorChord alternatives (chromem-go markdown twin, VectorChord 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 VectorChord?
- chromem-go: Steady. VectorChord: Very active. 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 VectorChord?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: chromem-go trust report; VectorChord trust report.