One place for your family's records

Wholekin

Back to comparisonsComparison and positioning

Like a CMDB, but for your household

For technical readers, a CMDB is the closest analogy. Wholekin plays a similar role for a family — connecting people, things you own, documents, and how they relate.

Wholekin vs CMDB
If you've worked with a CMDB (Configuration Management Database), the structure will feel familiar: people, things, owners, documents, and history connected in one place.
A CMDB for your family.
One place for who owns what, the supporting documents, and what's changed.
A real record, not a fancy inventory app.

What makes that category valuable 01

A CMDB connects assets, owners, dependencies, and history in one place.

What makes that category valuable 02

It gives you a single reference instead of relying on spreadsheets and memory.

What makes that category valuable 03

Handoffs are easier because the context outlives the original owner of the record.

Where the analogy breaks down
Why it is similar, but not the same
  • A CMDB is built for infrastructure and services, not family members or household documents.

  • The asset is the center of the model, not the people around it.

  • It doesn't naturally model family relationships, succession, or shared household care.

Why Wholekin is the stronger fit
Where Wholekin goes further
  • Wholekin uses the same kind of structure, but applied to families.

  • People and relationships are first-class — not just devices or accounts.

  • Structured enough to trust, light enough that you'll actually use it.