head to head · open source
xerj vs dingo
xerj has 18,686 GitHub stars, 1,423 forks, 16 open issues and last shipped yesterday. dingo has 1,705 stars, 263 forks, 8 open issues and last shipped 4 days ago. xerj leads on adoption by 996% (18,686 vs 1,705 stars). xerj is written in Rust under Apache-2.0; dingo is written in Java under Apache-2.0. xerj has attracted 8% as many forks as stars, dingo 15%. xerj was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (hybrid-search), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| xerj | dingo | |
|---|---|---|
| GitHub stars | ★ 19K | ★ 1.7K |
| License | Apache-2.0 | Apache-2.0 |
| Written in | Rust | Java |
| Last push | 2026-11-02 | 2026-10-30 |
| Forks | ⑂ 1.4K | ⑂ 263 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick xerj if
- You weight community size — 19K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Rust
- You value the larger contributor base for long-term maintenance
pick dingo if
- You want the dingo feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Java
- You evaluated both and dingo fits your workflow better
About xerj
XERJ XERJ is a community trusted local AI search that indexes any folder automatically, so your coding agent stops burning tokens reading files one by one and pulls the exact code it needs instead. Reference coding is its main use case and the clearest win: point an agent at a task and it downloads the open source repos closest to it, indexes them, and reuses how they solved the problem before writing its own code. In a controlled study that cut a coding agent's output tokens by 2.7x at the same 16/16 solve rate (case study), and people report roughly 5x in everyday work (field reports). It is enough for a…
About dingo
DingoDB DingoDB is an open source distributed multi modal vector database independently designed and developed by DataCanvas, which integrates real time strong consistency, relational semantics, and vector semantics into a unified platform, DingoDB positioning itself as a distinctive multi modal database solution. With exceptional horizontal scalability and elastic scaling capabilities, it effortlessly meets enterprise grade high availability requirements. Furthermore, DingoDB offers extensive multi language interfaces and seamless compatibility with the MySQL protocol, delivering unparalleled flexibility and…
read the full dingo overview →
More in AI & Machine Learning
Related comparisons
More Machine Learning Infrastructure projects
Compare either of these against the rest of the Machine Learning Infrastructure field.
Frequently asked questions
Is xerj or dingo more popular?
xerj has 18,686 GitHub stars and dingo has 1,705. xerj has the larger community by that measure.
Are xerj and dingo free?
Both are open source. xerj is licensed under Apache-2.0 and dingo under Apache-2.0. Neither carries a licence fee.
What is the difference between xerj and dingo?
xerj is written in Rust and dingo in Java. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, xerj or dingo?
Choose xerj if you want the larger community (18,686 stars) or its Apache-2.0 licence terms. Choose dingo if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.