MeYou
BUILT WITH TENANTSDB /
MeYou
MeYou
An AI companion with permanent memory, in development. Every person's companion keeps its memories, context, and history in data that belongs to them alone.
Built with TenantsDB
VIA TENANTSDB
pg · mongo · redis
WEB
meyou.ai
THE PROBLEM
A companion's memory belongs to one person only
An AI companion remembers conversations, preferences, relationships, and years of shared history. That is the most intimate dataset a consumer product can hold. MeYou's memory is not a flat index but a knowledge graph, entities and relationships built up over time, and a graph makes shared storage structurally dangerous: one missed filter on one edge of a graph walk is enough to surface a piece of someone else's life.
For that data, a tenant_id column is not a boundary. The boundary has to be the database itself. MeYou is in fact where this whole platform started: TenantsDB was born from MeYou's need to give every user their own physically separate database.
HOW IT USES TENANTSDB
Designed on per-user isolation from the first line
MeYou is being built on a database-per-user model. Each person's companion holds its memory graph in its own physically isolated databases, so a recall can never cross into another person's data, because that data lives somewhere else entirely. Long-term memory runs on LeapMemory, which provisions each user's MongoDB and Redis through TenantsDB, the same foundation as every product on this page.
The product is in development, but the architecture decision is already made and already running underneath: isolation first, then features on top. When MeYou ships, its trust story will not be a policy page. It will be the infrastructure itself.