explaingit

emilresearch/ragless

Analysis updated 2026-05-18

7PythonAudience · developerComplexity · 3/5Setup · moderate

TLDR

A document Q&A system that uses AI only during setup to create answer blocks, then answers questions at runtime via fast local vector search with zero AI calls, zero hallucinations, and near-zero cost.

Mindmap

mindmap
  root((RAGless))
    How it works
      AI extracts Q&A blocks
      Qdrant stores vectors
      Query matches by similarity
    Three scripts
      prepare_data
      ingest_to_qdrant
      chatbot CLI
    Key benefits
      No runtime LLM calls
      Zero hallucinations
      Local and private
    Trade-offs
      Fixed answers only
      Coverage bounded by docs
    Setup
      Python 3.10 plus
      Free Gemini API key
      No Docker needed
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Build a support chatbot for your product's help documentation that gives exact, verifiable answers without ever calling an AI at runtime.

USE CASE 2

Create an FAQ bot for a hotel, venue, or service business by feeding policy documents to the preparation script.

USE CASE 3

Add a deterministic Q&A layer to an internal knowledge base so employees get consistent answers to policy questions.

USE CASE 4

Replace a costly generative RAG pipeline with a retrieval-only system to eliminate per-query API costs.

What is it built with?

PythonQdrantGemini APILiteLLM

How does it compare?

emilresearch/raglesscaptaingrock/krea2trainercodenamekt/hexus
Stars777
LanguagePythonPythonPython
Setup difficultymoderatehardmoderate
Complexity3/54/53/5
Audiencedeveloperdesignerdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires a free Gemini API key and one LLM-powered ingestion run per document set before the chatbot is usable.

No license information was mentioned in the README.

In plain English

RAGless is a question-answering system for your own documents that works without calling an AI model at query time. Most documentation chatbots send each user question to a language model at runtime, which costs money, introduces lag, and sometimes produces incorrect answers. RAGless takes a different approach: an AI model is used only once during setup to convert your documents into pre-written question-and-answer pairs, and all subsequent user queries are handled by fast local vector search with no API calls. The workflow has three steps. First, you run a preparation script that reads your PDF, text, or Markdown files and uses the Gemini API to extract structured question-and-answer blocks from them. Each block contains the answer text, several ways a user might phrase the question, and a source quote. Second, an ingestion script turns those blocks into vector embeddings and loads them into a local Qdrant database stored on your disk. Third, users interact with a command-line chatbot that compares their question to the stored question vectors, sums up scores across multiple phrasing variants of the same answer, and returns the best matching pre-written answer verbatim. Because answers are fixed at ingestion time, the system cannot hallucinate at runtime. It also cannot generate novel answers or combine information from multiple sources into a single synthesized response. It works best for support documentation, FAQ content, or policy documents where there is a known, finite set of correct answers. The README includes a detailed comparison table showing where this approach beats classic retrieval-augmented generation and where it falls short. Setup requires Python 3.10 or newer and a free Gemini API key from Google. There is no Docker requirement: Qdrant runs embedded directly on your machine. Installing the Python dependencies, configuring the API key in a .env file, placing your documents in the source folder, and running the three scripts in sequence is the full setup process. The tool is aimed at developers who need a reliable, low-cost Q&A layer over a stable knowledge base and want deterministic behavior rather than generated responses.

Copy-paste prompts

Prompt 1
I have a 200-page PDF product manual. Help me run RAGless's prepare_data.py to extract Q&A blocks from it, then ingest and test with the chatbot CLI.
Prompt 2
My RAGless chatbot keeps returning 'no answer found' for valid questions. Show me how to use the --debug flag to inspect aggregation scores and tune the threshold.
Prompt 3
I want to add RAGless to a Python web app so users can ask questions via a REST endpoint instead of the CLI. What changes do I need to make to chatbot.py?
Prompt 4
Explain the answer_id aggregation scoring in RAGless and how summing scores from multiple question variants makes retrieval more reliable than top-1 search.

Frequently asked questions

What is ragless?

A document Q&A system that uses AI only during setup to create answer blocks, then answers questions at runtime via fast local vector search with zero AI calls, zero hallucinations, and near-zero cost.

What language is ragless written in?

Mainly Python. The stack also includes Python, Qdrant, Gemini API.

What license does ragless use?

No license information was mentioned in the README.

How hard is ragless to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is ragless for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub emilresearch on gitmyhub

Verify against the repo before relying on details.