PedigreeTool vs Evagene: standards-first versus clinical-grade

Short version. PedigreeTool is a Stanford-backed browser pedigree application that positions itself as offering "the speed of sketching with standard scientific labels." Its strengths are NSGC-standard nomenclature with gender-inclusive symbols, ontology-linked search against HPO and MONDO, a rich export surface including GA4GH Phenopackets v2, and cloud storage — a set of capabilities that align very well with FAIR data principles and cross-institution research sharing. PedigreeTool's own website states plainly that it is not certified for clinical diagnostics, that auto-layout for complex families is still in development, and that clinical features are delayed to 2026. Evagene is a clinical-grade pedigree platform: BRCAPRO / MMRpro / PancPRO risk models, Mendelian calculators, AI-powered clinical interpretation with bring-your-own-key LLMs, a REST/webhook/MCP platform layer, and a 200+ disease catalogue with ICD-10 and OMIM coding. Neither product is strictly a superset of the other. If you are a research group whose data has to round-trip through GA4GH Phenopackets and HPO/MONDO repositories, PedigreeTool is a strong answer today. If you are a clinical service that needs validated risk numbers, clinical-grade reports, and a real integration platform, Evagene is the more appropriate tool.

This comparison is drawn from PedigreeTool's public website and documentation as of April 2026. If anything has since changed on their side, the PedigreeTool product pages supersede this article.

How the two products position themselves

PedigreeTool describes itself as combining "the speed of sketching with standard scientific labels." The product emphasises four things prominently: drag-and-drop canvas drawing, NSGC-standard nomenclature with gender-inclusive symbols, ontology-linked search against HPO (Human Phenotype Ontology) and MONDO (the Mondo Disease Ontology), and a broad export set (SVG, PNG, PDF, CSV, PED, JSON) including GA4GH Phenopackets v2. The Phenopackets alignment is meaningful — it places PedigreeTool inside the GA4GH FAIR-compliant data-sharing ecosystem, which matters for research consortia, collaborative rare-disease networks, and any group whose outputs need to flow into tools like Exomiser or LIRICAL.

PedigreeTool is also commendably honest about its current scope. Its own product pages state that auto-layout for complex family structures is still in development, that its clinical feature set is "delayed to 2026," that assisted-reproduction labelling is limited, and that the product is "not certified for clinical diagnostics." That is the kind of statement we always want to see on a research/clinical boundary product; it avoids ambiguity that could mislead a clinical buyer.

Evagene positions itself as clinical-grade pedigree management for precision medicine. Its emphasis is on the pedigree as a clinical document that has to be produced at consultation speed, annotated with ICD-10 and OMIM-coded diseases from a curated 200+ catalogue, run through validated risk models (BRCAPRO, MMRpro, PancPRO, plus Mendelian AD/AR/XR), and then surfaced to downstream systems through a real platform: a scoped REST API, webhooks, an MCP server for AI agents, and an embeddable viewer. Evagene's AI layer is bring-your-own-key — you use your own Anthropic Claude or OpenAI GPT account (Fernet-encrypted at rest), so interpretation traffic goes where your information-governance process has already approved.

The headline difference is orientation. PedigreeTool orients to FAIR research data standards. Evagene orients to clinical service workflows. They share a browser, NSGC notation, and ontology-linked disease annotation; they diverge sharply on risk modelling, AI interpretation, and platform surfaces.

Feature-by-feature comparison

The matrix below summarises publicly advertised capabilities as of April 2026. A tick means the vendor publicly documents the feature. A dash means the feature is not publicly listed — it does not necessarily mean the feature is absent, especially on a beta product where documentation can lag the build.

Matrix compiled from publicly available product pages and documentation as of April 2026. "—" indicates the capability is not publicly advertised; it does not necessarily mean the feature is absent, particularly on a beta product.

Where PedigreeTool is stronger

It is fair to state this up front. PedigreeTool's alignment with the GA4GH FAIR data stack — HPO, MONDO, Phenopackets v2 — is a genuine advantage that Evagene does not currently match. If your service works with the Global Alliance for Genomics and Health ecosystem, shares phenotype and family-history data across research collaborations, or feeds downstream variant-interpretation pipelines that consume Phenopackets, PedigreeTool is the more immediately useful tool. The HPO-linked search in particular fits well into undiagnosed-rare-disease workflows where phenotype deep-capture drives candidate-gene prioritisation.

PedigreeTool also ships with an academic credibility that matters in some procurement conversations. Its Stanford backing, explicit non-certification statement, and transparent roadmap (Research/Professional/Institutional tiers from April 2026, equity pricing for low-income countries) are signals of a serious, honest project. We respect that.

Where Evagene is stronger

Evagene is designed around clinical-grade outputs, and that shows in several places PedigreeTool does not currently advertise. The integrated BayesMendel risk models (BRCAPRO, MMRpro, PancPRO) run directly on the pedigree data and give a clinician a risk number they can discuss with a patient — without re-entering family history in a separate model runner. The Mendelian inheritance calculators cover autosomal dominant, autosomal recessive, and X-linked recessive patterns for monogenic conditions. Batch risk screening inverts the workflow: rather than "clinician suspects condition X, runs model," Evagene screens across the catalogue and flags conditions where family history crosses a threshold. None of this is advertised by PedigreeTool; PedigreeTool's own site says clinical features are delayed to 2026.

The AI interpretation layer is the second large gap. Evagene's BYOK LLM support (Anthropic Claude and OpenAI GPT, Fernet-encrypted), Analysis Templates with variable injection, and the MCP server exposing 11 pedigree tools to Claude Desktop, Claude Code, and any other MCP-compatible AI agent put Evagene in a different conversation for services that are starting to use AI as part of clinical reporting. If you just want a pedigree drawing you can export as Phenopackets, this does not matter. If you want AI to help draft the report, it does.

The third gap is the platform layer. Evagene's REST API (scoped evg_ keys, SHA-256 hashed at rest, rate-limited, read/write/analyse scopes), webhooks (HMAC-SHA256 signed), and embeddable viewer (iframe/SVG/JavaScript) make Evagene usable from other systems without bespoke integration work. PedigreeTool's export surface is strong for file-based interchange; Evagene's platform surface is stronger for live system integration.

Standards, ontologies, and honest gaps

This is the section where we have to be frank. Evagene does not today offer native GA4GH Phenopackets v2 export. If that is a requirement — and for some research-leaning services it is — PedigreeTool is the right answer today, and Evagene is not. We would rather say so clearly than let a buyer discover the gap after commitment. Evagene's roadmap on FAIR standards (Phenopackets, HPO-native capture, MONDO alongside OMIM) is worth confirming with the vendor at procurement time. Similarly, PedigreeTool's certification status is, by the vendor's own words, not "clinical diagnostic"; that cuts the other way for services whose governance requires clinical-grade tooling.

A reasonable compromise for some services is to run both: PedigreeTool for research and FAIR-compliant export into downstream variant interpretation pipelines; Evagene for the clinical workflow, risk calculation, and reporting side. The shared ground is standard pedigree structure, which travels well via JSON and via PED-to-GEDCOM conversion.

Pricing and deployment

PedigreeTool is in free beta through March 2026. From April 2026, PedigreeTool's own site describes a tiered commercial model — Research (non-commercial), Professional (clinical/commercial), Institutional (admin dashboard) — with equity pricing for low-income countries. Exact numbers should be confirmed on PedigreeTool's pricing page, which supersedes this article. Deployment is cloud SaaS with no credit card required during beta.

Evagene is in Alpha and free via a waiting list at evagene.com. Pricing for general availability has not been published. Deployment is browser-based cloud; the platform surface (REST, webhooks, MCP, embedded viewer) means Evagene can sit inside another clinical system rather than being the only place the pedigree is accessed from.

When to choose PedigreeTool

• Your output needs to be GA4GH Phenopackets v2 for downstream variant-interpretation pipelines (Exomiser, LIRICAL, consortium repositories).
• Your workflow is HPO-first: phenotype deep capture driving candidate-gene prioritisation.
• You use MONDO as your disease ontology.
• You are a research service and need FAIR-compliant interchange, not validated clinical risk numbers.
• Your institution values Stanford-adjacent academic backing and the explicit non-clinical-certification posture.
• Your pedigree needs are simpler (straightforward family structures, not complex multi-generational consanguinity).

When to choose Evagene

• You run a clinical genetics service and need validated risk models (BRCAPRO, MMRpro, PancPRO, Mendelian) rather than phenotype export.
• AI-assisted report drafting using your own LLM keys is part of how your service wants to work.
• You need programmatic pedigree access via REST API, webhooks, MCP, or an embeddable viewer for EHR and patient-portal integration.
• You build pedigrees live during consultation and want gesture drawing.
• You need consanguinity detection, a karyogram viewer, and batch risk screening across a curated disease catalogue.
• You want a vendor whose public posture is explicitly clinical-grade rather than explicitly non-diagnostic.

Migrating from PedigreeTool to Evagene

PedigreeTool exports JSON, CSV, PED, PNG, SVG, PDF, and Phenopackets v2. Evagene imports GEDCOM 5.5.1, JSON, XEG, 23andMe genotype/traits/health, and pedigree images via OCR. The practical migration path is JSON-to-JSON (a short schema mapping where individual/parent relationships transfer one-for-one), or PED-to-GEDCOM (the pedsuite R package has utilities for this, or a hand-written converter is a few dozen lines). HPO and MONDO annotations from PedigreeTool will need to be mapped to Evagene's ICD-10 / OMIM disease catalogue, which is a clinical-knowledge step rather than a data-conversion step — an Evagene clinician can typically do it in a few minutes per case.

For services running both tools in parallel, Evagene's GEDCOM import makes a weekly or monthly bulk sync practical. For services that have never used Evagene but want to try, the pedigree-image OCR feature means you can bring an existing PNG or SVG from PedigreeTool directly into Evagene without any conversion step at all.

Frequently asked questions

Related comparisons and reading

• Phenotips vs Evagene
• Progeny vs Evagene
• QuickPed vs Evagene
• Pedigree drawing software: a field guide
• Clinical genetics pedigree tools
• Hereditary cancer risk assessment