Show HN: Hubmesh – Multi-hop RAG retrieval with zero LLM calls in the query path
Hubmesh is an open-source multi-hop RAG retrieval system that routes queries across a mesh of knowledge nodes without invoking an LLM in the query path.
Hubmesh, an open-source retrieval-augmented generation library, launched on GitHub on August 5, 2026, posted to Hacker News by author dsk_7699 as a Show HN submission. The project's core claim, per the Hacker News listing, is zero LLM calls in the query path — meaning retrieval traversal happens without invoking a language model at inference time.
The project is hosted at the GitHub repository under the handle DemigodDSK. The "multi-hop" framing refers to a retrieval approach where a query does not simply fetch the nearest vector neighbors in a single step, but instead traverses a graph-like mesh of knowledge nodes across multiple hops to assemble context before any generation step occurs.
The absence of LLM calls during query routing is the design's stated differentiator. In conventional RAG pipelines, some implementations use an LLM to rewrite, decompose, or route queries before retrieval — adding latency and cost. Hubmesh's architecture, as described in the Show HN post, moves that reasoning out of the hot path, handling traversal logic through the mesh topology itself rather than through model inference.
Beyond the headline and repository link, the available source material is limited: the HN submission had 1 point and 0 comments at the time of posting, and no additional corroborating sources were available. Details on supported embedding backends, graph construction methods, licensing, or benchmarks are not described in the source material and cannot be confirmed here.
What to watch: as a Show HN debut with minimal community engagement at launch, the project's trajectory will depend on documentation, reproducible benchmarks comparing retrieval quality and latency against single-hop or LLM-routed RAG baselines, and whether the author follows up in the thread with technical detail. No roadmap, team, or funding information is available from the sources provided.
No comments yet — start the thread.