xerj vs manticoresearch

Two of the top projects in RAG and search, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.

11st of 21 in RAG and search

xerj

Elasticsearch-compatible search server that auto-indexes folders for coding agents

#77th of 21 in RAG and search

manticoresearch

C++ search database with full-text, vector and hybrid search over SQL and HTTP

Verdict

xerj ranks higher, 87 to 75. Of the 4 score parts we measure for both, xerj leads on 3, manticoresearch on none and 1 is even.

  • Adoptionxerj leads by 9 points, 83 to 74.
  • FreshnessEven at 100.
  • Maintenancexerj leads by 18 points, 96 to 78: a wide gap.
  • Agent-readyxerj leads by 30 points, 30 to 0: a wide gap.

Pick xerj if you are

Developers giving coding agents local code and document search or memory

  • Single static binary, no JVM; prebuilt for Linux, macOS and Windows on x86-64 and arm64
  • Works with existing Elasticsearch clients pointed at localhost:9200; 1366/1369 ES-YAML conformance tests

Pick manticoresearch if you are

Engineers replacing Elasticsearch or adding hybrid search to self-hosted apps

  • Hybrid full-text and KNN retrieval in one query, with auto-embeddings and chunking
  • Speaks MySQL protocol and HTTP JSON; official clients for nine languages
xerj vs manticoresearch: score parts and facts
What we comparexerjmanticoresearch
Score parts, out of 100
Adoption83, widely used74, popular
Freshness100, active100, active
Maintenance96, healthy78, fair
Agent-ready30, minimal0, none
Facts from GitHub and the README
Stars19.2k12.1k
LicenseApache-2.0 (permissive)GPL-3.0 (copyleft)
Last commitNov 2026Nov 2026
Last releaseNov 2026Sep 2026
LanguageRustC++
DockerNoYes
GPUNot neededNot stated
arm64 or Apple SiliconMentionedMentioned

xerj

XERJ is a single Rust binary that speaks the Elasticsearch API. `xerj autoindex <folder>` infers datasets from code, docs, logs, PDFs, SQLite and CSV, and creates one typed index per dataset, with tree-sitter symbols and line numbers for code. It supports BM25, kNN and hybrid search, a `/_memory` agent memory API, and a `xerj mcp` stdio server exposing 13 tools. Its main pitch is cutting agent token use by retrieving passages instead of reading files.

Who it is for: Developers giving coding agents local code and document search or memory

Strengths

  • Single static binary, no JVM; prebuilt for Linux, macOS and Windows on x86-64 and arm64
  • Works with existing Elasticsearch clients pointed at localhost:9200; 1366/1369 ES-YAML conformance tests
  • Autoindex needs no schema; handles code, PDF, DOCX, XLSX, SQLite, mail and logs
  • Default lexical embedder runs offline; air-gapped deployment recipe is documented

Weaknesses

  • Token savings come from the project's own 16-run study; neutral to negative on popular libraries
  • Default embedder is lexical feature-hashing; neural mode is opt-in and downloads about 90 MB
  • `--insecure` quick start disables TLS and auth; every caller becomes a superuser
  • Optional Jev rerank sends result text to TypeSafe's servers
  • Rust, lexical embedder (default, offline), neural embedder (opt-in, ~90 MB download), Jev reranker (optional, external service)

manticoresearch

Manticore Search is a C++ search database with SQL (MySQL protocol) and HTTP JSON interfaces, positioned as an Elasticsearch alternative. It combines full-text search, KNN vector search, hybrid queries and auto-embeddings with chunking, and adds conversational search through SQL CALL CHAT. Storage is row-wise or columnar, with real-time inserts, sharded tables and Galera-based multi-master replication.

Who it is for: Engineers replacing Elasticsearch or adding hybrid search to self-hosted apps

Strengths

  • Hybrid full-text and KNN retrieval in one query, with auto-embeddings and chunking
  • Speaks MySQL protocol and HTTP JSON; official clients for nine languages
  • Columnar storage for datasets larger than RAM; about 40MB RSS when empty
  • Replication, sharded tables, built-in auth, backup to S3-compatible storage

Weaknesses

  • GPL-3.0 licence may constrain embedding in proprietary products
  • Not fully ACID; only isolated transactions and binary logging
  • Elasticsearch compatibility covers writes only, not the full query API
  • Benchmark claims come from the project's own suite and are workload-specific
  • C++, auto-embeddings, LLM-backed CALL CHAT
  • Needs Manticore Columnar Library (columnar storage), LLM provider (conversational search)

More in RAG and search

Building with these?

We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.