AutoTreeGen
A research instrument

The library
of your
lineage.

AutoTreeGen is a working archive for serious genealogy. Every name, every date, every DNA segment is bound to a citation, a confidence score, and a chain of provenance you can defend in print.

230,000+people · platform testing
20DNA kits — all relatives, all consenting
QUAY 1–3citation grades
The thesis

Genealogy is not a hobby. It is the guesswork evidence we owe to the people who came before us — and the ones who come after.

No. 01

Cite, or it didn't happen.

Every fact traces back to a source — a parish register, a census line, a centiMorgan segment. Unsupported claims are stored separately, as hypotheses.

QUAY 1 · 2 · 3
No. 02

Disagreements are versioned, never overwritten.

Two cousins, two birth years, two scribes' hands. The archive keeps all of them. Confidence is computed, not asserted, and updates with new evidence.

audit trail · permanent
No. 03

Paper and DNA, in one workspace.

Y-DNA, mtDNA, autosomal cM segments and your scanned records sit in the same tree. The engine reads both at once.

Any GEDCOM · strict
The archive

An archive that thinks in centuries.

Fig. 01

Eight lineages, four generations, one diagram.

The signature ribbon-tree: each branch carries its lineage colour from root to tip, with portraits attaching where photographs survive.

Fig. 02

Confidence as a number, not a feeling.

The hypothesis engine scores every proposed link and shows which evidence raises it and which lowers it.

Fig. 04

QUAY-graded provenance.

Sources are graded on a 1–3 scale. A link is confirmed only at QUAY 2 or higher.

Fig. 05

Y, mt, and autosomal in one view.

Three evidence streams — paternal line, maternal line, recent cousins — overlay on the same tree.

Do not build trees of names. Build trees of evidence.
— the founder

No fact without a source.

Every name, date and DNA segment is bound to a citation, a confidence score and a provenance trail you can audit — and defend.

See it work

Eight engines, one workspace.

Pick an engine to watch it run on a sample tree — the names and places are synthetic.

GEDCOM Doctor
# GEDCOM Doctor · read family.ged✓ parsed 41,208 persons · UTF-16 → UTF-8▲ 37 broken FAMS links · 12 duplicate persons✓ merged Müller/Mueller · parents + sources keptrepaired · nothing lost · reversible
Claim under auditRejected

Helga Vogt is recorded as the mother of Klara Müller.

autosomal · 0 cM shared, ~3,400 expected mother–child−0.62
autosomal · 1,540 cM across a known descendant pair+0.30
baptism register 1849 · names Margarethe Weiss+0.80

Timeline impossible and DNA excludes maternity. Claim removed from the canonical tree, kept in the audit trail. Suggested correction — mother is Margarethe Weiss.

Evidence graph
Klara MüllerMargarethe WeissHelga VogtHans MüllerL. Kovač?DNA
ConfirmedProbableHypothesisConflictDNA support
Working in the background

Your evidence, being assembled.

DNA kitsComputing
Hypotheses trackedComputing
Conflicts openComputing
Sources gradedComputing
Methodology

From GEDCOM and DNA to a defensible tree.

i

Import

Drop any GEDCOM file — from Ancestry, MyHeritage, Geni, any version, any size. We parse it strictly and tell you which records bend the spec.

Any GEDCOM · any size
ii

Match

Add Y, mt and autosomal kits, or your exports from Ancestry, MyHeritage and GEDmatch. Each kit becomes its own evidence stream.

cM · segments · haplogroups
iii

Hypothesise

The engine proposes parent–child links, scores them, and records the evidence both for and against.

confidence ∈ [0, 1]
iv

Cite

A finding is confirmed only with at least one QUAY-graded source.

QUAY 2+ to confirm
Why AutoTreeGen

What the engine actually does.

It checks the evidence

Every proposed link is scored against the records and DNA behind it; anti-fantasy detectors flag the fabricated and the over-reached.

It keeps the chain of sources

Each fact stays bound to its citation — parish register, census line, DNA kit — graded QUAY 1 to 3.

It accounts for DNA

Y-DNA, mtDNA and autosomal cM read alongside the paper trail, with endogamy weighed in so shared segments are never over-read.

It tracks conflicting hypotheses

When sources disagree, both are kept and versioned. Confidence is computed from the evidence, never overwritten.

It generates research reports

Findings, evidence and open questions compile into a defensible report you can export.

Pricing

Plans built around evidence, not vanity

Three plans — Free, Pro and Premium. Free is a real working tier: a tree, 5,000 people, the GEDCOM Doctor and the Anti-Fantasy detector, no card required. Pro and Premium add full DNA and the advanced engines. Capability is the contract.

2 months free
Carved oak medallion — Free plan
Free
Carved oak
Open a tree, read the record, see what’s there.
$0 USD forever
Polished silver medallion — Pro plan
Pro
Polished silver
Merge matches, resolve conflicts, grow the tree.
$290 USD/yr
2 months free
FAQ

Questions, answered plainly.

What file formats can I import?

Any GEDCOM — from Ancestry, MyHeritage, Geni or any other tool, any version. We parse it strictly and flag the records that bend the spec.

Is my DNA data safe?

DNA is special-category data: encrypted at rest, never used to train models, and processed only under your explicit consent. You can delete it at any time.

How is confidence calculated?

Every claim is graded on its evidence — sources scored QUAY 1 to 3, DNA weighed against the expected range, agreement between records. Confidence is computed, not asserted.

Can I export my tree?

Yes. Your tree exports back to GEDCOM, and its findings compile into a PDF research report.

Is it available now?

The methodology and worked examples are public today. Entry opens at launch.

Get started

See the proof behind your own tree.

Every claim on this platform carries a status, a confidence, and a source. Start with the method behind it, and a worked example.

DNA is special-category data — encrypted at rest, never used to train models, handled under explicit consent. The details live in the privacy notice.