d-hackmt/8hr-marathon — explained in plain English
Analysis updated 2026-05-18
Build an internal chatbot that answers questions from a company's own documents.
Study a reference architecture for retrieval augmented generation with guardrails and reranking.
Evaluate RAG answer quality using the included RAGAS based evaluation suite.
Learn how to route LLM calls through a gateway with automatic key fallback.
| d-hackmt/8hr-marathon | krishnaik06/complete-machine-learning-2023 | physx-omni/physx-omni | |
|---|---|---|---|
| Stars | 106 | 119 | 88 |
| Language | Jupyter Notebook | Jupyter Notebook | Jupyter Notebook |
| Last pushed | — | 2023-09-16 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | hard | easy | hard |
| Complexity | 4/5 | 1/5 | 5/5 |
| Audience | developer | general | researcher |
Figures from each repo's GitHub metadata at analysis time.
Requires API keys for Groq, Portkey, Qdrant, Logfire, LangSmith, and Gemini before it will run.
This repository, titled Enterprise Agentic RAG, is a system that answers questions by first retrieving relevant information from a set of documents and then generating an answer with a language model, an approach commonly called RAG. It is aimed at enterprise style document question answering and is built to tell apart genuinely relevant technical content from irrelevant or noisy documents before answering. The system checks incoming questions with a safety layer called NeMo Guardrails before doing anything else, blocking off topic requests, jailbreak attempts, and prompt injection. A planner then decides whether a question is simple conversation or something that needs document retrieval. Technical questions go through a retriever that searches a Qdrant vector database, then a local reranker called FlashRank narrows the results down before a final responder generates the answer, with LangGraph keeping track of conversation memory across the whole flow. Language model calls are routed through a gateway called Portkey, which can automatically fall back to a backup key if the primary one fails, and the underlying model used is Llama 3.3 70B served through Groq. Document embeddings for search come from Google's Gemini embedding model. Document parsing for PDF, HTML, TXT, DOCX, and PPTX files happens entirely on the user's own machine, with no external service needed. The project also includes tracing through Pydantic Logfire and LangSmith, and an evaluation suite built on RAGAS with six metrics plus a Streamlit app to view results. To run it, you create a Python virtual environment, install the pinned dependencies, and fill in a .env file with API keys for Groq, Portkey, Qdrant, Logfire, LangSmith, and Gemini. After running an ingestion command that parses and indexes the sample documents, you start a FastAPI backend and a separate Streamlit chat interface in two terminals. An optional evaluation app can be run against the live backend afterward. The README includes eleven separate documentation guides covering the system's architecture, environment variables, and known gotchas in detail.
An enterprise question answering system that retrieves relevant documents, filters out noise, and generates safe answers using multiple AI services.
Mainly Jupyter Notebook. The stack also includes LangGraph, Portkey, Qdrant.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.