THE WRAPPER QUESTION
Most memory products are JSON blobs in a vector store.
A lot of the cynicism here is earned. Plenty of "memory" is a JSON blob in a vector store with a logo on it. Frameworks ship a default vector database, a quick cache that quietly becomes production, no schema, no access control, no audit trail. If that is your reference point for AI Memory, being skeptical is the correct response.
So let us not defend the category. Let us separate from it. The difference between a wrapper and a memory system is the work you cannot see in a demo. It is whether the system resolves entities, whether it handles two facts that contradict each other, whether it knows what is stale, whether it scopes what each agent and each user can read, and whether it forgets on purpose. That is the iterative depth work that is hard to get right, and it is the reason a benchmark number is not just marketing for us. On LongMemEval we are at 92%, and that gap is the difference between memory and a cache with good branding.
If the wrapper criticism makes you check what is actually under the hood, good. That is the check we want you to run.
The proof, in numbers
See the operations a wrapper skips.