The cookie-free, GDPR-friendly analytics tool that ships in a 1KB script and replaces Google Analytics for marketing sites. The $9/mo entry, the EU-hosted data story, and how it stacks up against PostHog, Fathom, and Vercel Web Analytics. Pricing reconciled against plausible.io/pricing.
Plausible is one of those products that earned its audience by saying no. No cookies, no cross-site tracking, no individual user profiles, no session recording, no funnels, no feature flags, no in-app event firehose. What you get instead is a focused, fast, privacy-respecting web analytics tool that does the small handful of things most marketing sites actually need — and does them well enough to replace Google Analytics for a meaningful slice of the indie SaaS scene. For solo founders who want to know how many people visited their landing page yesterday, where those visitors came from, and which posts are pulling traffic without lighting up every GDPR cookie banner on the internet, Plausible is one of the most defensible picks in the category.
Methodology. This is a research-based overview. We have not personally built production apps with Plausible; this article synthesizes the company’s documentation at plausible.io/docs, public pricing at plausible.io/pricing, public user reports from indie founders, and third-party benchmarks. Last reviewed: May 13, 2026.
Plausible is an open-source, privacy-first web analytics tool. The company was founded in 2018 by Uku Taht in Estonia, originally as a side project meant to be the analytics tool he wanted to use himself: simple, fast, free of cookies, and respectful of user privacy. The product is hosted in the European Union on Hetzner infrastructure, the codebase is written in Elixir and Phoenix, and the entire stack is publicly available on GitHub for anyone who wants to self-host it. Roughly 90% of paying users still choose the hosted offering at plausible.io because $9 a month is cheaper than the time it takes to run Postgres and Elixir on your own server.
The product is positioned squarely as a Google Analytics replacement — not a superset, not a competitor on features, but a replacement specifically for the slice of Google Analytics functionality that most site owners actually use. That positioning has stayed consistent for five years, and it’s the reason Plausible has built a loyal user base in the indie hacker, content marketing, and solo SaaS scenes. The product knows what it is and doesn’t try to be anything else.
Plausible’s pitch is three sentences long: pageview and traffic analytics, without GDPR consent banners, without 50KB of Google Analytics JavaScript, and without your visitor data ending up in a system that profiles them across the internet. Each of those three claims maps to a specific design choice in the product.
The no-consent-banner claim works because Plausible does not set cookies, does not generate persistent user identifiers, and does not track visitors across sites. Under the GDPR, the EU’s ePrivacy Directive, and the California Consumer Privacy Act, the data Plausible collects is generally not treated as personal data — meaning the consent-banner machinery that surrounds Google Analytics simply doesn’t apply. Plausible publishes a legal explainer on how it qualifies, and the conclusion is widely accepted by European privacy lawyers. For a solo founder running a marketing site, removing the cookie banner is genuinely a UX win.
The script-size claim is the headline number. Plausible’s tracking script is roughly 1KB compared to Google Analytics 4’s 50KB+ payload. That difference is meaningful on a slow mobile connection and contributes a measurable, if small, improvement to Core Web Vitals scores. For solo founders who treat Lighthouse scores as a leading indicator of SEO performance, the script-size delta matters.
The data-ownership claim rests on Plausible’s hosting location and business model. Data lives on EU servers; you can export it anytime via CSV or the API; the company does not resell or share visitor data with third parties because it has no advertising business to support. The contrast with Google Analytics — where the data fuels an advertising graph — is the privacy story Plausible leans on.
Plausible covers the metrics that matter for marketing-site analytics and explicitly stops there. The dashboard surface includes:
utm_source, utm_medium, utm_campaign, utm_term, and utm_content — everything a content-marketing or paid-acquisition founder needs to attribute traffic.The dashboard is a single-page, fast-loading view that surfaces all of those metrics together. There’s no segmentation builder, no cohort tool, no funnel surface, no path analysis — and that’s the trade-off. If your analytics question can be answered in the standard dashboard, Plausible is delightful to use. If you need to ask harder questions, the product will not answer them.
The list of missing features is intentional and worth understanding before you commit to the tool:
Most of those gaps are paired with a clean recommendation: use Plausible for web analytics, use PostHog or Mixpanel for product analytics, and run both. The two tools serve different layers of the stack, and the cost of running both at indie scale is small enough that the dual-tool pattern is the common solution.
Plausible’s tracking script is famously small — the company has measured it at roughly 1KB gzipped, compared to Google Analytics 4’s payload that lands in the 45–75KB range depending on configuration. The script is also lazy, deferred, and asynchronous by default, which means it does not block page rendering. For marketing sites that obsess over Core Web Vitals as an SEO signal, Plausible’s footprint is essentially free. For sites that already have heavy JavaScript payloads from frameworks like Next.js, the difference is smaller as a percentage of total weight but still real.
The setup is as fast as the script is small. You add a single <script> tag to your site — usually in the <head> — pointing at plausible.io/js/script.js with your domain as a data-domain attribute, you deploy, and you watch traffic show up in the dashboard within a minute or two. There is no consent banner to wire up, no cookie consent SDK to configure, and no “wait two days for data to backfill” latency the way Google Analytics has historically had. Most users describe the setup as the fastest in the category.
Plausible publishes a usage-based ladder on plausible.io/pricing driven primarily by monthly pageview volume. Always reconcile against the live page; rates in this space adjust periodically.
All plans come with a free 30-day trial, no credit card required. For self-hosters, the open-source Community Edition is free under an AGPL license — you pay only in server costs and operational attention. The math on self-hosting versus paying $9 a month rarely works out for a solo founder; you’d need a strong privacy or sovereignty reason to take on the operational overhead.
Plausible Community Edition is the open-source version of the product, released under the AGPL. It runs on Elixir and Phoenix with a Postgres database and a ClickHouse instance for event storage, and it can be deployed via Docker Compose to any VPS that can run those services. The feature parity with the hosted version is reasonable for the core analytics surface, though some newer features sometimes land in the hosted product first.
The reason most solo founders don’t self-host is straightforward: $9 a month is cheap, ClickHouse and Postgres are operational surface area you don’t need, and the time spent maintaining a self-hosted analytics stack is time not spent on your product. For founders with a specific data-sovereignty requirement or an existing infrastructure team, self-hosting is a real option; for everyone else, the hosted offering is the obvious pick.
Plausible’s data is stored on Hetzner servers in Germany, which puts it under EU jurisdiction and out of reach of US data-disclosure mechanisms like the CLOUD Act. The company commits in its terms not to resell visitor data, not to share data with advertising networks, and not to use the data for any purpose beyond serving your own analytics dashboard. Visitor IP addresses are hashed daily and not retained.
For founders selling to European customers — especially in healthcare, finance, or government-adjacent verticals — the EU-hosted, no-resale story is genuinely useful in sales conversations. For founders selling exclusively to the US market, the privacy story matters less but the simplicity story still holds. The SaaS GDPR compliance guide covers the broader compliance posture; Plausible is one of the cleanest analytics picks inside that frame.
Plausible’s setup is among the fastest in the entire SaaS category. The flow is: sign up at plausible.io, add a site by entering its domain, copy the generated <script> tag, paste it into the <head> of your site, deploy, and watch real-time traffic appear in the dashboard. The total time from account creation to first data point is typically under five minutes for a static site or a Next.js project, and most of that time is the deploy step.
For framework-specific integrations, Plausible ships first-party packages for Next.js, Nuxt, and a handful of other ecosystems — though none of them are strictly necessary because the bare script works everywhere. The how to add analytics with PostHog tutorial covers the more complex product-analytics setup; Plausible’s installation is essentially “paste this tag.”
Three honest cases:
A solo SaaS landing page, a content marketing blog, a documentation site — anywhere the analytics questions are “how many people are reading, where are they coming from, what posts are pulling traffic.” Plausible answers those questions cleanly at $9 a month with no consent-banner overhead and a 1KB performance cost.
If your sales motion runs through European customers or you’re selling into privacy-sensitive verticals, the cookie-free posture removes a real friction point. The legal explainer Plausible publishes is sturdy enough that most EU privacy lawyers accept it.
The common pattern: Plausible runs on the marketing site for traffic analytics, PostHog runs inside the application for feature usage, funnels, and session recording. Both have free or near-free tiers at indie scale, and the dual-tool stack covers more analytical surface than either alone.
The mismatch cases are straightforward:
Plausible is web analytics; PostHog is product analytics. PostHog is broader (events, funnels, feature flags, session recording, experiments) but it’s also more complex to set up and reason about. Plausible is simpler but limited to pageview-style metrics. Most teams that take this comparison seriously end up running both: Plausible on the marketing site, PostHog inside the app. The Plausible vs PostHog vs Fathom piece dives deeper on the trade-offs; the PostHog review covers the product side in detail.
The closest direct comparison. Fathom Analytics has nearly identical positioning — privacy-first, cookie-free, simple, lightweight script — at a similar price point of roughly $14–$15/month at the entry tier. The substantive differences are jurisdictional: Plausible is hosted in the EU on Hetzner, Fathom is US-based with a Canadian operations team. For EU-customer-facing sites, Plausible is the cleaner story; for US-centric sites, Fathom is fully competitive. Feature-for-feature the two products are close enough that the choice often comes down to brand affinity, hosting jurisdiction, and which dashboard you find more readable.
Google Analytics 4 is free, powerful, and complex. Plausible is paid, simple, and focused. GA4’s feature surface is substantially larger — segments, custom audiences, integration with Google Ads, BigQuery export — but the cost is the complexity tax and the consent-banner requirement. For founders who don’t need GA4’s deeper surface and don’t want to deal with the cookie-consent infrastructure, Plausible is a strict upgrade in user experience even though it’s a downgrade in raw feature count. The privacy story tilts strongly to Plausible.
Vercel Web Analytics is built into Vercel hosting and priced at roughly $1 per million pageviews on the Pro plan, which makes it materially cheaper than Plausible for any site already running on Vercel. The trade-off is feature depth: Vercel’s analytics surface is intentionally minimal and the dashboard is less developed than Plausible’s. For Vercel users who only need basic pageview counts and source attribution, Vercel Web Analytics is often the obvious cheaper pick. For users who want the broader Plausible feature surface or who care about the EU-hosting story, Plausible still wins.
Plausible is best-in-class for marketing-site analytics for solo SaaS founders. It’s the simplest reliable replacement for Google Analytics, the privacy story is clean enough to skip the cookie banner, and the $9-a-month entry tier is the cheapest line item in the typical solo founder stack. The performance footprint is negligible, the setup is genuinely under five minutes, and the dashboard is fast in a way that older analytics tools structurally aren’t.
The honest limitation is that Plausible covers web analytics only. For in-app product analytics — the feature usage, funnel, and retention questions that matter once people are inside your product — you need PostHog or a comparable tool. The pairing is cheap and the two tools complement each other cleanly. We cover the broader analytics stack in the complete guide to SaaS analytics, and Plausible fits naturally into the developer-focused roundup in best SaaS tools for developers. If you’re still deciding which analytics layer to invest in first, the head-to-head in Plausible vs PostHog vs Fathom is the next read.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.