A spine, laid once
Underneath Docusift, Memoria and Lekha is the same substrate — the same encrypted per-customer configuration, the same approach to authentication and rate limiting, the same shape of error handling, the same durable formats. When we start a new product, most of that arrives for free. The new thing inherits a standard instead of reinventing one, badly, under deadline.
This is the practical answer to an obvious worry: how can a small team hold several products to a high bar? The honest answer is that they are not held up independently. They rest on shared bones. Fix a weakness in the foundation and every product standing on it gets stronger at once — and that leverage is the whole reason one hand can make several things without the quality thinning out.
Shared foundations, not shared fate
Sharing a spine is not the same as sharing a fate. The foundation is common; the economics are not. Docusift has to earn its keep with finance teams. Lekha has to earn its keep with small manufacturers. Memoria has to earn its keep in the household. Each product stands or falls on its own merits and its own unit economics — the family gives it a backbone, it does not prop it up.
We are deliberate about the line. What propagates across the family is infrastructure and standard — security, formats, the privacy substrate. What does not propagate is a product's own logic, its market, or its right to exist. A weak product does not get carried by strong siblings; it gets fixed or it goes. That discipline is what keeps a family of products from becoming a euphemism for spreading ourselves thin.
The privacy substrate everything inherits
The most important thing the family shares is where configuration lives. Every product reads its runtime settings — integrations, model providers, retention, data flows — from a per-customer encrypted store, not from a global switch an operator can flip. That pattern is not re-decided per product; it is the substrate, and a new surface that cannot be expressed as per-customer configuration gets sent back to design before any code is written.
So the privacy promise is not repeated three times and hoped for three times. It is one architectural decision that each product inherits by standing on the foundation. That is the deeper meaning of one origin: not one marketing story stretched over several logos, but one set of load-bearing decisions that every product is built to obey.