Dev tools · alternatives · 2026

24 alternatives to memory-keeper
99.9% DeepSeek cache hit, 3-tier context proxy
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Prices are shown for the 1 we have checked on their own sites, 1 of them free or with a free tier.
- 1
DeepSeek-V4▲387The open-source era of 1M context intelligence
Apr 2026 · huggingface.co · its alternatives →
- 2

Long-context efficiency with DeepSeek Sparse Attention
2025 · huggingface.co · its alternatives →
- 3

We recently used DeepSeek V4 Flash as a teacher for finance tasks with GPT-OSS-120B. Distillation works well on this problem. At a constrained 8k token budget, our self-distilled 120B scores 83.61% on FinanceReasoning, above Kimi K3 (81.93%) and Inkling (65.13%). We released the 20B open weights. With V4 as the teacher though, we realized it would be timely to measure if the censorship characteristic of it transferred to the distilled version of the base model. tl;dr it didn't, the teacher answered politically sensitive questions 7 SDs differently than expected, but the distilled model's…
Jul 2026 · ctgt.ai · its alternatives →
- 4RG
Hey HN! I'm José, and I built Recall to solve a problem that was driving me crazy. The Problem: I use Claude for coding daily, but every conversation starts from scratch. I'd explain my architecture, coding standards, past decisions... then hit the context limit and lose everything. Next session? Start over. The Solution: Recall is an MCP (Model Context Protocol) server that gives Claude persistent memory using Redis + semantic search. Think of it as long-term memory that survives context limits and session restarts. How it works: - Claude stores important context as "memories" during…
2025 · npmjs.com · its alternatives →
- 5
DSH Desktopfree▲176Official app for DeepSeek’s open-source agent harness
22d ago · deepseek.com · its alternatives →
- 6

Take DeepSeek to the Next Level
2025 · chromewebstore.google.com · its alternatives →
- 7

OpenMemory Chrome Extension: Long-term memory for ChatGPT, Claude, Perplexity, Grok etc - mem0ai/mem0-chrome-extension
2024 · github.com · its alternatives →
- 8BA
Hi HN, Erik here. Today we launch Butter, an OpenAI-compatible API proxy that caches LLM generations and serves them deterministically on revisit. Since April, we’ve been working on this concept of “muscle memory,” or deterministic replay, for agent systems performing automations. You may recall our first post in May, launching a python package called Muscle Mem: https://news.ycombinator.com/item?id=43988381 Since then, the product has evolved entirely, now taking the form of an LLM Proxy. For a deep dive into this process, check out:…
2025 · docs.butter.dev · its alternatives →
- 9

A high performance HTTP proxy cache server and RESTful NoSQL cache server based on HAProxy - jiangwenyuan/nuster
2018 · github.com · its alternatives →
- 10

Simple in-memory Key/Value Store written in Elixir using `cabol/ex_shards` - cabol/kvx
2016 · github.com · its alternatives →
- 11

Vibe profile your ML models to get max performance.
2025 · github.com · its alternatives →
- 12KC
If you’ve ever been curious about how GPT actually works under the hood, I built a small project you might find interesting. I implemented a GPT-style transformer from scratch in a single notebook—covering tokenization, embeddings, causal self-attention, training, and autoregressive text generation without relying on high-level abstractions. The focus was on mechanistic clarity rather than scale or performance, and the notebook is structured to read more like a technical walkthrough than an experiment log. Feedback from people who’ve built or studied transformers would be very welcome.
May 2026 · pythongiant.github.io · its alternatives →
- 13

Fast(est), sharded Go cache with lock-free reads, self-adaptive SieveTinyLFU, batched async writes and HTTP middleware. - unkn0wn-root/kioshun
2025 · github.com · its alternatives →
- 14

A simple re-implementation of Google's sparsehash as a learning excercise. - qpfiffer/Simple-Sparsehash
2015 · github.com · its alternatives →
- 15
memories.sh▲50One layer for memories, skills, and rules across any agent
Feb 2026 · memories.sh · its alternatives →
- 16

Fast PUT/GET/DELETE in-memory key-value store for lookaside caching - jonhoo/cucache
2015 · github.com · its alternatives →
- 17

High-performance cache policies and supporting data structures for Rust systems, with optional metrics and benchmarks. - OxidizeLabs/cachekit
Jan 2026 · github.com · its alternatives →
- 18CC
If you had to build a context window manager in 24h, would you stick to the existing model or come up with something better? Here's what I did: 1. Built a proxy that intercepts Codex's calls to OpenAI and rewrites them on the fly. 2. Replayed 3,807 rounds of SWE-bench Verified traces through it: avg prompt 44k → 6k tokens (-87%). 3. Posted it to HN to get the next reduction applied to my confidence interval — starting with the inevitable "How about accuracy?" npx -y pando-proxy · github.com/human-software-us/pando-proxy
Apr 2026 · npmjs.com · its alternatives →
- 19

Raymond here from Butter.dev, an LLM response cache built as a chat-completions proxy. Today we're launching a key feature for the platform: the ability to generalize on dynamic, templated inputs. Caching at the HTTP request level has the obvious problem of generalizability. Nearly no request is identical, due to templated variables (like names) and metadata (like timestamps), so exact-match cache lookups rarely hit. We solve this at Butter by using LLMs to detect dynamic content in requests and derive their inter-relationships, allowing the cache entry to be stored as a template + variables…
Jan 2026 · blog.butter.dev · its alternatives →
- 20

Cuts your LLM API costs by 40-70%. One line of code.
May 2026 · semanticguard.dev · its alternatives →
- 21

A comprehensive caching and performance plugin for WordPress
2017 · poweredcache.com · its alternatives →
- 22

Hey HN, we’re the developers of OpenLake, an open source storage engine for offloading LLM KV caches from GPU memory into a shared tier of RAM and NVMe. We built OpenLake because KV caches are outgrowing GPU memory. A single 256K token conversation on Gemma 4 31B produces approximately 43GB of KV state, more than half the memory of an 80GB H100. The problem becomes even harder across a cluster: a prefix cached on one GPU host is unavailable when the next request lands on a different GPU, forcing the new GPU to repeat work the fleet has already completed. Once the KV cache is offloaded,…
Jul 2026 · github.com · its alternatives →
- 23

Why advCache? Throughput: 160–170k RPS locally; ~250k RPS sustained on 24‑core bare‑metal with a 50GB cache. Memory safety: 1.5–3GB overhead at 50GB (no traces); ~7GB at 100% OTEL sampling. Hot path discipline: zero allocations, sharded counters, per‑shard LRU, TinyLFU admission. Control plane: runtime API for toggles (admission, eviction, refresh, compression, observability). Observability: Prometheus/VictoriaMetrics metrics + OpenTelemetry tracing. Kubernetes‑friendly: health probes, config via ConfigMap, Docker image.
2025 · borislavv.github.io · its alternatives →
- 24

A Python Library for Efficient LLM Query Caching
2024 · github.com · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →