Plausible

Open-source web analytics, honestly reviewed. What you actually get when you ditch GA4 — and when self-hosting quietly breaks your numbers.

TL;DR

• What it is: Open-source (AGPLv3) web analytics built as a direct Google Analytics replacement — no cookies, no personal data, GDPR-compliant without a consent banner [6].
• Who it’s for: Founders, indie developers, and small teams who want meaningful traffic data without feeding Google’s ad machine or wrestling with GA4’s complexity [1][6].
• Cost reality: Cloud plans are traffic-based starting around $9/mo. Self-hosting is free software but the community edition strips out the bot filtering that makes numbers meaningful — a serious, non-obvious trade-off [1].
• Key strength: Genuinely the simplest privacy-compliant analytics switch available. One script tag, no consent banner, everything on one page. Trusted by Hugging Face, Basecamp, Ghost, and 16,000+ paying subscribers [homepage].
• Key weakness: Self-hosted community edition lacks advanced bot filtering — one real-world user watched their “200 visitors/day” site balloon to 5,000+/day post-migration, making the numbers useless. Funnels and revenue tracking are also cloud-only [1].

---

What is Plausible

Plausible is a web analytics tool built to answer one question: how many real people visited your site, where did they come from, and what did they do? That’s it. No user profiles, no advertising integrations, no retargeting segments. The entire codebase is public under the GNU Affero General Public License v3 (AGPLv3), meaning you can read it, run it, and verify it does exactly what it says [6].

The product comes from a team of 10, bootstrapped, self-funded, debt-free, and headquartered in the EU. Their servers run on European-owned infrastructure, and visitor data never leaves the EU — a meaningful distinction if you’re dealing with GDPR and tired of worrying about Schrems II [homepage]. The co-founders Uku and Marko describe their pitch plainly on the homepage: “We built Plausible because Google Analytics is frustrating to use, difficult to understand, slow to load and privacy-invasive” [homepage].

The technical pitch is similarly blunt: their tracking script is 75 times smaller than Google Analytics, no cookies are set, no persistent identifiers are created, and no cross-site or cross-device tracking happens. Because nothing personal is collected, you don’t need a cookie consent banner — which alone is worth something in terms of both user experience and legal headache reduction [homepage][6].

As of this review, the platform tracks 260 billion pageviews and reports 99.99% uptime over the last 90 days. It’s trusted by organizations including Hugging Face, Basecamp, Ghost, MongoDB, the Open Source Initiative, and the Python Software Foundation [6][homepage].

---

Why people choose it over Google Analytics, Matomo, and Umami

The pattern across every third-party source is consistent: people come to Plausible for one of three reasons — privacy ethics, GA4 frustration, or simplicity. They stay because the product actually delivers on those three things.

The GA4 migration push. Google’s forced migration from Universal Analytics to GA4 pushed a significant number of developers and founders to look for alternatives. GA4 is a materially different product — event-based rather than session-based, with a completely redesigned interface and a steeper learning curve. The loopwerk.io blogger [1] captures the mood: after years on Google Analytics they switched to Plausible specifically to get out of the “Google tracking visitors across the web, building advertising profiles from my site’s data” dynamic. One Trustpilot reviewer describes Plausible as “privacy-first, high-quality and very useful… completely open source and even can be self-hosted” [4].

Simplicity as a feature. The r/selfhosted comparison thread [3] sums up the UI trade-off clearly: “Umami is easier to set up and collects more complete data, while Plausible has a slicker but more branded user interface.” The homepage testimonial from SEO consultant Cyrus Shepard is representative: “My 100% favorite GA4 alternative so far. Not free and not a ton of bells and whistles, but SOOOO easy to use (for clients too) and the data is near real-time. A good solution for ~70% of websites struggling with GA4.” The product designer Rob Hope put it more bluntly: “I can’t remember when last I was this impressed by a SaaS UX + design. Became a paying customer within 1hr of the 30-day trial.” [homepage]

Privacy and GDPR compliance without legal risk. For founders selling into European markets, the ability to run analytics without a consent banner is genuinely valuable. Plausible’s entire value proposition is that you can answer “do I comply with GDPR?” with “yes, nothing personal is collected, verify it yourself in the open source code” — a much shorter conversation than explaining GA4’s data processing agreements [6].

Where the cracks show. The Trustpilot score is 3.1 out of 5 from 6 reviews — thin sample, but the complaints are pointed [4]. One user reports a two-week unresolved support issue after a domain migration, with the support team giving contradictory answers about proxy forwarding behavior. Another reports their dashboard being locked after exceeding pageview limits. A third describes what they call a fraudulent subscription — paying annually and then being forced to upgrade or losing access mid-year due to bot-inflated traffic pushing them over their plan limit [4]. These are minority views but they point at the same tension: bot traffic inflates your numbers, forces you into a higher tier, and the self-hosted escape hatch turns out to have a different set of problems.

---

Features

Based on the homepage, open-source documentation, and third-party descriptions:

Core analytics:

• Single-page dashboard — all essential metrics at a glance without custom reports or menus [homepage]
• Real-time dashboard updating every 30 seconds [homepage]
• Automatic scroll depth tracking on every page, no tag manager required [homepage]
• Built-in bot filtering (extent varies — see Deployment section) [1][homepage]
• Referral sources, countries, devices, and browser breakdown [5][homepage]
• Google Analytics data import [homepage]

Goal and conversion tracking:

• Codeless goals — turn any page into a conversion goal [homepage]
• Automatic tracking of file downloads, form completions, and external link clicks [homepage]
• Custom events and revenue tracking [homepage]
• Conversion funnels — cloud only [1]
• UTM campaign tracking with automatic channel grouping [homepage]

Integrations and context:

• Google Search Console integration for search queries and organic performance [homepage]
• AI traffic monitoring — see which AI tools (ChatGPT, Perplexity, Claude) send you traffic [homepage]
• Consolidated dashboard across multiple sites [homepage]

Privacy architecture:

• No cookies, no personal data, no persistent identifiers [homepage][6]
• EU-based servers, data never leaves the EU [homepage][6]
• GDPR, CCPA compliant out of the box — no consent banner required [homepage][6]
• AGPLv3 license — fully auditable [6]

What’s gated to cloud only:

• Advanced bot filtering (32,000 data center IP ranges + behavioral pattern analysis) [1]
• Funnels [1]
• Revenue tracking [1]

---

Pricing: SaaS vs self-hosted math

Plausible Cloud (their SaaS):

Plans are traffic-based — you pay for monthly pageview volume, not per-event or per-user. The loopwerk.io blogger [1] documents the tier structure from lived experience: the 10k plan ran $48/year when they joined in 2020; the 100k plan was $96/year originally, then jumped to $190/year (with grandfathered pricing kept at $96); the 200k plan is currently $290/year. The homepage shows a 30-day free trial with no credit card required.

Self-hosted (Community Edition):

• Software license: $0 (AGPLv3) [6]
• Hosting: $5–15/month on a VPS with Docker
• Bot filtering: severely degraded — see below [1]

Google Analytics for comparison:

• Free — paid with your visitors’ data and your GDPR compliance risk
• No cost except the consent banner friction and the advertiser profiling you enable

Concrete comparison for a mid-size founder:

A site with 100,000 monthly pageviews on Plausible Cloud runs around $190/year. That’s real money compared to zero for Google Analytics. The honest question is what you’re buying: GDPR compliance, no consent banner, no Google dependency, and numbers you can trust. Whether that’s worth $190/year is a values question as much as a budget question.

Self-hosted is nominally free but — as the loopwerk.io case demonstrates — if your site receives bot traffic (most do), you may find the self-hosted numbers so inflated they’re useless [1]. One blog’s ~200 daily visitors turned into 5,000+ post-migration. If that happens, you’ve saved $190/year and gained nothing.

---

Deployment reality check

The self-hosting setup is Docker Compose running three containers: the Plausible app, ClickHouse (for analytics queries), and PostgreSQL (for account data). The GeekSocket writeup [5] walks through the actual compose setup, including the mail server for account activation and notifications. The r/selfhosted thread [3] notes that the ClickHouse requirement makes the stack heavier than Umami (PostgreSQL only), though on a properly-specced VPS the performance difference isn’t noticeable.

What you actually need:

• A Linux VPS with 2–4 GB RAM minimum (ClickHouse is memory-hungry)
• Docker and docker-compose
• A domain with HTTPS (Caddy or nginx reverse proxy)
• SMTP provider for notification emails
• About 30–60 minutes if you’ve deployed Docker stacks before

The bot filtering problem. This is the single most important thing to understand before self-hosting. Plausible’s cloud offering uses layered bot detection: user-agent filtering, referrer spam blocking, around 32,000 known data center IP ranges, and behavioral pattern analysis. The self-hosted community edition includes only basic user-agent filtering and referrer spam blocking — the IP range list and behavioral analysis are cloud-only [1].

The loopwerk.io blogger [1] documented this quantitatively. After migrating from Plausible Cloud to self-hosted, their site went from ~200 unique visitors/day to sometimes more than 5,000 per day — all bot traffic. They write: “Without proper bot filtering, the numbers stop representing real people. At that point, what are you even measuring?” The blogger’s conclusion is pointed: “Offering managed hosting and backups should be enough to justify a paid tier. Instead, Plausible talks up being open source while they strip out core functionality to push you towards it.” [1]

For a personal blog or portfolio site with low traffic, this may not matter — bots may never overwhelm real signal. For any site with meaningful public exposure, this is a critical limitation that Plausible’s documentation doesn’t surface prominently.

Funnels in self-hosted: The community edition shows the funnel feature in the UI — but it’s non-functional and can’t be removed from the interface. The loopwerk.io blogger flags this: “always in your face” [1]. That’s a poor UX choice for an open-source project.

---

Pros and cons

Pros

• Genuinely privacy-first architecture. No cookies, no personal data, EU servers, AGPLv3 — you can audit every claim in the source code [6]. This is not marketing language; it’s verifiable.
• No consent banner required. Because nothing personal is collected, you’re GDPR/CCPA compliant without popup friction. Meaningful for conversion rates and user experience [homepage][6].
• Simplest analytics switch available. One script tag, one dashboard page, all the essential metrics. DHH of 37signals calls it “wonderful”; Ghost switched everything from GA [homepage]. The learning curve is close to zero.
• Lightweight tracking script. 75x smaller than Google Analytics — measurable impact on page load time and carbon footprint at scale [homepage].
• Traffic-based pricing, not per-event. You pay for your traffic tier, not for how many events you fire. No “I accidentally tracked 10M events this month” bill [homepage].
• Bootstrapped, EU-based, independent. No VC pressure to monetize data, no acquisition risk, no US data sovereignty concerns [homepage].
• AI traffic visibility. Built-in tracking for which AI tools send you traffic — a relevant capability as ChatGPT and Perplexity become real referral sources [homepage].

Cons

• AGPLv3, not MIT. You can self-host freely, but if you modify and distribute (embed in a SaaS product you sell), you must publish your source code. Check with a lawyer before building a business on top of the modified code [6]. This is a real constraint compared to MIT tools.
• Self-hosted bot filtering is broken for many use cases. The community edition’s bot detection is so stripped-down that high-traffic or publicly-indexed sites will see numbers 10-25x their real traffic. This isn’t a niche edge case — it affected a real user’s production analytics immediately after migration [1].
• Funnels and revenue tracking are cloud-only. Core conversion analytics features are intentionally gated [1]. The funnel UI even appears in self-hosted but is non-functional.
• Trustpilot score is 3.1/5 from a small sample, with genuine complaints about support quality, contradictory answers on proxy forwarding, and dashboard access being cut off mid-subscription over bot-inflated pageview counts [4]. Sample is too small to be definitive, but the pattern is consistent.
• ClickHouse requirement makes self-hosted heavier than alternatives. Minimum 2–4 GB RAM. Fine for a dedicated VPS; a constraint on shared or tiny instances [3][5].
• Fewer features than Matomo. No session recording, no heatmaps, no A/B testing, no CRM integrations. That’s intentional — but if you need those, Plausible isn’t the answer [3].
• No offline data export / data portability is straightforward but the loopwerk.io blogger did successfully export from cloud and import to self-hosted, so migration isn’t impossible [1].

---

Who should use this / who shouldn’t

Use Plausible Cloud if:

• You’re running 1–5 sites and spending $0 on GA while absorbing GDPR risk and cookie banner friction.
• You need something a client or non-technical co-founder can read without training.
• You want to stop feeding Google data about your visitors and you’re willing to pay ~$9–16/mo for a clean conscience and clean numbers.
• Your compliance team needs a simple answer to “how do you handle EU visitor data?” — Plausible is that answer.

Self-host Plausible if:

• Your site gets low-moderate traffic from known, legitimate sources and bot traffic isn’t a concern you’ve measured.
• You have technical staff comfortable with Docker Compose and VPS maintenance.
• You understand and accept the degraded bot filtering and cloud-only funnel features going in.
• You’ve evaluated Umami and prefer Plausible’s UI.

Skip Plausible (use Umami instead) if:

• You want self-hosted analytics that works reliably without bot flooding your numbers — Umami runs on PostgreSQL, is MIT-licensed, and the r/selfhosted community consistently rates it easier to set up and more complete for self-hosters [3].
• You want MIT licensing instead of AGPLv3 — Umami gives you full commercial freedom.

Skip Plausible (stay on Google Analytics) if:

• You genuinely need GA4’s advanced features: cohort analysis, BigQuery export, audience building for Google Ads.
• You’re not selling into EU markets and GDPR compliance isn’t a concern.
• Your budget is zero and you’re comfortable with Google’s data practices.

Skip Plausible (use Matomo) if:

• You need session recordings, heatmaps, or A/B testing alongside page analytics.
• You want the most feature-complete GA replacement regardless of complexity [3][5].

---

Alternatives worth considering

• Umami — MIT-licensed, PostgreSQL backend, easier self-hosting setup, generally more complete data according to the r/selfhosted comparison [3]. The practical alternative for self-hosters who hit Plausible’s bot filtering wall.
• Matomo — The enterprise-grade open-source option. Feature-complete GA replacement with heatmaps, session recording, and funnels. PHP stack is more complex to self-host; community finds it overwhelming for simple use cases [3][5].
• Fathom Analytics — Similar privacy-first positioning to Plausible, closed source, Canadian-hosted. Comparable pricing. Choose between Plausible’s open-source transparency or Fathom’s simpler architecture.
• GoatCounter — Minimal, free for public sites, self-hostable. The GeekSocket blogger mentions trying it but found “the UI is very basic” [5]. Viable if Plausible’s pricing is a barrier and you can live with sparse UI.
• PostHog — If you need product analytics (session replay, feature flags, A/B testing) in addition to web traffic. Open source, self-hostable, significantly heavier stack. Different category.
• Google Analytics 4 — Still the zero-cost default. If the privacy trade-off is acceptable and you need the full feature set including Google Ads integration, it’s hard to beat on price.

---

Bottom line

Plausible is the right product for a specific, well-defined problem: you’re done feeding Google your visitors’ data, you need GDPR compliance without lawyering, and you want analytics simple enough to actually use. For that use case — cloud-hosted, ~$9–16/month depending on traffic — it’s genuinely excellent. The UI is clean, the setup is a single script tag, and the data is trustworthy.

The self-hosted pitch is where it gets complicated. Plausible markets itself as open source and self-hostable, but the community edition strips the bot filtering that makes traffic numbers meaningful, gates funnels to the cloud, and then shows you a broken funnel UI anyway. The loopwerk.io case [1] is a real-world demonstration of what this looks like in practice, not a theoretical concern. If you’re self-hosting to save money and end up with analytics that show 25x your real traffic, you haven’t saved anything — you’ve just broken your metrics.

For self-hosted analytics that actually works reliably without buying a cloud subscription, Umami is the more honest recommendation. For the managed cloud experience, Plausible earns its reputation. Just know which product you’re actually getting before you migrate.

---

Sources

1. Loopwerk — “Self-hosting Plausible broke my analytics” (February 17, 2026). https://www.loopwerk.io/articles/2026/plausible/
2. Jeremy Cheng, CodeX / Medium — “Plausible: Self-Hosted Analytics. Open Source, Lightweight, Dead Simple…” (March 30, 2021). https://medium.com/codex/plausible-self-hosted-analytics-5370fc1aa889
3. r/selfhosted (Chronicallybored) — “self-hosted analytics: comparing Umami, Plausible and Matomo”. https://www.reddit.com/r/selfhosted/comments/1h0fle4/selfhosted_analytics_comparing_umami_plausible/
4. Trustpilot — Plausible Reviews (6 reviews, 3.1/5). https://www.trustpilot.com/review/plausible.io
5. Bhavin Gandhi, GeekSocket — “Self-hosting Plausible Analytics” (May 31, 2021). https://geeksocket.in/posts/plausible-analytics/
6. Plausible Analytics — “Open source Google Analytics alternative”. https://plausible.io/open-source-website-analytics

Primary sources:

• Official website and homepage: https://plausible.io
• Open-source documentation: https://plausible.io/open-source-website-analytics