Comparison
hora vs chromem-go
Verdict
Pick hora if hora is a Rust-based library for high-performance approximate nearest neighbor search algorithms critical in applications such as image and recommender systems where speed and efficiency are paramount; 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.
Markdown twin · hora alternatives · chromem-go alternatives
GraphCanon updated today
vs
Trust & integrity
| Signal | hora | chromem-go |
|---|---|---|
| Maintenance | Slowing (155d since push) As of 4w · github_public_v1 | Slowing (96d since push) As of today · github_public_v1 |
| Provenance | Not a fork · Organization account As of 4w · github_public_v1 | Not a fork · Personal account As of today · 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
- hora
- efficient approximate nearest neighbor search algorithm collections library written in Rust
- chromem-go
- Embeddable vector database for Go with Chroma-like interface.
Stars
- hora
- 2.7k
- chromem-go
- 1.0k
Forks
- hora
- 78
- chromem-go
- 75
Open issues
- hora
- 26
- chromem-go
- 18
Language
- hora
- Rust
- chromem-go
- Go
Adopt for
- hora
- Hora is a Rust-based library for high-performance approximate nearest neighbor search algorithms critical in applications such as image and recommender systems where speed and efficiency are paramount.
- 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
- hora
- -
- chromem-go
- -
Runtime
- hora
- -
- chromem-go
- -
License
- hora
- Apache-2.0
- chromem-go
- MPL-2.0
Last pushed
- hora
- Feb 17, 2026
- chromem-go
- May 17, 2026
Categories
- hora
- Data & Retrieval, Vector Databases
- chromem-go
- Vector Databases
Trust and health
Days since push
- hora
- 155d
- chromem-go
- 96d
Open issues (now)
- hora
- 26
- chromem-go
- 18
Stars delta
- hora
- Unknown
- chromem-go
- +14 (30d)
Open issues delta
- hora
- Unknown
- chromem-go
- +1 (30d)
Owner type
- hora
- Organization
- chromem-go
- User
Full report
- hora
- Trust report
- chromem-go
- Trust report
Choose hora if…
- hora is primarily Rust; chromem-go is Go.
- License: hora is Apache-2.0, chromem-go is MPL-2.0.
- Tags unique to hora: algorithm, approximate-nearest-neighbor-search, artificial-intelligence, data-structures.
- Also covers Data & Retrieval.
- When you require a high-speed library written in Rust to implement an efficient similarity-search solution
When NOT to use hora
- If your project is restricted to languages other than Rust and you cannot work with Rust bindings or require a more general-purpose vector database library
- When exact nearest neighbor search accuracy is preferred over the speed provided by approximate algorithms, as Hora specializes in sacrificing minimal precision for significant performance gains
Choose chromem-go if…
- chromem-go is primarily Go; hora is Rust.
- License: chromem-go is MPL-2.0, hora 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.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (hora-search/hora) · observed Jul 23, 2026
- GitHub forks (hora-search/hora) · observed Jul 23, 2026
- Last push (hora-search/hora) · observed Feb 17, 2026
- License file (Apache-2.0) · observed Jul 23, 2026
- Decision facts (enrichment) · observed Jul 15, 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: hora 2.7k · chromem-go 1.0k (synced Jul 23, 2026).
Common questions
- What is the difference between hora and chromem-go?
- hora: efficient approximate nearest neighbor search algorithm collections library written in 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 hora over chromem-go?
- Choose hora over chromem-go when hora is primarily Rust; chromem-go is Go; License: hora is Apache-2.0, chromem-go is MPL-2.0; Tags unique to hora: algorithm, approximate-nearest-neighbor-search, artificial-intelligence, data-structures; Also covers Data & Retrieval; When you require a high-speed library written in Rust to implement an efficient similarity-search solution.
- When should I choose chromem-go over hora?
- Choose chromem-go over hora when chromem-go is primarily Go; hora is Rust; License: chromem-go is MPL-2.0, hora 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 avoid hora?
- If your project is restricted to languages other than Rust and you cannot work with Rust bindings or require a more general-purpose vector database library When exact nearest neighbor search accuracy is preferred over the speed provided by approximate algorithms, as Hora specializes in sacrificing minimal precision for significant performance gains
- 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 hora or chromem-go more popular on GitHub?
- hora has more GitHub stars (2,663 vs 1,047). Stars measure visibility, not whether either tool fits your constraints.
- Are hora and chromem-go open source?
- Yes - both are open-source projects on GitHub (hora: Apache-2.0, chromem-go: MPL-2.0).
- Where can I find alternatives to hora or chromem-go?
- GraphCanon lists graph-backed alternatives at hora alternatives and chromem-go alternatives (hora 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, hora or chromem-go?
- hora: Slowing. 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 hora and chromem-go?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: hora trust report; chromem-go trust report.