--- title: "chromem-go vs VectorChord" type: "comparison" canonical_url: "https://www.graphcanon.com/compare/philippgille-chromem-go-vs-supervc-stack-vectorchord" tools: ["philippgille-chromem-go", "supervc-stack-vectorchord"] --- # chromem-go vs VectorChord *GraphCanon updated Aug 21, 2026* ## 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. [chromem-go](https://github.com/philippgille/chromem-go) reports 1.0k GitHub stars, 75 forks, and 18 open issues, last pushed May 17, 2026. [VectorChord](https://docs.vectorchord.ai/vectorchord/getting-started/overview.html) has 1.8k stars, 71 forks, and 17 open issues, last pushed Jul 30, 2026. Figures are from public GitHub metadata via [chromem-go's repository](https://github.com/philippgille/chromem-go) and [VectorChord's repository](https://github.com/supervc-stack/VectorChord). | | [chromem-go](/tools/philippgille-chromem-go.md) | [VectorChord](/tools/supervc-stack-vectorchord.md) | | --- | --- | --- | | Tagline | Embeddable vector database for Go with Chroma-like interface. | Scalable, fast, and disk-friendly vector search in Postgres | | Stars | 1,047 | 1,758 | | Forks | 75 | 71 | | Open issues | 18 | 17 | | Language | Go | Rust | | Adopt for | 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__ - Scalable and disk-friendly vector search in PostgreSQL. | | Persona | - | - | | Runtime | - | - | | License | MPL-2.0 | Other | | Categories | Vector Databases | Vector Databases | ## Trust and health _Sourced signals - not a safety guarantee. No winner column._ | | [chromem-go](/tools/philippgille-chromem-go.md) | [VectorChord](/tools/supervc-stack-vectorchord.md) | | --- | --- | --- | | Maintenance | Slowing (36%) | Very active (96%) | | Days since push | 96d | 3d | | Open issues (now) | 18 | 17 | | Stars delta | +14 (30d) | Unknown | | Open issues delta | +1 (30d) | Unknown | | Full report | [trust report](/tools/philippgille-chromem-go/trust.md) | [trust report](/tools/supervc-stack-vectorchord/trust.md) | ## Decision facts: chromem-go - **Requirements:** Min 0.5 GB RAM - **Adopt for:** 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 ## Decision facts: VectorChord - **Adopt for:** __VectorChord__ - Scalable and disk-friendly vector search in PostgreSQL. ## Choose when ### 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. ### 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 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 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 ## 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,047). 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](/tools/philippgille-chromem-go/alternatives) and [VectorChord alternatives](/tools/supervc-stack-vectorchord/alternatives) ([chromem-go markdown twin](/tools/philippgille-chromem-go/alternatives.md), [VectorChord markdown twin](/tools/supervc-stack-vectorchord/alternatives.md)), 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](/compare/philippgille-chromem-go-vs-supervc-stack-vectorchord.md) 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: Slowing. 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](/tools/philippgille-chromem-go/trust); [VectorChord trust report](/tools/supervc-stack-vectorchord/trust). --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/graph?tool=philippgille-chromem-go`](/api/graphcanon/graph?tool=philippgille-chromem-go) - LLM index: [/llms.txt](/llms.txt) - Full corpus: [/llms-full.txt](/llms-full.txt) _GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_