gitwtfhub

wtf is cache-pot?

subh05sus/cache-pot — explained in plain English

Analysis updated 2026-05-18

2GoAudience · developerComplexity · 2/5LicenseSetup · easy

TL;DR

Cache-Pot is a Redis-compatible, single-binary in-memory store with built-in vector search and a semantic cache for reusing AI model answers.

Mindmap

mindmap
  root((cache-pot))
    What it does
      Redis compatible store
      Vector search built in
      Semantic answer cache
      Native MCP endpoint
    Tech stack
      Go
      RESP2 protocol
      Single binary
    Use cases
      Drop-in Redis replacement
      Trim model API bills
      Agent memory via MCP
    Limits
      No clustering
      No replication
      Single machine focus

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

Why would anyone build with this?

REASON 1

Replace a Redis cache with Cache-Pot in an existing app to add vector search without extra infrastructure.

REASON 2

Cache AI model answers by meaning so similar questions reuse a stored response instead of a new API call.

REASON 3

Give an AI agent like Claude direct read, write, and search access to a cache through its built-in MCP endpoint.

What's in the stack?

GoRESP2Docker

How it stacks up

subh05sus/cache-potanomalroil/1keyanshuman852/dasan-router-cli
Stars222
LanguageGoGoGo
Last pushed2019-05-17
MaintenanceDormant
Setup difficultyeasymoderatemoderate
Complexity2/53/53/5
Audiencedeveloperops devopsops devops

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

How do you spin it up?

Difficulty · easy Time to first run · 5min

Semantic cache feature needs an embeddings provider such as a local Ollama or an OpenAI API key.

BSD-3-Clause license: use freely, including commercially, as long as you keep the copyright notice and do not use the author's name to promote derived products without permission.

Wtf does this do

Cache-Pot is an in-memory data store built to work like Redis, but designed around how AI applications and agents actually use a cache. It speaks the same wire protocol as Redis, so an existing Redis client and the code around it keep working untouched once you point it at Cache-Pot instead. What sets it apart from plain Redis is that vector search and a semantic cache are built in rather than added on. You can store vectors and search for the nearest matches directly, which is useful for things like similarity search over documents. The semantic cache lets you save a model's answer to a question once, and later, when a similar but not identical question comes in, Cache-Pot can return the saved answer instead of paying for another call to the model. There is also a native connection for AI agent tools called MCP, so agents such as Claude can read, write, search, and remember through Cache-Pot directly as a tool, without extra glue code. The whole project ships as one self contained binary with no other services to install, and it includes a small web dashboard for watching what is happening inside the store. You can install it with Go, run it through Docker, or build it from source, and once it starts it listens on the usual Redis port as well as a separate port for the dashboard. A built in command line shell lets you talk to it even if you do not have the standard Redis client tools installed. The project is honest about its limits: there is no clustering, replication, or failover, and it is not tuned to beat Redis on raw speed. It is meant as a single machine cache and AI data layer, not a replacement for a large production Redis cluster.

Yoink these prompts

Prompt 1
Install and run Cache-Pot with Docker, then point our existing Redis client at it and verify basic SET and GET work.
Prompt 2
Set up a semantic cache in Cache-Pot for our chatbot so similar questions return the same stored answer.
Prompt 3
Show me how to store and search vectors in Cache-Pot using VSET and VSEARCH.
Prompt 4
Connect Cache-Pot's MCP endpoint to Claude so it can read and write cache entries as a tool.

Frequently asked questions

wtf is cache-pot?

Cache-Pot is a Redis-compatible, single-binary in-memory store with built-in vector search and a semantic cache for reusing AI model answers.

What language is cache-pot written in?

Mainly Go. The stack also includes Go, RESP2, Docker.

What license does cache-pot use?

BSD-3-Clause license: use freely, including commercially, as long as you keep the copyright notice and do not use the author's name to promote derived products without permission.

How hard is cache-pot to set up?

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

Who is cache-pot for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.