HomeCatalog🌐 Web & CMSPlausible Analytics
Screenshot of Plausible Analytics website

// screenshot of plausible.io ↗

WEB & CMS · PRO TIER

Plausible Analyticspro

Plausible is privacy-friendly Google Analytics — a lightweight, cookie-less, GDPR-compliant web analytics platform. ~1 KB tracking script (vs 45 KB for GA4), no personal data collection, no cross-site tracking, no consent banner required in the EU. AGPLv3 open source with a hosted SaaS arm; the self-host community edition is fully featured.

🌐 Web & CMS Min 1024 MB RAM Port 8000 (http) Tier pro
// What it is

A closer look.

Plausible is privacy-friendly Google Analytics — a lightweight, cookie-less, GDPR-compliant web analytics platform. ~1 KB tracking script (vs 45 KB for GA4), no personal data collection, no cross-site tracking, no consent banner required in the EU. AGPLv3 open source with a hosted SaaS arm; the self-host community edition is fully featured.

It's the default analytics choice for European businesses that want real metrics without legal exposure.

// Use cases

What it's for.

Concrete scenarios where teams pick Plausible Analytics over the SaaS alternative.

GDPR-by-default analytics

no cookie banner, no personal data, EU-friendly out of the box

Lightweight tracking

~1 KB script doesn't tank PageSpeed scores

Marketing / SaaS dashboards

pageviews, sessions, sources, goals, funnels, revenue

Multi-site management

one server, dozens of customer / agency client sites

Replacement for GA4

same job, less Google, no cookie banner pain

// Who it's for

Built for these teams.

If your team profile matches one of these, Plausible Analytics is a strong fit out of the box.

Profile A

Marketing / product teams

replacing GA4 to skip cookie banners and recover 30%+ traffic from banner refusals

Profile B

Agencies

managing analytics across a portfolio of 10-100 client sites from a single dashboard

Profile C

SaaS founders

wanting simple page + funnel + goal metrics without GA4's "explorations" rabbit hole

Profile D

Government / EU compliance offices

required to drop US-based analytics under data sovereignty rules

Profile E

Bloggers & OSS maintainers

wanting honest pageview stats without harvesting reader privacy

// Differentiators

Why teams pick Plausible Analytics.

When evaluating self-hosted options for this category, here are the dimensions on which Plausible Analytics consistently lands above the alternatives.

  • No cookies, no consent banner — saves 30%+ traffic loss from banner refusals
  • GDPR / CCPA / PECR compliant — by design — no DPO sign-off needed
  • Simple UI — one screen, no GA4-style "explorations" complexity
  • AGPLv3 — verifiable open source, source-available CE matches SaaS
  • Self-host parity — community edition is the same code as the SaaS
  • API for data export — Stats API for custom dashboards / billing
// Integrations

Connects to.

The stack you'll plug Plausible Analytics into — services, protocols, and adjacent apps in the BluixApps catalog.

Tracking script
~1 KB JS, drop into any HTML, no SDK lock-in
CMS plugins
WordPress, Ghost, Hugo, Astro, Next.js, Gatsby ready-made
Goals + custom events
track signups, downloads, purchases via dedicated event API
Webhooks
fire on goal completions for downstream automation
Stats API
read-only API for billing dashboards, internal BI, weekly reports
Google Search Console
pull keyword data alongside on-site analytics
Email reports
scheduled weekly / monthly summaries via SMTP
// Adoption & deployment

Notable users & community

  • 22k+ GitHub stars
  • Used by ~10k self-host instances + the Plausible Cloud SaaS customers (DuckDuckGo, ConvertKit, Penpot, others)
  • Active forum, monthly product updates, strong stance on open web + privacy
  • Featured in "privacy-first stack" guides across Hacker News, r/privacy, Mastodon
  • Backed by Plausible Insights Ltd (EU-based) — sustainable open-source business

What we ship

  • Docker compose: Plausible + Postgres + Clickhouse (event store) + mailer
  • Pinned plausible/community-edition:v3.0.0, monthly upstream tracking
  • HTTPS via Let's Encrypt — tracking endpoint correctly configured for first-party setup
  • Admin user with random password + SMTP credentials placeholder for invite emails
  • Multi-site support enabled; agency reseller use case documented
  • Backup hook covers Postgres (config) + Clickhouse (event data)
// Tips & operations

Run it properly.

Operational guidance from running this in production — what to do before you scale, what to lock down, what surprises people.

// PERFORMANCE
Proxy /api/event via your nginx
first-party tracking endpoint dodges ad blockers and improves data quality
// SECURITY
Set up DNS for analytics subdomain
point analytics.yoursite.com at your Plausible instance for first-party setup
// OPERATIONS
Mind Clickhouse retention
events accumulate fast; set TTL on hits table for cost control above ~10M monthly events
// RELIABILITY
SMTP is required
invite emails + weekly reports break silently without it; wire Resend / SES / Mailgun
// DEPLOYMENT
Define goals BEFORE collecting data
backfilling goals on old events is partial; goal funnels need labels upfront
// SCALING
API keys are READ-ONLY
generate distinct keys per consumer; revoke individually without breaking other integrations
1024
// min ram (MB)
10
// min disk (GB)
8000
// access port
http
// protocol
pro
// bluixapps tier
postgres:15-alpine · clickhouse/clickhouse-server:23.3-alpine · ghcr.io/plausible/community-edition:v3.0.1
// docker image

Project resources

Official siteplausible.io ↗
// Alternatives in Web & CMS

Compare with