I Don't Need Source Code. I Need Your Help Documentation.
A confession from someone who reverse engineers software for fun — and built a private family legacy platform because the big ones were going to fail my family eventually.
There is a certain kind of person who reads help documentation the way other people read novels.
Not because they're stuck. Not because something broke. They read it because help documentation is a confession. It's the company telling you, in careful, liability-aware language, exactly what the product can and cannot do, what it was designed to assume about you, and where the walls are. Read enough of it and you stop seeing a support article. You start seeing the architecture. The decisions. The trade-offs the engineers made at 2 a.m. before a sprint review.
Give me your help docs. I'll give you back a feature matrix.
Give me a feature matrix and enough time, and I'll build your product.
Not a copy. Something better. Something built for one specific use case that your product was never actually designed to serve.
The Problem With Every Platform You're Already Using
Here's the thing nobody tells you about Facebook, Google Photos, Ancestry, MyHeritage, 23andMe, or any of the other platforms currently holding the most irreplaceable parts of your family's story:
They are not built for your family. They are built for their investors.
Facebook connects your family the same way it connects 3.1 billion other people — by making connection a byproduct of engagement, and engagement a byproduct of outrage. Ancestry is a subscription product owned by a private equity firm. Google Photos will organize your memories with breathtaking accuracy — until Google decides the product no longer fits its portfolio priorities.
These are not accusations. These are business realities. The problem is that what they're supposed to do and what your family actually needs are two different things, and that gap only grows over time.
The Reverse Engineer's Methodology
Reverse engineering a software product — at the feature and architecture level, not the code level — requires exactly three things:
1. The help documentation. Every feature a product has is documented somewhere. Support articles reveal data models. "Known limitations" sections are gold.
2. A feature matrix. List every function, every permission model, every data type. Put them in rows and columns.
3. A specific, honest articulation of what you actually need. Most people skip this step. They let the platforms define the problem space.
What I Actually Needed
I needed a private, controlled place to manage and preserve my family's history. Specifically: medical records and health history, voice recordings, video, person tagging with genealogical integrity, anticipating platform mortality, and security and access control I actually designed.
So I Built It
Private. Controlled. Designed for exactly one use case: my family's legacy, preserved on our terms, not theirs.
Voice recordings with speaker attribution. Video that doesn't get compressed into irrelevance. Medical history tagged to individuals. A genealogical data model that treats people as records, not as social media profiles. Access controls that I designed.
The Part That Still Amazes Me
I built this from help documentation and a feature matrix. No insider access. No leaked specs. No source code. Just a careful reading of what these platforms were willing to tell me about themselves.
Every product you use every day is fully describable from its public documentation. Most people read help docs to fix a problem. A small number read them to understand the system. An even smaller number read them to find the gap — and then fill the gap themselves. That last group builds things.
The Offer
If you're managing your own family's history and you've hit the same walls I hit — platform risk, privacy theater, data models that treat your grandmother as a social media profile — and you're serious about building something real, I'll show you what I built and how I built it.
The platforms you're trusting with your family's history made decisions about what you need before they ever met you. Read their documentation carefully. You'll find out exactly what those decisions were. Then decide if you agree.



