AI · alternatives · 2026
24 alternatives to Wolbarg – Local-first shared memory for AI agents using SQLite
hi HN, While building Wolbarg (an open-source shared memory SDK for AI agents), I assumed PostgreSQL would be the obvious choice for memory storage. After benchmarking SQLite under realistic agent workloads, I was surprised by the results. For local-first and single-node deployments, SQLite handled far more than I expected while keeping the architecture much simpler. I wrote up the benchmarks, methodology, trade-offs, and where I still think PostgreSQL is the better choice.
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
I built LocalGPT over 4 nights as a Rust reimagining of the OpenClaw assistant pattern (markdown-based persistent memory, autonomous heartbeat tasks, skills system). It compiles to a single ~27MB binary — no Node.js, Docker, or Python required. Key features: - Persistent memory via markdown files (MEMORY, HEARTBEAT, SOUL markdown files) — compatible with OpenClaw's format - Full-text search (SQLite FTS5) + semantic search (local embeddings, no API key needed) - Autonomous heartbeat runner that checks tasks on a configurable interval - CLI + web interface + desktop GUI - Multi-provider:…
Feb 2026 · github.com · its alternatives →
- 3
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 →
- 4
- 5
In-memory Postgres for unit/E2E tests. Contribute to hexclave/pgmock development by creating an account on GitHub.
2024 · github.com · its alternatives →
- 6
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 →
- 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
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 →
- 9
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 →
- 10
Query Memory▲100One API for all documents your AI agents need
Mar 2026 · querymemory.com · its alternatives →
- 11
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 →
- 12
- 13
A file-based protocol for multi-agent AI workflows — portable, auditable, human-in-command. Cross-agent communication and persistent shared memory across runtimes, projects, and machines. No daemons, no central server.
May 2026 · oacp.dev · its alternatives →
- 14
Hi HN, Been hacking on a simple way to run agents entirely inside of a Postgres database, "an agent per row". Things you could build with this: * Your own agent orchestrator * A personal assistant with time travel * (more things I can't think of yet) Not quite there yet but thought I'd share it in its current state.
Feb 2026 · github.com · its alternatives →
- 15
At JigsawStack.com, we are using Redis by Upstash to store and validate API keys among other datasets for speedy retrieval. As we scaled to more Asian markets and added replicated nodes, the cost started to shoot up while performance got a lot worse. I discovered hosting SQLite on Fly which was crazy fast & cheap with the full power of a relational database but difficult to use and scale without writing tons of code & devops. Then I found Turso as a managed service which is pretty cool but again got really expensive and had to manage a bunch of replications manually and pay per replications…
2024 · dzero.dev · its alternatives →
- 16
Hi HN, we're Kiran and Vijay! Over the past two years, we have built a columnar storage engine for observability: logs, metrics, and traces. Today, it's exciting for us to show what we've built on top of that foundation: LLM Agent Observability. Given how non-deterministic agents are, storing all traces without sampling was critical for us. But these traces tend to be in the MBs, sometimes GBs - we needed to store them inexpensively. We also needed the queries and analyses to be fast. To meet both these goals, we store them in S3 in our own parquet-like file format, and query them using AWS…
Jul 2026 · oodle.ai · its alternatives →
- 17
postgres + sqlite = pglite. Contribute to viggy28/pglite development by creating an account on GitHub.
2024 · github.com · its alternatives →
- 18
I've been working on Polign and built a small prototype around something I've been thinking about with agent memory. I have built a lightweight/stateless vector db + BM25 search which works really well with typed facts and structured queries. It uses your own S3, or GCS bucket as primary storage, and restarting a node is fairly quick. Demo + writeup: https://polign.com/blog-edge-agent-memory Live search demo: https://demo.polign.com Docs: https://polign.com
Aug 2026 · polign.com · its alternatives →
- 19
Hey HN, I just spent the last few weeks building a database for agents. Over the last year I built PostHog AI, the company's business analyst agent, where we experimented on giving raw SQL access to PostHog databases vs. exposing tools/MCPs. Needless to say, SQL wins. I left PostHog 3 weeks ago to work on side-projects. I wanted to experiment more with SQL+agents. I built an MVP exposing business data through DuckDB + annotated schemas, and ran a benchmark with 11 LLMs (from Kimi 2.5 to Claude Opus 4.6) answering business questions with either 1) per-source MCP access (e.g. one Stripe…
Apr 2026 · github.com · its alternatives →
- 20
Shared execution memory for every AI agent in your org
Aug 2026 · semelbase.com · its alternatives →
- 21
CortexDB▲2Single-file AI memory and knowledge graph for agents
Jun 2026 · github.com · its alternatives →
- 22
How it works: - Storage uses one SQLite database file, plus a local LanceDB index of vectors. No need for a server, cloud services, or any API keys. - Retrieval is a hybrid approach using BM25 (rank-bm25) and vector-based search (sentence-transformers) combined with a co-occurrence graph of entities, using reciprocal rank fusion. The idea is to find the right memory, not the closest one. - It plugs into the agent's lifecycle via MCP: before the agent responds, relevant memories are added to its input; after each turn, decisions and new learnings are automatically recorded. No need to…
Jun 2026 · github.com · its alternatives →
- 23
Gomaa — Autonomous Agent Memory OS. Persistent memory system for AI agents with Obsidian vault integration, hybrid RRF search, knowledge graphs, security gates, and MCP server. - M4F-S/gomaa
Aug 2026 · github.com · its alternatives →
- 24
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 →
Also compare
- A local-first memory store for LLM agents (SQLite) alternatives
- LocalGPT – A local-first AI assistant in Rust with persistent memory alternatives
- SQLite Memory – Markdown based AI agent memory with offline-first sync alternatives
- pumaDB alternatives
- I open-sourced the in-memory PostgreSQL I built at work for E2E tests alternatives
- MCP Memory – Fast Agent Memory Using Google's OKF and SQLite FTS5 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 →