AutoTreeGen - Evidence-First Genealogy Intelligence
Stuck at a brick wall?

AutoTreeGen - Your cousin's DNA holds the next step.
We show you
the branch.

Bring your tree and your DNA matches. AutoTreeGen finds where a cousin's line meets yours and proposes the branch beyond your brick wall, with the evidence behind it.

Upload your GEDCOM
Start with an example. No personal file needed.
250Kpersons per tree on Pro
8audit engines
46languages in the app
Sources stay visibleHypotheses stay labelledYou decide
MyHeritageAncestryFamilyTreeDNAGEDmatch23andMeGeniAutoCluster ZIP+ any GEDCOM file
EXPLORER / The Bennett familyExample tree
Select a person to explore their evidence
Clara Bennett · EvidenceResearch in context
01 · SourcesBirth register, 1889

A cited record, connected to a person.

02 · DNAMaternal lineage

Illustrative lineage, not relationship proof.

03 · ReviewTwo birth years

1889 in a register. 1890 in a census. Both remain visible.

Evidence first. Conclusions second.Fictional demonstration
A workspace for research from different sources
MyHeritageAncestryFamilyTreeDNAGEDmatch23andMeGeniAutoCluster ZIP+ any GEDCOM file
Thousands of DNA matches?

We tell you how each cousin is related to you.

Upload your match list from Ancestry, MyHeritage, FamilyTreeDNA or GEDmatch. AutoTreeGen predicts the relationship from shared DNA, sorts cousins into clusters on your family lines and shows the surnames each cluster carries.

Kit bridges

Two kits see the same person. Your tree shows the branch.

Keep your own DNA kit and your relatives' kits in one AutoTreeGen account. When the same person appears in the match lists of two of those kits, AutoTreeGen shows the bridge and proposes the branch of your tree where that match belongs, as a hypothesis with its evidence.

Diagram: one account with three DNA kits, one person seen by two of them, and the branch of the tree proposed for that person.Clara Lindner's account holds three kits: her Ancestry kit, her father Paul's Ancestry kit and her MyHeritage kit. The match Jonas Brenner appears in both Ancestry match lists, which makes a bridge, and does not appear in the MyHeritage list. Paul's kit is linked to Paul in Clara's tree, so the match is proposed on her father's line.One account, three kitsAncestryyour kitAncestryyour father's kitMyHeritageyour kitnot in this listBridgeJonas BrennerDNA matchYour treeFather's linePaulFatherMartaMotherClaraYou
Illustration with a made-up family. Names, kits and matches are invented.
A look inside

What it looks like inside

Five screens from the platform, drawn with a fictional family. The layout is the product's own.

PortfolioExample
Bennett family4,812 persons
Ward of Norfolk1,206 persons
Reed and Hale638 persons
Every tree in one list, with its paternal and maternal lines at a glance.
DNA kitsExample
Helen BennettReady · 1,284 relatives · 37 clusters
MyHeritageMH-EX4417
AncestryDNAAN-EX20B6
GEDmatchGM-DEMO-731
FamilyTreeDNAFT-DEMO-552
GeniGN-EX0907
One person, five platforms, one joined DNA record.
DNA matchesExample
Margaret Hale142 cM
Thomas Ward88 cM
Ruth Ellison61 cM
Daniel Reed47 cM
DNA matches with their ancestral surnames and the platform they came from.
Kit bridgesExample
214shared people
96with marked lines
12lines that can move
When two kits see the same people, the platform shows where the lines meet.
ToolsExample
  • GEDCOM Doctor
  • Find duplicates
  • Smart matching
  • Hypotheses
  • Reconcile trees
  • Reports
The research tools, one click from any tree.
See it work

Eight engines, one workspace.

An illustration with synthetic data: pick an engine to see the kind of output it produces. Names, places and numbers are invented.

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 keptoriginal file kept · every change reversible
Claim under auditConflict found

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

autosomal · 0 cM shared, 3,330 - 3,720 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 conflicts with maternity. The conflict and its evidence go to the researcher, who decides; the tree changes only on that decision, and the claim stays in the audit trail. Suggested correction - mother is Margarethe Weiss.

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

No fact without a source.

Facts imported with a source keep their citation, a confidence score and a provenance trail you can audit - and defend. Facts without one are marked unsourced, never dressed up as proven.

ConfirmedProbableHypothesisConflictRejected

Your tree. Your evidence. Your DNA. Your decisions.

The AutoTreeGen approach

A connection is the beginning. Not the proof.

  1. 01

    Bring your research.

    Start with your GEDCOM. Add the records and DNA evidence relevant to your research.

  2. 02

    Follow the evidence.

    Explore people, sources and possible relationships together, rather than in separate silos.

  3. 03

    Keep the disagreements.

    A different date or an uncertain link is a question to investigate, not a detail to hide.

  4. 04

    Make the decision.

    Review the evidence. Keep a hypothesis open, reject it, or record your conclusion.

Explore the methodology ↗
What is built

Already working, today.

Kits from different sites recognise the same person

A match seen on two platforms is proposed as one person - and nobody is merged without you.

One door for every DNA file

Ancestry, MyHeritage, FamilyTreeDNA, 23andMe, GEDmatch, AutoCluster ZIP - recognised by content, never by file name.

Haplogroups on the tree

The Y and mt lines read from your kits become a claim on the paternal or maternal line, shown where that line runs.

A conflicts queue where a person decides

Contradictions between sources wait in a queue, and a person closes each one: confirm, reject, keep it as a hypothesis, or override it with a reason on the record.

Provenance everywhere.

A fact here is an assertion, its evidence, and a computed confidence - never a bare name. Conflicts are versioned, not overwritten. The Fantasy scan flags people whose branches look invented, and says plainly that a flag is not proof. Our mtDNA reference carries all 5,371 haplogroups of PhyloTree Build 17 in van Oven's exact notation - and when a chip cannot distinguish subclades, we say so instead of guessing. Many of these instruments exist because researchers on genealogy forums around the world asked for them - endogamy-aware DNA, honest chip resolution, imports that hold at family-archive scale. Built to requests, not to trends.

Several trees become one

Preview the merge, resolve the conflicts, commit into a new tree. Your original files stay downloadable byte-for-byte, and every decision is kept.

Duplicates found and merged in bulk

The Duplicate Detective proposes pairs, and you accept them one by one or hundreds in a single action.

Branch Curator

Every branch outside the main tree, listed: keep it, attach it or delete it - and undo if you change your mind.

Your file, signed

Every GEDCOM the platform writes is identifiable and verifiable, and your original stays downloadable at any moment.

46 languages, and surnames found by sound

The app speaks 46 languages, and Daitch - Mokotoff phonetic search finds a surname however the clerk spelled it.

Built for the trees that break other tools.

Serious research outgrows casual software. AutoTreeGen's import pipeline is tested end-to-end at 350,000 persons - a real parse, real persistence - on demand, on our own hardware. Free and Pro carry 250,000 persons per tree (on Free the engines above 20,000 wait for Pro), Premium 500,000 - the same ceiling for everyone; above it, some engines still run on a sample until streaming catches up.

Your tree and your DNA stay yours. Secured, never sold.

Your tree and DNA live on our own dedicated servers, not in a shared cloud database, and travel only over encrypted connections. Raw DNA is encrypted before it touches the disk, and every DNA computation runs only behind your explicit consent. We never sell or share your data and never use it to train AI. AI features see only the fragment you ask about, never raw DNA. The one copy that leaves our servers is a nightly encrypted backup the storage provider cannot read. Export your tree whenever you like, and ask us to delete it and it is erased.

Pricing

Plans built around evidence, not vanity

Four plans - Free, Starter, Pro and Premium. Free gives you a tree, 250,000 people, the GEDCOM Doctor and the Anti-Fantasy detector, no card required. Starter adds one DNA kit and your match list. Pro and Premium add full DNA and the advanced engines. Capability is the contract.

Carved oak - Free
Free
Open a tree, read the record, see what’s there.
$0 USD forever
Start free
Burnished copper - Starter
Starter
One tree, one DNA kit, your match list.
$9 USD/mo
Get Starter
Polished silver - Pro
Pro
Merge matches, resolve conflicts, grow the tree.
$29 USD/mo
Get Pro

Paid plans renew automatically each month or year, on the period you choose, until you cancel. Cancelling stops the next renewal; you keep the plan until the end of the period you already paid for.

Pay by card through Stripe, or with PayPal.

Free is a working tier, not a trial.

When it matters, a person answers.

  • Community · Free
  • Email 12h · Pro
  • Dedicated · Premium
Contact us
We work with you, whatever you bring.

One tree or fifty DNA kits - the same attention. If your import is messy, we help you clean it. If your kits are spread across platforms, we help you bring them together. If you are stuck on one ancestor, that is a real question and it gets a real answer. Write to us and a person replies - not a ticket number.

Before you begin

Good questions.
Plain answers.

Research deserves transparency.

Read our trust & privacy policies ↗
What file formats can I import?

Start with a GEDCOM exported from your genealogy tool. AutoTreeGen checks its structure and flags records that need attention.

How is DNA handled?

DNA requires explicit consent and careful handling. Read the current DNA privacy and consent policy before uploading your data.

What does confidence mean?

Confidence should be read alongside the supporting and conflicting evidence, not as a substitute for it. The methodology explains the approach.

Can I export my tree?

Your tree can be exported as GEDCOM. See the current product and plan information for research-report availability.

Where do I get started?

Create an account and start with your GEDCOM, or explore a worked example first.

More questions
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.

Is it available now?

Yes. AutoTreeGen is open: create an account and import your GEDCOM. There is a feedback button in the top bar - tell us what breaks.

Your next discovery starts with a question

See the proof behind
your own tree.

Give your family history a workspace where sources, DNA and decisions belong together.

Read our privacy notice before sharing personal or DNA data.