Compare · updated 2026-08-31
03 · The field
juuna vsFathom.
Fathom Analytics is simple, privacy-first web stats done with real polish: a light script, a dashboard that fits on one screen, and years of taking visitor privacy seriously before it was fashionable.
juuna shares the privacy instincts and builds a bigger product on them: funnels, session replay, heatmaps and Web Vitals alongside the traffic, each customer on a dedicated instance. Which one you want depends on how much product you want.
Their case
Choose Fathom if…
- You want traffic numbers and nothing else, on a dashboard you can read in ten seconds. Fathom is built deliberately lean, and the leanness is the product.
- You run a portfolio of sites. Fathom is priced and shaped for keeping many small sites under one roof.
- A long privacy track record matters: Fathom has been privacy-first from the start and has years of reputation behind it.
- You want almost nothing to configure, and nothing that needs a manual.
Ours
Choose juuna if…
- You need to see sessions, not just count them: masked session replay and click, scroll and attention heatmaps on every plan.
- You want product analytics past what aggregate web stats can answer: funnels, retention cohorts, user flow and identify().
- You want performance beside traffic: Core Web Vitals p75s per page, measured on real visits.
- You want your analytics on hardware nobody else shares: a dedicated instance with its own Postgres, run for you.
I
Side by side
- What it is
- juuna Product analytics suite: traffic, funnels, replay, heatmaps, vitals
- Fathom Privacy-first web stats, built deliberately lean
- Hosting model
- juuna A dedicated managed instance per customer
- Fathom Fathom’s managed cloud
- Pricing model
- juuna Flat per instance: $29 / $79 / $199 per month
- Fathom Tiered by monthly pageview volume
- Session replay
- juuna Included, masked by default
- Fathom Outside its deliberate scope
- Heatmaps
- juuna Included, over captures of the real page
- Fathom Outside its deliberate scope
- Core Web Vitals
- juuna Included, daily p75s per page
- Fathom Outside its deliberate scope
- User-level analytics
- juuna identify(), traits, retention cohorts, per-visitor timelines
- Fathom None by design: privacy-first aggregate stats
- Built for
- juuna One product you want to understand deeply
- Fathom Many sites you want counted cleanly
- Script weight
- juuna 1.0 KB gzipped, no dependencies
- Fathom Light, by design
II
The real difference
Fathom is what discipline looks like in analytics: a small, fast, private tool that counts traffic and declines to become more. For a marketing site, a blog, or a founder with five projects, that restraint is exactly right, and Fathom executes it beautifully.
juuna is for the questions that come after the counting: where users get stuck, what a session actually looked like, how fast the page felt while it happened. If you are asking those, you have outgrown web stats, and that is the moment juuna is built for.
§
Asked and answered
- Can Fathom do session replay or heatmaps?
- No, by design: Fathom is built deliberately lean around private traffic stats, and that focus is much of why its fans love it. If watching real sessions and seeing where people click is part of your work, that is the line where the two products part. juuna includes masked replay and click, scroll and attention heatmaps on every plan.
- Is juuna as private as Fathom?
- The instincts are the same; the shapes differ. Fathom’s answer is to collect almost nothing. juuna collects what a product team needs and then contains it: one dedicated instance per customer, replay masked by default, a first-party identifier that never crosses sites, raw events pruned on schedule. More data, held more tightly. If collecting less is itself the requirement, Fathom’s model is the purer fit.
- Is juuna overkill for a simple marketing site?
- Honestly, it can be. If visit counts, referrers and a few events answer every question you have, Fathom will serve you beautifully and juuna’s replay and funnels will sit unused. juuna earns its keep when the site is a product: a signup flow to debug, sessions worth watching, performance worth tracking.
See it with your own traffic.
Flat plans, everything included. Checkout to live dashboard usually takes about ten minutes.