explaingit

skundu42/recallops

Analysis updated 2026-05-18

0PythonAudience · developerComplexity · 4/5LicenseSetup · easy

TLDR

A Python tool that tests AI search pipelines for quality regressions and proves the exact cause using verified counterfactual reruns.

Mindmap

mindmap
  root((RecallOps))
    What it does
      Tests retrieval quality
      Finds root cause of regressions
      Verifies cause with reruns
    Tech stack
      Python
      pgvector
      Qdrant
      Chroma
    Use cases
      CI retrieval gate
      Compare embeddings
      Compare chunkers
    Audience
      RAG developers
      ML engineers

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

Catch retrieval quality regressions in a RAG pipeline before they reach production.

USE CASE 2

Compare embedding models or chunking strategies with a printed cost estimate before running.

USE CASE 3

Get a verified explanation for why a specific search query started failing after a config change.

USE CASE 4

Add a statistically gated retrieval quality check to a CI pipeline.

What is it built with?

PythonpgvectorQdrantChromaLanceDB

How does it compare?

skundu42/recallops0xallam/my-recipe0xhassaan/nn-from-scratch
Stars00
LanguagePythonPythonPython
Last pushed2022-11-22
MaintenanceDormant
Setup difficultyeasymoderatemoderate
Complexity4/52/54/5
Audiencedevelopergeneraldeveloper

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

How do you get it running?

Difficulty · easy Time to first run · 5min

Runs fully offline at no cost by default, vector database and embedding provider extras are optional.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

RecallOps is a Python tool built to catch a specific problem: when teams change how they process documents for AI search systems, called RAG pipelines, like switching embedding models, chunking methods, or rerankers, the quality of search results can quietly get worse. Most tools cannot tell you exactly why that happened, only that something changed. RecallOps is built to answer that question with proof, not guesses. The core idea is verified attribution. When search quality drops, RecallOps does not just point at a likely cause. It reruns the pipeline with only one factor reverted at a time and checks whether the failing search recovers. Only if that test passes does it report the cause as verified. Anything it cannot confirm this way is labeled as a hypothesis instead, kept separate from confirmed causes. To make this possible, RecallOps stores full embeddings, not just references to them, so it can replay past searches and test changes without paying to regenerate embeddings each time. It works by versioning an entire document pipeline, including the documents, how they were split into chunks, the embeddings, and the configuration, using content based identifiers so identical inputs always produce the same result. By default RecallOps runs entirely offline at no cost, using local hash based embeddings and a built in exact search method, with no API keys or servers required. Optional extras add support for vector databases such as pgvector, Qdrant, Chroma, and LanceDB, plus embedding providers including OpenAI, Cohere, Voyage, and sentence transformers. Any operation that would cost money through an external provider prints a cost estimate first and requires explicit confirmation. It also includes a continuous integration testing feature that checks retrieval quality against a set of test queries, using statistical methods designed to avoid false alarms from random noise. The project is aimed at teams building or maintaining RAG based search systems who want a way to test changes safely and understand exactly what broke after an update, backed by evidence rather than assumptions. It is licensed under Apache 2.0.

Copy-paste prompts

Prompt 1
Help me set up RecallOps to test my RAG pipeline's retrieval quality in CI.
Prompt 2
Explain how to use RecallOps to find out why my search results got worse after changing chunkers.
Prompt 3
Show me how to compare two embedding models using RecallOps's compare-embeddings workflow.
Prompt 4
Write a GitHub Actions step that runs recall eval and fails the build on a regression.

Frequently asked questions

What is recallops?

A Python tool that tests AI search pipelines for quality regressions and proves the exact cause using verified counterfactual reruns.

What language is recallops written in?

Mainly Python. The stack also includes Python, pgvector, Qdrant.

What license does recallops use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is recallops to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is recallops for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.