Milestones, ecosystem launches, and source-backed adoption signals behind XMemo.
2026-06-29 · launch · self-reported
XMemo adds Own Database storage for AI memory
Teams can keep XMemo's hosted recall layer while routing memory data to their own PostgreSQL or Supabase database.
What happened
XMemo added Own Database storage for AI memory. Users can register a PostgreSQL-compatible database, including Supabase, verify the connection, initialize the memory schema through an explicit setup flow, and choose whether new memories are written to XMemo Cloud or to their own database.
Why it matters
AI memory is long-lived project context: decisions, preferences, handoffs, and agent activity that should remain portable and governable. Own Database gives teams more control over where that memory data lives while preserving XMemo's hosted recall, search, and multi-agent coordination experience.
How it works
The hosted XMemo control plane still manages accounts, sessions, policies, setup state, and redacted diagnostics. The memory data plane can route to XMemo Cloud or to the user's selected PostgreSQL or Supabase backend after verification and activation.
Setup and sync boundaries
Database setup is explicit: users review connection status, dry-run initialization, apply migrations, and activate the backend before new writes move to Own Database. Existing memories are not silently moved. XMemo provides manual Cloud-to-database and database-to-Cloud sync previews with conflict review before applying changes.
Source note
This is a self-reported XMemo product update based on the implemented Storage settings, backend routing, Supabase setup, and manual sync flows. Own Database is a storage ownership feature; it is not a zero-knowledge, end-to-end encryption, or silent automatic migration claim.
XMemo Stories