Plausible vs Fathom: near-twins, and how to actually pick one
Two cookieless, privacy-first analytics tools that solve the same problem the same way. The differences are real but small, which is itself the most useful thing to know before you spend a week comparing them.
Plausible and Fathom are functionally near-twins: both are cookieless, script-light, privacy-first analytics tools designed to replace GA4 for simple site measurement. The differences that can decide it: Plausible is open source with a self-hosting option and an EU-based company; Fathom is closed source with its own privacy-focused infrastructure. For most sites, either works, so decide fast.
- tool1
- Plausible
- tool2
- Fathom
The most useful fact: they are near-twins
Most "X vs Y" pages manufacture drama because drama holds attention. This pair does not have much. Plausible and Fathom were built in the same era, in reaction to the same problem, for the same buyer: site owners who want honest traffic numbers without cookies, consent walls, or a training course. Both load a tiny script, count visitors without cross-site identifiers, and put the answers on one page.
I have seen teams spend two weeks on this decision. The two weeks cost more than a year of either subscription. If your measurement needs are simple enough for either tool, they are simple enough that the choice between them is nearly free of risk. That framing matters more than any feature table, so it goes first.
Where they genuinely differ
- Open source. Plausible's code is public and there is a self-hostable Community Edition. Fathom is a closed product. If your policy, your client contracts, or your own convictions require inspectable code or the option to run it yourself, the decision just ended: Plausible.
- Company and hosting jurisdiction. Plausible is an EU company hosting in the EU. Fathom is a North American company that has built privacy-focused infrastructure with EU-friendly routing. Both market GDPR alignment; the corporate home differs, and for some EU businesses (or their lawyers) that difference is the whole conversation. Verify the current hosting architecture on each vendor's docs before deciding on this axis, because infrastructure details change faster than comparison pages.
- Feature edges. Both cover the core: pageviews, sources, goals, events, simple funnels or conversion views. At the edges each has conveniences the other lacks, and both ship changes often enough that any specific list here would age badly. Read each changelog for the one feature you cannot live without; if you cannot name that feature, the edges do not apply to you.
What choosing either one gets you
The shared trade is the same one described in GA4 vs Plausible: you give up user-level exploration, ads-platform plumbing, and deep segmentation for a dashboard everyone actually reads and a much simpler privacy posture. If you have not yet decided whether the lightweight category fits you at all, start with the cookieless analytics roundup and come back here with the finalists.
The decision, stated plainly
- Need self-hosting or open source: Plausible.
- Legal wants an EU company end to end: Plausible, and have the lawyer confirm the hosting details.
- Neither constraint applies: pick on interface taste and current pricing, and give the decision an afternoon. Sign up for both trials, look at your own site's data in each, and keep the one you reach for on day three.
The mistake to avoid
The tool pair is not where the risk lives. The risk is the same as any migration: goals that nobody defined, campaigns nobody tags consistently, and a GA4 history nobody exported before the property went quiet. Whichever twin you choose, spend the week you saved on the boring part: define the three conversions that matter, write down your UTM discipline, and export the old data. A simple tool measuring well-defined events beats a deep tool measuring chaos, and it also beats a simple tool measuring chaos.