Nicheloom visits: 58,069 all-time · 7,637 in the last 7 days

The opportunity tracker for new startups.

Today: 1,953 launches · Niche of the day: specialized calculation tools · See what launched today →

L88

A Local RAG System on 8GB VRAM (Need Architecture Feedback)

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

Hey everyone,I’ve been working on a project called L88 — a local RAG system that I initially focused on UI/UX for, so the retrieval and model architecture still need proper refinement.Repo: https://github.com/Hundred-Trillion/L88-FullI’m running this on 8GB VRAM and a strong CPU (128GB RAM). Embeddings and preprocessing run on CPU, and the main model runs on GPU. One limitation I ran into is that my evaluator and generator LLM ended up being the same model due to compute constraints, which defeats the purpose of evaluation.I’d really appreciate feedback on:Better architecture ideas for small-VRAM RAGSplitting evaluator/generator roles effectivelyImproving the LangGraph pipelineAny bugs or design smells you noticeWays to optimize the system for local hardwareI’m 18 and still learning a lot about proper LLM architecture, so any technical critique or suggestions would help me grow as a developer. If you check out the repo or leave feedback, it would mean a lot — I’m trying to build a solid foundation and reputation through real projects.Thanks!

HN · launched Feb 24, 2026 · 12 upvotes (top 40%) · 0 views

Niche: rag developer frameworks and tools · 59 launches, 3 in the last 7 days · Explore this niche →

Category and tags

  • Horizontal
  • Search & retrieval
  • Developer
  • AI-native
  • Hobby / open-source project

Source listing ↗

Could you build this?

Yes This is a local RAG interface built on standard open-source tools (like Ollama, LangChain/LlamaIndex, and local vector stores) constrained to run on 8GB VRAM.

Discussion

3 comments analyzed.

Competitors mentioned: Qdrant, FAISS, SQLite, Supabase (vector/storage solutions), BGE-base-en-v1.5, bge-reranker-v2-m3 (embedding/reranking models), Cross-encoder rerankers, BM25 (keyword search)

Concerns raised: VRAM/RAM constraints on free-tier/low-resource servers, Latency from multiple sequential LLM calls, Circular evaluation issue: using same model for retrieval and quality scoring, Vector search alone misses exact-match queries (titles, authors), Cross-encoder rerankers destroy performance on resource-constrained setups

Feature requests: Merge router/analyzer/rewriter into single LLM call to reduce latency, Implement hybrid BM25 + vector search with dynamic weighting by query type, Add semantic caching layer (cosine similarity threshold) alongside exact-match hashing, Use cross-encoder for evaluation/thresholding instead of LLM-as-judge, Parent-child chunking: embed small chunks, store large payloads in lightweight DB

Competitors

Other products that read as similar to this one : 426 launches clear the similarity bar, closest 8 shown.

Attention rank: #189 of 427 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 116 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.