AI · alternatives · 2026
24 alternatives to Rekal – Long-term memory for LLMs in a single SQLite file
I got tired of repeating myself to my LLM every session. rekal is an MCP server that stores memories in SQLite and retrieves them with hybrid search (BM25 + vectors + recency decay). One file, local embeddings, no API keys.
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Local persistent memory store for LLM applications including claude desktop, github copilot, codex, antigravity, etc. - CaviraOSS/LongMemory
Dec 2025 · github.com · its alternatives →
- 2
Your memories, in every LLM you use.
2025 · mcp.supermemory.ai · its alternatives →
- 3
Reor is an open-source AI note-taking app that runs models locally. The four main things to know are: 1. Notes are connected automatically with vector search. You can do semantic search + related notes are automatically connected. 2. You can do RAG Q&A on your notes using the local LLM of your choice. 3. Embedding model, LLM, vector db and files are all run or stored locally. 4. Point it to a directory of markdown files (like an Obsidian vault) and it works seamlessly alongside Obsidian. Under the hood, Reor uses Llama.cpp (node-llama-cpp integration), Transformers.js and Lancedb to power…
2024 · github.com · its alternatives →
- 4
This is a small library for giving an agent persistent memory without running any infrastructure. The whole store is one SQLite file, and the default install has no dependencies. I built it because whenever I wanted an agent to remember a handful of facts across sessions, the options were a hosted API, a vector database, or a framework, and that felt like too much for what is usually a few thousand short strings. The part I find most useful is that recall is deterministic, so you can write unit tests that assert what your agent remembers and run them in CI. I haven't seen that elsewhere and…
Aug 2026 · github.com · its alternatives →
- 5
An OKF-backed Model Context Protocol (MCP) server delivering persistent long-term memory and SQLite FTS5 search for AI agents. - fellowgeek/mcp-memory
Aug 2026 · github.com · its alternatives →
- 6
Built this for my LLM workflows - needed searchable, persistent memory that wouldn't blow up storage costs. I also wanted to use it locally for my research. It's a content-addressed storage system with block-level deduplication (saves 30-40% on typical codebases). I have integrated the CLI tool into most of my workflows in Zed, Claude Code, and Cursor, and I provide the prompt I'm currently using in the repo. The project is in C++ and the build system is rough around the edges but is tested on macOS and Ubuntu 24.04.
2025 · github.com · its alternatives →
- 7
PMB▲211PMB gives Claude Code, Cursor, Codex and Zed a real memory. Decisions, lessons and facts in one SQLite file on your disk. Offline, no API keys, no cloud.
Jun 2026 · pmbai.dev · its alternatives →
- 8
OpenMemory MCP▲379Sync memory across AI's so they pick up where you left off.
2025 · mem0.ai · its alternatives →
- 9
Rememberall▲201Open source solution for long term memory for LLMs
2024 · github.com · its alternatives →
- 10
I have a proposal that addresses long-term memory problems for LLMs when new data arrives continuously (cheaply!). The program involves no code, but two Markdown files. For retrieval, there is a semantic filesystem that makes it easy for LLMs to search using shell commands. It is currently a scrappy v1, but it works better than anything I have tried. Curious for any feedback!
Apr 2026 · github.com · its alternatives →
- 11
DeltaMemory▲104Most AI agents forget everything between sessions. We built DeltaMemory to fix that. It's a cognitive memory layer that gives agents persistent recall, automatic fact extraction, and temporal reasoning — via a single SDK call. Key numbers: - 89% accuracy on LoCoMo long-term conversation benchmark - 50ms p50 retrieval latency - 97% cost reduction vs raw token re-processing Open source SDKs, works with any LLM stack. Currently in early access. Happy to answer questions about the architecture, benchmark methodology, or how we handle knowledge graphs.
Feb 2026 · deltamemory.com · its alternatives →
- 12LS
Hi HN, I built llm.sql, an LLM inference framework that reimagines the LLM execution pipeline as a series of structured SQL queries atop SQLite. The motivation: Edge LLMs are getting better, but hardware remains a bottleneck, especially RAM (size and bandwidth). When available memory is less than the model size and KV cache, the OS incurs page faults and swaps pages using LRU-like strategies, resulting in throughput degradation that's hard to notice and even harder to debug. In fact, the memory access pattern during LLM inference is deterministic - we know exactly which weights are needed…
Apr 2026 · its alternatives →
- 13
- 14
- 15
I keep running in the same problem of each AI app “remembers” me in its own silo. ChatGPT knows my project details, Cursor forgets them, Claude starts from zero… so I end up re-explaining myself dozens of times a day across these apps. The deeper problem 1. Not portable – context is vendor-locked; nothing travels across tools. 2. Not relational – most memory systems store only the latest fact (“sticky notes”) with no history or provenance. 3. Not yours – your AI memory is sensitive first-party data, yet you have no control over where it lives or how it’s queried. Demo video:…
2025 · github.com · its alternatives →
- 16
Markdown based AI agent memory with semantic search, hybrid retrieval, and offline-first sync between agents. - sqliteai/sqlite-memory
Apr 2026 · github.com · its alternatives →
- 17
The Universal Cross-Model Episodic Memory Standard. Local-first, project-scoped SQLite memory engine for Google Antigravity, Claude Code, Cursor, and Windsurf. Zero cloud lock-in. - timgordontg/engrim
Sep 2026 · github.com · its alternatives →
- 18
Local-first AI memory layer for any LLM. Persistent knowledge graph, entity extraction, semantic retrieval. Works with Ollama, OpenAI, Anthropic, or any OpenAI-compatible backend. - zaydmulani09/mnemo
Jun 2026 · github.com · its alternatives →
- 19BA
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 →
- 20ZL
Zep is a long-term memory store designed for conversational AI applications built using modern LLMs. It handles the storage, summarization, embedding, indexing, and enrichment of chat histories, and offers developers a simple, low-latency API to this data. Chat history storage is an infrastructure challenge all developers and enterprises face as they look to move from prototypes to deploying conversational AI applications that provide rich and intimate experiences to users. Key features include long-term memory persistence, auto-summarization, vector search, auto-token counting, and Python…
2023 · its alternatives →
- 21
- 22
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 →
- 23
Hey HN! We posted Rivet Actors here previously [1] as an open-source alternative to Cloudflare Durable Objects. Today we've released SQLite storage for actors (Apache 2.0). Every actor gets its own SQLite database. This means you can have millions of independent databases: one for each agent, tenant, user, or document. Useful for: - AI agents: per-agent DB for message history, state, embeddings - Multi-tenant SaaS: real per-tenant isolation, no RLS hacks - Collaborative documents: each document gets its own database with built-in multiplayer - Per-user databases: isolated, scales…
Feb 2026 · github.com · its alternatives →
- 24RA
Hi HN, we are the founders of Relari (https://www.relari.ai). We launched our LLM evaluation stack on HN a few months ago (https://news.ycombinator.com/item?id=39641105), which is now used in production by AI teams at companies like Vanta and PwC. We have since expanded to directly optimizing parts of an LLM pipeline using a data-driven approach. In particular, we see a lot of potential in the Auto Prompt Optimization—which could be an attractive alternative to fine-tuning in many cases—to use data to align LLMs for domain-specific tasks. Here’s a demo video:…
2024 · its alternatives →
Also compare
- A local-first memory store for LLM agents (SQLite) alternatives
- Universal Memory MCP alternatives
- Reor – An AI note-taking app that runs models locally alternatives
- Remembrane – agent memory in one SQLite file, zero dependencies alternatives
- MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5 alternatives
- Yet another memory system for LLMs alternatives
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 →