Skip to main content
Cache-Pot ships as a single self-contained binary with no external dependencies — no database engine to install, no configuration file required, no companion services to keep running. Choose the installation method that fits your workflow: pull the binary with go install, run a Docker container, or build directly from source.
No external services or databases are required. Once the binary starts, it brings up its own RESP2 server, vector index, semantic cache, MCP bridge, and web dashboard by itself.

Installation methods

If you have Go 1.25 or newer on your machine, go install fetches, compiles, and places the binary in $GOPATH/bin in a single command.
Make sure $GOPATH/bin (usually ~/go/bin) is on your PATH so you can run cache-pot from any directory:
Requires Go 1.25 or newer. Download Go from go.dev/dl if you don’t have it installed.

Verifying the installation

After installation, confirm the binary is available and the server is responding:
If redis-cli returns PONG, Cache-Pot is running correctly and ready to accept connections.

What starts up

When Cache-Pot launches you will see two lines in the terminal output:
Two services start on every run: Both ports are configurable. Pass --addr to change the Redis port, --dashboard-addr to change the dashboard port, or set either to an empty string to disable it:

Next steps

Quickstart

Connect a Redis client, run a vector search, and try the semantic cache in under 5 minutes.

Server configuration

Set up authentication, configure snapshot and AOF persistence, and connect an embeddings provider.