Alright, I've been down the rabbit hole for the last week trying to decide between Plausible and Fathom for a new side project. It's a documentation site for a dev tool, so privacy-first is a must, and I'm expecting maybe 30k-50k pageviews a month to start. Both tools get recommended constantly, but when you actually line them up feature-by-feature and cost-by-cost, the differences get really interesting!
I'm not just looking at the raw monthly price, but the *model* behind it. Both are roughly in the same ballpark for under 100k views, but the devil's in the details, right?
Here’s my breakdown so far:
**Pricing Structure Nuances:**
* **Plausible:** Straightforward bucket pricing. You pay $9/month for up to 10k pageviews, $19 for up to 100k. Simple. But it's per *site*. If I add a second project later, that's another subscription. Views are counted monthly, and if you go over, you need to upgrade.
* **Fathom:** Starts at $14/month for up to 100k pageviews *across all your sites*. That's a huge distinction! It's a pooled model. So if I have Site A with 70k views and Site B with 25k, I'm still on the base plan. Overages are billed at $0.0015 per view, which is pretty generous.
**Hidden Costs & Operational Quirks:**
* **Data History:** This is a big one. If you cancel Plausible, your historical data is gone after 2 years. Fathom keeps it "indefinitely" (or as long as they're around, I suppose). That's a potential future cost of staying subscribed even if you're not actively using it, just to keep the data.
* **API & Data Ownership:** Both offer APIs, but the ease of pulling your raw data out for my own dashboards or archiving feels like a hidden cost in developer time. Has anyone built a simple pipeline to back up their stats from either service?
* **Feature Gating:** Some advanced features (like funnels, some goals) can push you to higher plans. Need to check if the things I might want later (e.g., custom event tracking for button clicks) are included in their "Starter" or "Business" tiers.
My gut says: if you're a single-site, Fathom's price is slightly higher but the data retention policy is a big plus. If you're a tinkerer with multiple small projects, Fathom's pooled views make it way more economical. But Plausible's interface feels a bit snappier to me, and their open-source, self-hostable option (which I'd probably never use, but it's nice to know it's there) is a unique angle.
Has anyone else run both side-by-side for a few months? I'm super curious about the accuracy differences – do they track bots/spam the same way? Are there any weird discrepancies in session counts or bounce rates that could trip up my decisions later?
I'm a community manager running analytics for several technical blogs and a small SaaS company, so I've tested both on live sites under 100k views.
Here are my specific findings for your scenario:
1. **True Pricing for Multiple Projects:** Fathom's $14 base plan covers 100k views pooled across unlimited sites, a clear win if you'll have 2-3 low-traffic sites. Plausible's model is strictly per-site, so a second site is another $9-$19 monthly subscription. The breakpoint is usually around 2 sites before Fathom is cheaper.
2. **Data Freshness and API:** Plausible updates its dashboard near-real-time, typically within 2 minutes. Fathom has a built-in delay; in my usage, data can take 3-5 minutes to appear. If watching a live launch matters, Plausible is better. Both have solid APIs for your dev tool docs.
3. **Pageview Definition and Filtering:** Both are privacy-first, but they handle spam differently. Plausible has built-in filters for common bots and lets you create custom rules easily. Fathom relies more on a simple exclude list you manage. If you're not using a CDN that filters bots, Plausible requires less manual maintenance.
4. **Dashboard Clarity for Technical Audiences:** Plausible's dashboard is more granular for tech content, showing top pages by page title *and* URL separately, which I find better for docs. Fathom's interface is simpler but sometimes groups pages differently, which can be less precise for a documentation site structure.
My pick is Plausible for your single documentation site because the granular page reporting and real-time updates are more valuable for tracking doc usage. I'd choose Fathom if you were certain you'd add two or more sites within the next six months.
To decide cleanly, tell us if you plan to add more sites soon and if you need to see visitor counts the moment you share a link.
Keep it constructive.
You've correctly identified the core pricing divergence. The pooled model becomes a major factor if you intend to manage multiple sites from a single account. However, one nuance is that Fathom's overage billing, while generous, requires closer monitoring if you have traffic spikes across several sites. A single project going viral could push your pooled total over 100k quickly, whereas with Plausible's per-site model, only that specific site's subscription would need upgrading.
From an integration perspective, this model difference also affects how you'd set up automated alerts or dashboarding via their APIs. With Fathom, you'd monitor the aggregate usage across your account. With Plausible, you'd need to check each site's individual usage endpoint.
The per-site versus pooled decision often hinges entirely on your multi-project roadmap. If this documentation site will truly be standalone for the foreseeable future, the cost comparison is nearly moot. But if you're planning a blog or a separate marketing site for the same tool within the next year, Fathom's model starts pulling ahead immediately.
- Mike