Add /vs/mem0 comparison page - #235
Closed
jy7lsna wants to merge 2 commits into
Closed
Conversation
Contributor
|
@jy7lsna is attempting to deploy a commit to the Statewave Team on Vercel. A member of the Team first needs to authorize it. |
Mem0 rewrote its OSS migration page on 2026-08-05 (mem0ai/mem0#6808), retitling the graph section from entity linking as the OSS successor to Platform-only graph memory, separate from entity matching. No code changed, only the label - but the page's claim was built on that label. - Table row (Graph / relationship memory): split OSS vs Platform behavior instead of naming entity linking as an OSS graph successor. - Footnote: replaced with claims checkable against deleted code, config surface, and response shape (graph_store config removed, relations field no longer returned, no graph payload in Platform responses) instead of Mem0's shifting terminology. Source: mem0ai/mem0 docs/migration/oss-v2-to-v3.mdx at 3f717e5.
smaramwbc
pushed a commit
that referenced
this pull request
Aug 10, 2026
Four page and content additions, landed together: - /benchmarks — LoCoMo and LongMemEval results for Statewave, mem0 cloud and mem0 OSS, run in-harness with a shared gpt-4o judge; numbers trace to the statewave-memory-benchmarks repo. - /vs/mem0 — comparison page: deterministic, token-bounded context assembly with policy enforcement and receipts vs. ranked similarity retrieval. - /use-cases/grounded-shop-assistant — use-case page for the grounded shop assistant reference build (links smaramwbc/statewave-grounded-shop-assistant). - Custom header and OG images for all five blog posts. Combined from PRs #226, #228, #235 and #239 (see those PRs for the full per-change history and discussion).
18 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a
/vs/mem0comparison page: deterministic, token-bounded context assembly with policy enforcement and integrity-hashed receipts vs. Mem0's ranked similarity retrieval. Covers the retrieval/governance/ops capability gap, a worked support-agent example, LoCoMo + LongMemEval benchmark results measured on Mem0's own harness, a Mem0 → Statewave migration table, and FAQ.
Related Issue
N/A — new marketing/comparison page, not tied to an existing issue.
Type of Change
Changes Made
StatewaveVsMem0Pageat/vs/mem0: hero, capability gap, ranking-signal breakdown, full comparison table, worked example, governance/receipt section, LoCoMo + LongMemEval benchmark charts,Mem0→Statewave migration guide, FAQ, closing CTA.
App.tsx), footer nav (Footer.tsx), and sitemap/SEO metadata (seo-meta.ts).--series-statewave,--series-mem0-cloud,--series-mem0-oss) and a.section-glow--softambient-glow variant toindex.css, reused by the LoCoMo bars and the kind-priority bars on this page instead of gradient fills.
/vs/mem0renders.Testing
Test Commands Run
npx tsc --noEmit -p . npx vitest run tests/routes.test.tsxChecklist
Additional Notes
Benchmark figures cited (LoCoMo 0.905 Statewave vs. 0.899 mem0 cloud / 0.866 mem0 OSS; LongMemEval 0.933 mem0 cloud / 0.833 mem0 OSS; 8/8 vs. 2/8 support eval) are measured on Mem0's own harness
see
statewave-memory-benchmarksrepo linked from the page's reproduce-it section. Nominative use of the "mem0" name is disclaimed in the page footer.