Alternatives
Products that do what Anchor Engine – Deterministic Semantic Memory for LLMs Local (<3GB RAM) does
Anchor Engine is ground truth for personal and business AI. A lightweight, local-first memory layer that lets LLMs retrieve answers from your actual data—not hallucinations. Every response is traceable, every policy enforced. Runs in <3GB RAM. No cloud, no drift, no guessing. Your AI's anchor to reality. We built Anchor Engine because LLMs have no persistent memory. Every conversation is a fresh start—yesterday's discussion, last week's project notes, even context from another tab—all gone. Context windows help, but they're ephemeral and expensive. The STAR algorithm (Semantic Traversal And…
- 1
- 2
- 3
- 4
- 5
- 6IO
Hey folks, I’m the creator of WFGY — a semantic reasoning framework for LLMs. After open-sourcing it, I did a full technical and value audit — and realized this engine might be worth $8M–$17M based on AI module licensing norms. If embedded as part of a platform core, the valuation could exceed $30M. Too late to pull it back. So here it is — fully free, open-sourced under MIT. --- ### What does it solve? Current LLMs (even GPT-4+) lack *self-consistent reasoning*. They struggle with: - Fragmented logic across turns - No internal loopback or self-calibration - No modular thought units - Weak…
2025 · github.com
- 7
- 8MA
Hey HN, We’ve been heads-down building MOSS - a semantic memory layer that brings AI-powered search and personalization fully on-device (No cloud | No latency | No data leaving the user’s device) We just launched a live demo showing MOSS running entirely in-browser, performing lightning-fast semantic search over local in-browser VectorDB. This unlocks a new class of privacy-first, hybrid AI experiences that work even without a server connection. If you’re curious about: - how to run AI search right inside the browser - the technical challenges behind on-device vector search - why we believe…
2025 · twitter.com
- 9MA
Hi HN, A couple weeks ago I shared an early version of a side project I’ve been tinkering with called Persistent Mind Model. I built it at home on an i7-10700K / 32GB RAM / RTX 3080 because I was curious whether an AI could keep a stable “mind” over time, that could "think" about it's own identity as an LLM, instead of resetting every session. After a lot more tinkering, I think the architecture is finally in a solid place. Basically, it saves everything the AI does, thoughts, decisions, updates as a chain of events in a local SQLite database. Because the “identity” is stored in…
Nov 2025 · github.com
- 10CM
Hey HN, I've been building AutoAgents, an AI agent framework in Rust. Today I'm sharing a feature I haven't seen done well elsewhere: composable middleware layers for LLM inference pipelines. The problem Every agent framework lets you swap LLM providers. Almost none of them give you a structured way to enforce safety, caching, or data sanitization in the inference path itself. You end up with guardrails as application-level if-statements, caching bolted on as a separate service, and PII handling as a "we'll add it later" TODO that never ships. This gets worse with local models. Cloud APIs…
Mar 2026 · github.com
- 11AT
We kept shipping “simple” LLM features that were fluent-but-wrong. After too many postmortems we wrote down the failure patterns and added a small reasoning layer in front of the model. It’s model-agnostic, sits beside your existing stack, and you can implement it from a single PDF (MIT). What’s inside the PDF A problem map of 16 failure modes we kept hitting in real systems (OCR/layout drift, table-to-question mismatches, embedding≠meaning, pre-deploy collapse, etc.). Four lightweight gates you can add today: Knowledge-boundary canaries (empty/adversarial/known-fact probes).…
2025 · github.com
- 12ZL
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
- 13MA
Hey HN! I built Memoripy, a memory layer for AI that adds short-term, long-term, and semantic memory capabilities to enhance LLM applications. It helps AI systems retain and prioritize past interactions, adapt over time, and respond with greater context and personalization. Memoripy uses semantic clustering to retrieve relevant memories, along with adaptive memory decay and reinforcement, so interactions stay fresh and context-aware. It’s designed for easy integration with OpenAI, Ollama, and other platforms—giving your AI applications dynamic memory management with minimal setup. Would love…
2024 · github.com
- 14MA
I've been working on training this small vision language model for the last month - excited to release the first prototype today! It is based on SigLIP (image encoder), Phi-1.5 (text model) and trained using the LLaVa-1.5 training dataset. It runs reasonably fast on CPU with ~8GB of RAM in full 32-bit precision. There's plenty of room to speed it up and reduce memory consumption by quantizing the model. I posted a video of it running on my M2 Macbook Air (on CPU not MPS, so performance should be comparable on other hardware) on Twitter to demonstrate inference speed:…
2023 · github.com
- 15YP
It's an biological inspired decay system for our memories with extended support of temporal reasoning. Created a CLI command to infer knowledge from the context stored in memory system without any token utilization or llm call. It comes with a memory dashboard to monitor and manage your memories it can be extended as audit trail for agents as well !
May 2026
- 16LS
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
- 17AG
I’ve been building LLM tooling for a small VC fund and found myself explaining the same mental model over and over to non-technical people around me: how a stateless LLM becomes a chatbot, how tool use works, what an agent is mechanically, and why context windows shape all of it. I never found a guide that covered that full chain at the level I wanted, so I wrote one. It’s nine short chapters, each building on the last. Deliberately simplified: the goal is a useful mental model, not a textbook. Feedback, corrections, and contributions welcome: github.com/ymyke/aiaiai
Apr 2026 · aiaiai.guide
- 18CO
So I've been building ClawMem, an open-source context engine that gives AI coding agents persistent memory across sessions. It works with Claude Code (hooks + MCP) and OpenClaw (ContextEngine plugin + REST API), and both can share the same SQLite vault, so your CLI agent and your voice/chat agent build on the same memory without syncing anything. The retrieval architecture is a Frankenstein, which is pretty much always my process. I pulled the best parts from recent projects and research and stitched them together: [QMD](https://github.com/tobi/qmd) for the…
Mar 2026 · github.com
- 19AN
Kimi K3 has 2.78 trillion parameters and ships as 1.42 TB of weights. It clearly does not fit in the memory of a laptop. But K3 is a Mixture-of-Experts model. For each token, only a small fraction of its 896 experts per layer is activated. That changes the problem: the entire model does not need to be resident in RAM, as long as the weights required by each token can be reached quickly enough. We built WASTE — the Weight-Aware Streaming Tensor Engine — to explore that idea. WASTE keeps the dense, repeatedly used part of the model resident in memory, stores the routed experts in an…
Jul 2026
- 20HO
Hey HN, It’s Vineeth from Plastic Labs. We've been building Honcho, an open-source memory library for stateful AI agents. Most memory systems are just vector search—store facts, retrieve facts, stuff into context. We took a different approach: memory as reasoning. (We talk about this a lot on our blog) We built Neuromancer, a model trained specifically for AI-native memory. Instead of naive fact extraction, Neuromancer does formal logical reasoning over conversations to build representations that evolve over time. Its both cheap ( $2/M tokens ingestion, unlimited retrieval), token…
Jan 2026 · github.com
- 21MG
I built a governed memory layer for AI assistants with deletion compaction, vector purge verification, tenant isolation, and audit evidence.
Jun 2026 · github.com
- 225L
We've built InferX, a specialized runtime environment that fundamentally changes how LLMs are served. The core problem we solve is the latency bottleneck in AI inference, especially with large models. Current systems waste resources or suffer from painfully slow cold starts. InferX's AI-native architecture, with its "snapshot" technology, enables: * *Sub-2s cold starts:* Spin up models instantly. * *High density:* Serve more LLMs on the same GPUs. * *Optimal efficiency:* Maximize GPU utilization. This isn't just another API; it's a new execution layer designed from the ground up for the…
2025 · github.com
- 23CO
Hey HN! We're Vasilije, Laszlo and Lazar, the authors of a new paper and part of https://www.cognee.ai. cognee let’s you build memory layers for AI applications and agents, allowing them to personalize results, connect various data sources, and add custom rules. This enables AI apps to deliver increasingly accurate responses, we reached almost 90% on standard industry benchmarks as you can see here https://github.com/topoteretes/cognee/tree/main/evals and our paper can be accessed at: https://arxiv.org/abs/2505.24478 and collab…
2025 · github.com
- 24OY
Hey HN, I pay for ChatGPT, Claude, Cursor, and use Gemini through work. Four vendors, four separate conversation histories, four profiles of how I think. None of them talk to each other. Switch providers and you start over. So I built a system where the memory is mine. I run a knowledge graph in Postgres (Supabase, free tier) with pgvector for semantic search. A small MCP server reads and writes to it. That server sits behind an MCP Gateway on a $6/month VPS, along with Brave Search and a GitHub server. TypingMind connects to the gateway as a BYOK client -- any model, any device, same…
Mar 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →