TrakGene vs Evagene: a detailed clinical pedigree software comparison

Short version. TrakGene is Evagene's closest technical peer: both are cloud-first pedigree platforms built with clinicians, both run cancer risk tools directly on the pedigree, both offer AI assistance, and both take data exchange seriously. They are genuine head-to-head competitors. The differences worth comparing are these. On AI: TrakGene ships an integrated AI copilot for gene, phenotype, and disease suggestions; Evagene ships a bring-your-own-key LLM layer (Anthropic Claude, OpenAI GPT), Analysis Templates, an MCP server with eleven pedigree tools, and clinical interpretation reports. On risk models: TrakGene covers CanRisk (BOADICEA) and GAIL; Evagene covers BRCAPRO, MMRpro, and PancPRO from BayesMendel. On phenotyping: TrakGene has explicit HPO support; Evagene uses ICD-10 and OMIM across a 200-plus disease catalogue. On interoperability: TrakGene has HL7 FHIR and a custom API SDK; Evagene has a scoped REST API, webhooks, an embeddable viewer, and MCP. On pricing: TrakGene is enterprise sales-led with institutional customers including NIH, NHS, and Geisinger; Evagene is free to try during Alpha. Neither product is universally better — this article is about which fits your service.

This comparison is written in good faith. TrakGene is publishing strong SEO content and is visibly investing in the category, and that is good for clinical genetics as a whole. Where TrakGene is stronger, we say so; where Evagene is stronger, we say that too. All TrakGene claims are drawn from the TrakGene website and public product material as of April 2026; if anything has since changed, TrakGene's own product pages supersede this article.

How the two products position themselves

TrakGene describes itself, in its own words, as an "intuitive and inclusive pedigree chart drawing tool, developed with clinicians for clinicians." Its product emphasis spans auto-pedigree generation from family history data, HPO phenotyping, genomic health records, an AI copilot that suggests genes, phenotypes, and diseases, cancer risk tools including CanRisk and GAIL, genotyping with ClinVar, a secure patient access portal, HL7 FHIR and custom API SDK integration, and electronic family history capture. Its public site lists institutional customers including the NIH, NHS, and Geisinger, placing the product firmly in the enterprise end of the market.

Evagene positions itself as clinical-grade pedigree management for precision medicine. Its emphasis is on the pedigree as the central clinical artefact, with a gesture drawing canvas for live consultation work, BayesMendel risk models (BRCAPRO, MMRpro, PancPRO), Mendelian inheritance analysis, AI-powered clinical interpretation via bring-your-own-key LLMs, an MCP server for agentic AI, a REST API with signed webhooks, an embeddable pedigree viewer, and comprehensive data import including GEDCOM 5.5.1, 23andMe, JSON, XEG, and pedigree image OCR. See our platform page for the full surface.

The headline difference is one of approach rather than ambition. TrakGene packages an integrated genomic health record with AI baked into the product as a copilot, aimed at institutional buyers. Evagene packages a deep pedigree platform with modern surfaces (BYOK LLMs, MCP, API, embeds) that let the pedigree flow into whatever downstream AI workspace, patient portal, EHR layer, or research dashboard a service uses. The two products share a substantial overlap and differ primarily in how they expose their capabilities.

Feature-by-feature comparison

The matrix below summarises the product features each vendor publishes on their public site and documentation. A tick means the feature is publicly advertised or documented; a dash means it is not publicly listed (which does not necessarily mean it is absent — enterprise products often keep capabilities behind sales). Where nuance matters, we add a note.

Matrix compiled from publicly available product pages, documentation, and marketing material as of April 2026. "—" indicates the capability is not publicly advertised and does not necessarily mean it is absent. Enterprise products commonly keep capabilities behind sales; confirm with each vendor for a procurement-grade comparison.

Pedigree drawing

Both TrakGene and Evagene draw pedigrees using standardised clinical notation, support gender-inclusive symbols, and are cloud-first browser applications. The two products diverge on the data capture model. TrakGene emphasises auto-pedigree generation from family history data and from electronic family history capture forms, producing a pedigree from structured input. Evagene emphasises gesture drawing during live consultations, keyboard shortcuts, and automatic symbol standardisation — with imports from GEDCOM 5.5.1, JSON, 23andMe, and pedigree image OCR as the structured-input path.

Neither is universally better. If your service collects a structured family history form ahead of the appointment and wants a pedigree produced automatically from it, TrakGene's electronic family history capture is a native fit. If your pedigree is constructed live during the consultation or reconstructed from heterogeneous inputs (a written pedigree from a referral, a GEDCOM export from another tool, a raw 23andMe upload), Evagene's gesture canvas plus multi-format import is the intended match.

On the specifics, Evagene additionally supports consanguinity detection with Wright's coefficient and a karyogram viewer, neither of which is currently advertised on TrakGene's public site. Both products support modern pedigree notation properly; the granular differences come down to workflow fit rather than drawing capability.

Risk models and clinical analysis

Both products run cancer risk tools directly on the pedigree rather than requiring re-entry. The model coverage is the place where an honest difference shows up, because the two products have built around different published models.

TrakGene integrates CanRisk (which incorporates BOADICEA v6 for breast and ovarian cancer and PanelPRO research models) and GAIL for breast cancer risk. CanRisk is a widely used, externally validated pipeline maintained by the University of Cambridge and is the modern successor to the BOADICEA Web Application. For services whose primary risk assessment need is breast cancer risk via the CanRisk/BOADICEA pipeline, TrakGene's integration is a strong fit.

Evagene integrates BRCAPRO for breast and ovarian cancer, MMRpro for Lynch syndrome, and PancPRO for pancreatic cancer, all from the BayesMendel suite. On top of this, Evagene layers Mendelian inheritance analysis for autosomal dominant, autosomal recessive, and X-linked recessive conditions, which covers reproductive genetics and non-cancer monogenic workflows where neither BayesMendel nor CanRisk is applicable. Evagene also ships batch risk screening across its entire 200-plus disease catalogue with configurable thresholds, so the software can flag a condition the clinician may not have thought to check.

If your service centres on breast cancer and wants CanRisk, TrakGene is the more direct fit today. If your service needs BRCAPRO/MMRpro/PancPRO explicitly, or wants a broader Mendelian calculator alongside cancer risk, Evagene is the more direct fit. A comprehensive service might use both; or might choose the platform whose other capabilities (AI, API, HPO, FHIR) match better.

AI: copilot vs bring-your-own-key

Both products take AI seriously, and both are past the point of stitching AI on as an afterthought. The shape of each AI integration is different enough to be a primary decision factor.

TrakGene advertises an AI copilot that helps clinicians during pedigree construction — suggesting genes, phenotypes, and diseases based on the data the clinician has entered. This is a vendor-managed, product-integrated AI experience: the copilot lives inside TrakGene, presumably runs against a TrakGene-chosen model, and is tuned for the specific workflow of building and annotating a pedigree. For many services this is the easiest way to have AI in the workflow — the vendor handles the model, the prompts, and the compliance story.

Evagene takes a different approach: bring-your-own-key (BYOK). Your service uses its own Anthropic Claude or OpenAI GPT account; Evagene encrypts your keys at rest with Fernet and calls your model provider directly with your credentials. No Evagene-managed model sits in the middle handling your clinical text. On top of BYOK, Evagene ships:

• AI clinical interpretation — structured narrative reports covering key findings, family implications, data gaps, and screening recommendations, designed as a drafting aid for clinicians.
• Analysis Templates — custom AI prompt templates with variable injection ({{pedigree_description}}, {{proband_name}}) that let a service codify its house style of report writing and reuse it across cases.
• MCP (Model Context Protocol) server — eleven pedigree tools exposed to Claude Desktop, Claude Code, and any MCP-compatible AI agent, so clinicians can work with pedigrees from inside their normal AI workspace.

The trade-off is a genuine one. TrakGene's copilot is easier to adopt — you do not need your own LLM account or any integration work. Evagene's BYOK layer is more work to set up but gives your service direct control over the model choice, the contract, the data residency, and the prompt library. For services that already run Claude Enterprise or ChatGPT Enterprise and want their existing AI contract to be the substrate, Evagene fits cleanly. For services that want AI embedded in the product with no external AI contract, TrakGene fits cleanly.

Interoperability, API, and integration

Both products are open to integration, and both have modern surfaces. TrakGene advertises HL7 FHIR integration and a custom API SDK, which together address the standard enterprise integration pattern of pushing clinical genetics data into a hospital's FHIR gateway. TrakGene also offers a secure patient access portal, which is valuable for services that want patients to view or confirm their own family history record.

Evagene's integration surface covers similar ground but with different specifics. A scoped, rate-limited REST API (keys in the format evg_<43 chars>, SHA-256 hashed at rest, with read, write, and analyse scopes) lets another system query or modify pedigrees programmatically. Webhooks deliver HMAC-SHA256-signed payloads for eight event types (pedigree and individual CRUD, analysis completed, import completed) so downstream systems can react to changes. The embeddable pedigree viewer ships as an iframe, raw SVG, or JavaScript snippet — which, in practice, is how services stand up a lightweight patient-facing or researcher-facing pedigree view without wiring up a full SSO flow. The MCP server exposes eleven pedigree tools to AI agents. Documentation is public at evagene.net/help.

On data portability, Evagene imports GEDCOM 5.5.1 (the de facto clinical pedigree exchange standard — see our GEDCOM pedigree software guide), JSON, 23andMe genotype/traits/health-history files, XEG, and pedigree images via OCR. Exports include JSON, GEDCOM, PNG, SVG, and PDF. TrakGene's public material does not enumerate these specific formats; services moving data in volume between systems should raise data format compatibility directly with TrakGene's team.

For a large institution whose clinical genetics traffic flows through a FHIR gateway, TrakGene's explicit FHIR story is a direct match. For a team building AI agents, patient portals, research dashboards, or EHR-side integration layers, Evagene's REST API plus embeddable viewer plus MCP surface is easier to prototype against.

Deployment, pricing, and governance

TrakGene is available as cloud SaaS with an on-premise option for institutions that need in-house data residency. Pricing is not publicly displayed; the product is enterprise sales-led and lists institutional customers including NIH, NHS, and Geisinger on its site. Evagene is a cloud-hosted browser application, currently in Alpha, free to access via the waiting list at evagene.com. Pricing for general availability has not been published. Evagene does not currently advertise an on-premise option; services with strict in-house data residency requirements should weigh TrakGene accordingly.

On security baseline, Evagene encrypts LLM keys at rest with Fernet, signs webhook payloads with HMAC-SHA256, and uses scoped API keys hashed with SHA-256. Any formal certification status (HIPAA, ISO 27001, Cyber Essentials Plus, NHS DSP Toolkit, etc.) should be confirmed directly with either vendor at the point of procurement — both products are aimed at clinical use and will respond to compliance questionnaires as part of a normal procurement cycle.

When to choose TrakGene

• Your workflow is HPO-driven rare disease phenotyping and you want HPO deeply integrated into pedigree construction.
• Your cancer risk assessment need is breast cancer via CanRisk/BOADICEA and/or GAIL, and you want those models built in and maintained by the vendor.
• Your service needs a vendor-managed AI copilot embedded in the product without a separate LLM contract.
• You need HL7 FHIR integration as a first-class, advertised capability.
• You have strict on-premise deployment requirements.
• You need a patient-facing portal built into the product.
• You are procuring at institutional scale and the precedent of NIH, NHS, and Geisinger as customers is meaningful.

When to choose Evagene

• You use BRCAPRO, MMRpro, or PancPRO and want them run directly from the pedigree, plus Mendelian inheritance for monogenic non-cancer conditions.
• AI-assisted clinical interpretation matters, and you want to use your own LLM keys (Anthropic, OpenAI) rather than a vendor-mediated model.
• You already work with Claude Desktop, Claude Code, or ChatGPT and want the MCP server to expose pedigree tools to your AI workspace directly.
• You need codified, reusable AI prompt templates (Analysis Templates) rather than a single vendor copilot persona.
• You are building AI agents, internal tooling, patient portals, or research dashboards that need REST API, webhooks, and an embeddable viewer.
• You need GEDCOM, 23andMe, and pedigree-image OCR interoperability for archival, referral, and research workflows.
• You want to start free today via the Alpha waiting list rather than going through an enterprise procurement cycle first.

Migrating from TrakGene to Evagene

If you decide to move from TrakGene to Evagene, the practical path runs through shared data formats. Where TrakGene's HL7 FHIR integration or custom API SDK can export pedigree data as FHIR resources, JSON, or a comparable structured format, Evagene's REST API can ingest it. Evagene imports GEDCOM 5.5.1, JSON, 23andMe, and pedigree images via OCR natively. OMIM-coded diseases and standard demographics transfer cleanly; HPO-first phenotype records will need to be re-expressed against Evagene's ICD-10 / OMIM catalogue, which is a workflow change if your documentation is HPO-native.

For services running both products in parallel during a transition, Evagene's webhook surface plus the embeddable viewer allows pedigrees to appear inside another application — including a TrakGene portal or a hospital EHR — without a full data migration up front. A sensible migration pattern is: run Evagene alongside TrakGene for new cases, export-and-reimport a representative historical cohort, verify BayesMendel and AI interpretation outputs against existing clinical notes, then plan a cutover.

Frequently asked questions

Related comparisons and reading

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