Weave

Git for genealogy.

The problem

Every genealogy tool forces the same bad choice: share one tree and watch careful work get overwritten, or fork and never reconcile again. Families stop collaborating the moment a second serious maintainer shows up. Private family archives stay unshared because existing tools force someone to surrender authority.

How Weave is different

Two maintainers keep their own sovereign trees. When one has a contribution for the other — a new fact, a correction, a document — they offer it. The recipient accepts, rejects, or branches. Nothing is auto-applied. Source attribution follows every fact across every boundary.

It's the same model that lets thousands of engineers collaborate on Linux without a single authoritative maintainer. Applied to the thing that actually matters.

What's preserved

• Sovereignty — no "master" tree
• Source attribution across merge boundaries
• Privacy tiers — living-person data can be blocked from crossing
• Full history of every offer, accept, reject, branch

Demo video coming soon

← Back to features