One Swiss Knife in the exact shape of your life.

Use cases

Family Tree (where it earns its place)

On Family Tree:

Somebody in every family is the one who remembers — which great-aunt married which farmer, who emigrated and why. The Family Tree makes you that somebody, gently: each person gets a name, their relation to you, when they were born, and a space for the stories and notes that are the actual treasure. … On this page: three concrete ways the person who actually remembers birthdays reaches for the Family Tree, and the signals that tell you it fits.

When the Family Tree earns its place

As a tracker, the Family Tree keeps name, relation, born, and stories & notes — no more, no less — so the record is small enough to actually read back.

Most tools in this category, folk at $288 a year, or $30 a month and Mesh (formerly Clay) at $120 a year, or $20 a month, solve a version of the same problem, then bill you for the privilege of remembering it. The Family Tree takes the opposite bargain: one file, once, kept.

Three scenarios drawn from family, and personal

The everyday one: you open the Family Tree on a Tuesday morning, log what needs logging, and close it. Two minutes. The record is more honest than the app that pinged you to remind you.

The specific one: the everyday task it's built to hold, day to day — the workflow it names is the record that most needs a home outside a subscription. Some people use only the Family Tree. Some fold it into a Swiss Knife next to five others. Both are correct.

The out-of-band one: months later, you want to look back. The Family Tree still opens because it is a file. There is no login lapsed, no export deadline missed. The record is where you left it.

Signals it fits the person who actually remembers birthdays

You want a relationship log that behaves like a document, not a service. You are comfortable typing your own numbers in. You would rather own the file than rent the log. Weight in the knife: 1. Manual: no manual — the tool is its own instructions.

Signals it fits

Questions people ask

01

How do I start recording my family history?

Start with the people you can ask. Add a row per relative — name, relation, birth date — and then get them talking while you fill the stories field. The dates are the skeleton; the anecdotes are the person.

02

Is this a full replacement for folk?

For the working core of what most people use it for — keeping name, relation, born, and stories & notes — yes. For personal CRM, per seat, no. The Family Tree is deliberately smaller and more honest about its scope.

03

Who is the Family Tree not for?

The person who actually remembers birthdays's opposite: a team that needs shared cloud state, or someone who wants automation over ownership. Use a SaaS for that; use this for the file.

A relationship log that opens where you left it, on the machine you left it on.

Other angles on Family Tree