At a glance
The philosophical difference
MemMachine is an open-source memory service that splits its model in two. Episodic memory, the relational context of conversations, lives in a Neo4j graph, while profile data lives in SQL. Retrieval walks the graph to reconstruct who said what to whom. It emphasizes token efficiency and works across LLM providers, including AWS Bedrock. Worlds stores relational structure too, but as RDF triples in an append-only ledger. The difference is where structure comes from. MemMachine derives context from conversation logs after the fact; Worlds accepts only facts you assert deliberately. Every fact in Worlds carries a path to its source and a point on the ledger’s timeline. The token-efficiency claim is worth weighing honestly. MemMachine reports using fewer tokens than comparable services. Worlds answers the same question with a different currency: exactness. A SPARQL query returns a deterministic result rather than a retrieved context window.When Worlds fits
- Facts must be true against a source of record, not derived from conversation logs.
- You want to query relationships deterministically instead of walking a reconstructed graph.
- You need to know when a fact changed and who asserted it.
- You want provider-agnostic LLM and embedding choices, including AWS Bedrock (provider-agnostic).
When Worlds does not fit
- You want episodic memory reconstructed from conversation logs, with no fact curation. Worlds ingests unstructured text but does not extract graph facts automatically (update).
- You want a memory service native to AWS operations, such as IAM-based access and Bedrock-managed storage.
- Context-window token cost is the binding constraint and you want the memory layer to minimize it.