Open-source genealogy software, honestly reviewed. For people who want to own their family tree — not rent access to it.

TL;DR

What it is: A self-hosted web interface for Gramps, the open-source genealogy database that’s been around since the 1990s. AGPL-3.0 licensed, runs in Docker, works alongside the Gramps desktop app [2][website].
Who it’s for: Genealogy hobbyists who’ve outgrown commercial platforms, people who don’t want their family data sitting on Ancestry or MyHeritage servers, and anyone who already uses Gramps Desktop and wants web access for the whole family [1][2].
Cost savings: Ancestry charges ~$25–50/month. MyHeritage’s full-featured plan runs $100–180/year. Gramps Web self-hosted costs whatever your VPS costs — typically $5–10/month — and zero licensing fees [AGPL-3.0].
Key strength: Deep integration with the Gramps desktop app. Full bidirectional sync. DNA match support, face detection, AI chat, interactive maps, printable reports — more features than most commercial platforms [website].
Key weakness: This is not beginner software. The learning curve is steep, setup is genuinely complex, and the project runs primarily on one maintainer. One detailed user review describes a three-hour setup attempt that ended in uninstall [4]. The community explicitly frames Gramps as software “you don’t outgrow” — not something you start with [1].

What is Gramps Web

Gramps Web is the browser-based frontend for Gramps — a genealogy database project that predates most of the commercial platforms it now competes with. The desktop application has existed for decades; Gramps Web API is the Python REST backend that makes it accessible from any browser, and the web frontend layers on top of that.

The pitch on the homepage is plain: “The free, open-source genealogy system for building your family tree – together.” Data lives on your server, you control who sees it, and you can export everything at any time in standard formats [website]. The “together” part matters — Gramps Web is built for collaborative family history research, where multiple family members can contribute from different devices without everyone needing to install a desktop app.

What separates it from a generic family tree app is that it inherits the full Gramps data model. Every record type the desktop supports — people, families, events, places, repositories, sources, citations, media objects, notes — is available in the browser. The bidirectional sync add-on means you can edit on the web, pull those changes to your desktop, then push updates back. They coexist rather than compete [website].

The GitHub repository for the API backend sits at 190 stars. That’s a modest number, but it doesn’t reflect the broader Gramps project, which has a long community history. The TrueNAS community catalog lists it as a supported app, last updated April 2026 [3], which is at least a signal that it’s maintained.

Why people choose it

The Reddit post announcing v3.4.0 [2] is the most useful single document for understanding who actually deploys this. The author lays out three reasons that keep coming up in the community:

Data ownership over convenience. The author explicitly names 23andMe, MyHeritage, Geni, and Ancestry as services where “one person who is really into committing our entire family history” may be uploading data to a platform that will eventually change pricing or cut access. 23andMe’s trajectory — their bankruptcy filing and questions about what happens to user DNA data — makes this concern concrete rather than theoretical [2]. Gramps Web imports from most genealogy export formats, so moving existing data in is at least possible.

DNA data specifically. Gramps Web supports DNA matches and a chromosome browser. If you’ve taken a DNA test and want to keep that data under your own control, there aren’t many self-hosted options. The Reddit author frames this directly: “I know companies like 23andMe will cut user access eventually. Corporation keeping that data but you losing access is wrong.” [2]

The OIDC trigger. The v3.4.0 release that prompted the Reddit post added OIDC support — login via Google, GitHub, Facebook, Keycloak, or Authentik. The author calls this the deciding factor: genealogy apps get opened infrequently, forgotten passwords are common, and convincing older family members to manage separate credentials is a support nightmare [2]. OIDC removes that friction.

The Gramps Discourse forum [1] offers a different angle. The community there argues explicitly that Gramps is not for new genealogists — it’s for people who’ve outgrown their first software. The framing: “Start wherever you want. Gramps will be there when you’re ready.” The people who arrive at Gramps Web tend to be either committed open-source users or people with real data volume and research depth who’ve hit the walls of commercial platforms [1].

Features

Based on the official features page and deployment documentation [website]:

Core genealogy:

All Gramps record types: people, families, events, places, sources, citations, media, notes
Bidirectional sync with Gramps Desktop via the Sync Add-on
Privacy levels: mark records as private, control which users see private data (filtered at database layer, not application layer)
Role-based access: owners, editors, contributors, members — with a live demo showing each role [2][website]

Visualization:

Interactive family tree graphs: ancestor chart, descendant chart, hourglass chart, fan chart, configurable generations
Interactive searchable map of all places
Support for historical map overlays stored as media objects in the database

Media and collaboration:

Photo tagging with automated face detection
Collaborative photo identification for old family images
Genealogy blog built in — research stories with pictures, stored in the Gramps database

Data management:

Full-text search across all object types including note content, with wildcard syntax and boolean operators
Import/export in Gramps XML and GEDCOM formats
User-initiated full data export (family tree + media + accounts) for backup or migration — no lock-in [website]
Printable reports: relationship graphs, book reports, PDFs — inherits all Gramps Desktop report types [website]

DNA:

DNA match storage and chromosome browser
Positioned as an alternative to commercial DNA platforms for data custody [2]

Modern additions:

OIDC authentication (Google, GitHub, Facebook, Keycloak, Authentik) — added in v3.4.0 [2]
Integrated AI chat assistant
Task management within the app
OpenHistoricalMap integration
Multi-tree support
40 interface languages [website]

Deployment options:

Docker (single container for quick start, multi-container for production)
PostgreSQL backend support
S3 storage support for media files
Let’s Encrypt integration documented
DigitalOcean and TrueNAS deployment guides [3][website]
CPU-limited deployment guide for low-power hardware

Pricing: SaaS vs self-hosted math

Gramps Web itself is free — AGPL-3.0, no commercial tier, no hosted SaaS. What you’re comparing is self-hosting costs against what you’d pay commercial platforms.

Commercial genealogy platforms (approximate):

Ancestry: ~$25–50/month depending on plan, record access database not included in base tier
MyHeritage: $100–180/year for Premium Plus; DNA storage extra
Geni: $100–120/year for Pro
23andMe: DNA kit one-time + subscription for health features; data access now uncertain post-bankruptcy

Gramps Web self-hosted:

Software: $0 (AGPL-3.0)
VPS: $5–10/month on Hetzner, Contabo, DigitalOcean
Domain: $10–15/year if you want a clean URL
Your time for setup and occasional maintenance

If you’re paying Ancestry $39/month (standard US plan) and running Gramps Web on a $6 Hetzner VPS, you save roughly $390/year on pure subscription costs. The comparison isn’t quite clean — Ancestry includes record databases that Gramps Web doesn’t replicate — but if you’re using Ancestry purely for hosting your own tree rather than searching historical records, the math is straightforward.

The important caveat: Gramps Web doesn’t replace Ancestry’s record access. It replaces the hosting part of Ancestry — your family tree, media, DNA data, and collaboration. You can still use free services like FamilySearch for record lookups. Pricing data for exact current plans is not available in the source materials — verify directly before making decisions.

Deployment reality check

The official documentation covers Docker single-container, Docker Compose multi-container, Let’s Encrypt, DigitalOcean, and TrueNAS [website][3]. The quick start is literally one Docker command:

docker run -p "5055:5000" -e TREE=new ghcr.io/gramps-project/grampsweb:latest

That gets you running. Production deployment is considerably more involved.

What you actually need for production:

A Linux VPS with at least 2GB RAM
Docker and docker-compose
PostgreSQL (the production config uses an external database rather than the default SQLite)
Redis (for task queuing — face detection, report generation, sync operations)
A reverse proxy with HTTPS (Caddy or nginx)
An S3-compatible store if you have significant media volume
SMTP configuration if you want email invites

What the community flags:

The Reddit author who posted the v3.4.0 announcement [2] explicitly warns: “it is fully featured project but… can be a bit… janky… at times… it carried over some design choices that I find… strange and it has a single maintainer.” The single-maintainer point is the most significant operational risk for anyone building long-term around this.

The negative user review [4] is worth reading in full context. It describes a failed GEDCOM import attempt in 2021 — a three-hour session ending in uninstall, with complaints about database locking errors and unhelpful error messages. The reviewer has a technical background and still couldn’t get it working. This is a data point from five years ago and software changes, but the underlying pattern — Gramps’s complexity punishing users who try to just dive in — matches what the community forum says [1]: this software expects you to read the documentation before using it.

The Discourse forum [1] is candid about this: Gramps’s community explicitly says new genealogists should probably start with commercial software and come to Gramps later. That honesty is admirable, but it means the software hasn’t prioritized first-run experience the way commercial competitors have.

Realistic time estimates:

Technical user with Docker experience, starting fresh: 2–4 hours to a working HTTPS instance
Non-technical user following guides: a full day or weekend, realistically
Importing an existing GEDCOM: variable — the 2021 review [4] warns of data loss warnings in Gramps’s own documentation for large files; verify current behavior before importing production data

TrueNAS has a one-click install via the community catalog [3], which lowers the bar significantly for NAS users already on that platform.

Pros and Cons

Pros

True data ownership. AGPL-3.0 means the code is open, and the export-anytime feature means your data is never trapped. No vendor can revoke access, raise prices, or go bankrupt taking your family tree with them [2][website].
Full Gramps Desktop integration. If you’re already a Gramps Desktop user, this adds web access without replacing your workflow. Bidirectional sync is a genuine differentiator [website].
More features than it looks. DNA chromosome browser, face detection, AI chat, historical map overlays, OpenHistoricalMap integration, printable reports — the feature list is longer than most commercial platforms [website].
OIDC in v3.4.0. Removing the separate-password problem significantly lowers the friction for getting family members to actually contribute [2].
No per-user or per-feature pricing. Once deployed, adding more family members costs nothing. The full feature set is available to everyone on the instance.
40 languages. Genuinely useful for families that span language communities [website].
TrueNAS community support. One-click install for NAS users lowers the deployment bar [3].

Cons

Single maintainer. The Reddit community flags this directly [2]. A project running primarily on one person is a bus-factor risk. If the maintainer burns out or moves on, maintenance velocity drops sharply.
Steep learning curve. The community itself says beginners should start elsewhere [1]. The negative review [4] describes a technical user failing to complete basic setup. The software expects investment before it rewards it.
“Janky at times.” The r/selfhosted author who posted the release announcement uses those exact words [2]. This isn’t a polished SaaS product — it’s a complex tool that occasionally shows its seams.
GEDCOM import warnings. The 2021 review [4] cites Gramps’s own documentation warning that large GEDCOM imports will cause data loss. Verify current behavior before trusting production data to an import.
Carries legacy design decisions. The Reddit author notes the rewrite from Java Applet to web app “carried over some design choices that I find… strange” [2]. Some UX rough edges appear to be inherited rather than new.
Documentation is written for people who are already Gramps users. It doesn’t meet newcomers where they are [4].
No commercial support tier. There’s no paid option that gets you a support SLA or professional setup help. You’re relying on community forums [website].

Who should use this / who shouldn’t

Use Gramps Web if:

You’re already a Gramps Desktop user and want collaborative web access for your family.
You have genealogy data on Ancestry, MyHeritage, or similar platforms and want to move it somewhere you control long-term.
You’re concerned about DNA data custody, especially post-23andMe-bankruptcy.
You have a NAS running TrueNAS and want a one-click install path [3].
You’ve been doing genealogy research seriously for years and have outgrown commercial platforms’ export and customization limits.
You’re comfortable with Docker and are willing to spend a weekend on setup.

Don’t use Gramps Web if:

You’re new to genealogy. Use Ancestry, MyHeritage, or FamilySearch first. Come back when you’ve hit their walls [1].
You want a polished consumer product. This is closer to research software than to a consumer app.
You need to search historical record databases — Gramps Web stores your tree but doesn’t include record access.
Your use case is one person, occasional use, and you don’t need collaboration. The desktop app alone may be simpler.
You need commercial support guarantees or an SLA. None exists.

Alternatives worth considering

FamilySearch — free, no subscription, operates the largest free genealogy record database in the world. Hosted, so no self-hosting option, but for pure record access it can’t be beaten on price.

The Next Generation (TNG) of Genealogy Sitebuilding — another self-hostable genealogy web app, longer track record, PHP-based. More mature in some respects, less active development recently.

Webtrees — open-source PHP genealogy app. Self-hostable, simpler to deploy than Gramps Web, active development. A reasonable alternative if you don’t need Gramps Desktop integration.

Ancestry — the incumbent. Biggest record database, most polished UI, most expensive, fully closed. Your data is accessible only through their platform.

MyHeritage — Ancestry competitor with strong European record databases and AI photo enhancement features. Hosted, subscription-required for full access, not self-hostable.

MacFamilyTree / RootsMagic — desktop-only applications, no self-hosted web option, but solid single-user genealogy tools if web sharing isn’t a requirement.

For someone who specifically wants self-hosted, the realistic shortlist is Gramps Web vs Webtrees. Gramps Web wins if you already use Gramps Desktop and want the sync integration. Webtrees wins if you want simpler deployment and don’t have existing Gramps data.

Bottom line

Gramps Web earns its place in the self-hosted genealogy space by doing something commercial platforms don’t: treating your family history data as actually yours. The OIDC addition, DNA storage, bidirectional desktop sync, and solid feature depth make it a legitimate alternative to Ancestry or MyHeritage for anyone who’s been doing this long enough to care about data portability.

The honest trade-off is steep. This is not software you hand to a non-technical family member on a Tuesday and expect working by Thursday. The single-maintainer bus factor is real, the setup complexity is real, and the “janky at times” characterization from the community is not a red flag to dismiss [2]. But for the right user — someone with existing Gramps data, a NAS or cheap VPS, and reasons not to trust commercial platforms with sensitive genealogy and DNA records — the investment pays off. A $6 VPS and a weekend of setup buys you perpetual, privately-hosted family history research that no subscription price hike can touch.

Sources

trlvn, The Gramps Project Discourse Forum — “Was Gramps your first?” (March 2025). https://gramps.discourse.group/t/was-gramps-your-first/7131
PovilasID, r/selfhosted — “Gramps web 3.4.0 release is viable alternative to myhertage/geni/23andme/ancestry” (2025). https://www.reddit.com/r/selfhosted/comments/1obpcy8/gramps_web_340_release_is_viable_alternative_to/
TrueNAS Apps Market — “Gramps Web” (App Version 26.4.1, last updated 2026-04-10). https://apps.truenas.com/catalog/gramps-web
Anonymous, genealogy-software.no1reviews.com — “Be Forewarned - A Three Hour Tour” (January 2021). https://genealogy-software.no1reviews.com/user-review-7489/gramps.html