Website analytics sounds like a pretty boring topic, I know. The reason I care is that I've been trying to de-Googlify my life, and if you run a website, Google Analytics is usually one of the biggest Google pieces still sitting on it. Plausible is a free and open source alternative that tells you how much traffic you're getting and where it's coming from, without the tracking baggage.
To test it, I ran Plausible and Google Analytics on techhut.tv at the same time for about two weeks before making the call. I'll go over what Plausible is, how it compared to Google Analytics for me, a tour of the dashboard, and how to self-host it yourself.
The video was recorded in April 2021, and a lot has moved since then. The self-hosted version is now called Plausible Community Edition (CE) and lives in its own community-edition repository, so the self-hosting steps below are for CE v3.2.1, released May 15, 2026, which is still the current release. Google also shut down Universal Analytics in 2023, so the Google comparison below reflects Google Analytics 4. The tracking snippet and a few settings screens have changed too, and I've noted those where they come up. My hands-on impressions are from the recorded walkthrough of the hosted dashboard.
What Plausible Is
Plausible is a web analytics tool. You add one small script to your site, and it gives you a single dashboard with visitors, page views, top pages, referral sources, locations, devices, and browsers. The core app is licensed AGPL-3.0, and the JavaScript tracker that goes on your site is MIT licensed so it doesn't drag AGPL obligations onto your website.
You have two ways to run it, which is kind of similar to how Bitwarden does things:
- Plausible Cloud: the paid, hosted service at plausible.io. Subscriptions are how the project is funded. When I recorded, I was on the free trial, which is still 30 days with no credit card required. I'm not going to quote prices here, since they've changed since 2021. Check the Plausible site for the current plans. Back then I was planning to just pay for it, because it's a good service and paying for their servers is how you support the project.
- Plausible Community Edition: the free, self-hosted version. You run it on your own server with Docker, and you never pay Plausible anything.
They aren't identical, though. Plausible's own comparison lays out the differences:
| Plausible Cloud | Community Edition | |
|---|---|---|
| Hosting and upkeep | Managed by Plausible | You handle installs, upgrades, backups, and uptime |
| Release schedule | Updated continuously | Long-term releases, about twice a year |
| Premium features | Everything in your plan | No marketing funnels, user journeys, ecommerce revenue goals, SSO, or Sites API |
| Bot filtering | Advanced, including about 32K data center IP ranges | Basic, based on User-Agent and referrer spam lists |
| Data location | EU-owned infrastructure, stored in Germany | Wherever you host it |
| Raw data | Dashboard, CSV export, Stats API | Same, plus direct access to the ClickHouse database |
| Support | From the Plausible team | Community only |
So CE is the same core product, but you're trading a few premium features and some bot filtering for full control.
Plausible vs Google Analytics
Plausible has a few pages on its site explaining why it's different from Google Analytics. In 2021, the gist was data ownership, open versus closed source, and visitor privacy. That still holds up, but GA4 has changed some details, so here's where things stand now.
Cookies and tracking. GA4 sets first-party _ga cookies that last two years by default and exist to tell users apart. Plausible doesn't use cookies, browser cache, or local storage. To count unique visitors, it hashes the IP address and User-Agent together with the site domain and a salt that's rotated and deleted every 24 hours. Raw IPs and User-Agents are never stored, and because the salt changes daily, the same person can't be followed from one day to the next.
IP addresses. To be fair to Google, GA4 is better here than the old Universal Analytics was. Google says it doesn't log or store IP addresses for EU, Swiss, and UK users and only uses them for coarse location. Plausible applies its no-raw-IP approach to everyone.
Open source. Plausible's code is on GitHub, and you can read it, audit it, or run it yourself. Google Analytics is closed.
Data retention. GA4 standard properties keep user-level and event-level data for either 2 or 14 months. That only limits explorations and funnel reports, not the standard aggregated reports. With Plausible CE, the data sits in your own database for as long as you keep it.
Script size and blocking. Plausible says its script is about 2.5 KB gzipped, compared with 135 KB for the GA4 tag. Those are Plausible's numbers, but either way it's a much lighter thing to add to every page.
The point I made in the video still applies: Plausible won't hand you, the site owner, sensitive information about your visitors, but it gives you enough to make reasonable decisions about your site. Plausible also says its approach means you don't need a cookie consent banner for it. That's their position. Check your own legal requirements, especially if you run other trackers next to it.
My Side-by-Side Numbers
Since I was running both on techhut.tv, I compared them. On my peak day, Thursday, April 22nd, Plausible reported 773 visitors, while Google Analytics showed 667 users. I wasn't sure if those were counted the same way, and they probably aren't, since Plausible counts visitors and Google counts users. There was a difference, but not one big enough to change what content I'd make.
![]()
The realtime numbers were close too. Google showed six active users while Plausible reported seven.
A Tour of the Dashboard
What I really liked about Plausible was the simplicity and visuals compared to Google Analytics. Google may give you more data, but most of that data isn't significant for me. What I want to know is where people are coming from, where in the world they are, and what devices they're on, so I can tailor the content and layout to them.
Realtime and Date Ranges
The realtime view shows current visitors, the pages they're on, and where they came from. When I recorded, people were on my Cooler Master guide, the Ryzen temperature monitoring article, and one of my Pop!_OS posts. Google's realtime report can also show the source, it just took me a second to find it.
![]()
The period picker switches between realtime, preset ranges, and a custom range. I'd only been running it for about two weeks, so the 30-day view didn't have much more than the 7-day one. A brand new site opens on today, then the default becomes Last 28 days the next day. The old 30-day range is still there, and the T shortcut opens it.
Top Stats
Across the top you get unique visitors, total page views, bounce rate, and average visit duration, everything you'd expect from a good analytics tool. In the two weeks of testing, I had a little over 11,000 page views. There's also an export option that gives you a CSV of the data.
Sources, Pages, Locations, and Devices
The tiles below the graph break things down into top sources, top pages, locations, and devices. The devices tile has tabs for browsers, operating systems, and device type (desktop, mobile, or tablet). Compared to most sites, a lot of my visitors use Firefox, which makes sense given that I push free and open source software and Linux. Most people come from desktops too, which is nice to know, since I can lay out guides and tutorials expecting a bigger screen.
![]()
Entry and Exit Pages
The pages tile also has entry and exit pages. In my case, the home page had a high exit count, but its entry count was a bit higher. So people coming to the site directly weren't just hitting the home page and leaving. Most of them were at least reading one article, which is exactly what I want to see.
Settings
What I walked through in the video, along with what's changed:
- Theme. I had dark mode on, switched to light to show it off, and it was absolutely blinding. Theme now lives under Account Settings, then Preferences, then Dashboard Appearance, and it follows your system theme by default, with manual light and dark options.
- My Sites. Clicking the logo takes you to your list of sites. I only had techhut.tv, but you can add as many as you want.
- Site settings. The gear icon next to a site opens its settings: the tracking snippet, timezone, and domain.
- Visibility. You can make a dashboard public so anyone with the link can see your stats. I did that for techhut.tv at the time and linked it in the video description. You can also embed the dashboard on another site or your own internal dashboard. Embedding now works from a shared link, which you can also limit to a specific segment of your traffic.
- Goals. You can set up goals to track specific pages or custom events, like signups or button clicks.
- Search Console. The Google Search Console integration pulls in the search terms that brought people to your site.
- Email reports. Weekly or monthly email reports of your stats.
- Custom domain. There was a custom domain option in 2021. Current versions don't have it. Instead, Plausible documents proxying the script through your own domain if you want it served first-party.
- Danger zone. This is where you reset all of a site's stats or delete the site from Plausible completely.
![]()
Since 2021, Plausible has also added things I didn't show in the video, such as acquisition channels, scroll depth, time on page, segments, and imports from Google Analytics 4. The changelog has the full list.
Adding Plausible to Your Site
Like Google Analytics, you enable it by putting a little script in your site's <head> tag. Since October 2025, every site gets its own snippet. You can copy it from your site settings, under General, then Tracking, then Review next to Site installation. It looks like this, with your own site's script ID:
On a self-hosted instance, the script URL points at your own domain instead of plausible.io. Older snippets keep working, but options like outbound link and file download tracking are now toggled from the same Site installation screen instead of by changing the script name. If you're on WordPress, the official plugin handles this for you.
Self-Hosting Plausible Community Edition
This is the part that's changed the most since the video. The official setup is the plausible/community-edition repository, which contains a Docker Compose file with three services:
plausible: the app itself,ghcr.io/plausible/community-edition:v3.2.1plausible_db: PostgreSQL 16 for users, sites, and settingsplausible_events_db: ClickHouse 24.12 for the analytics events, with config files tuned for small servers
Requirements
- Docker with the Compose plugin
- A CPU that supports SSE 4.2 or NEON, which ClickHouse needs
- At least 2 GB of RAM, so ClickHouse doesn't run out of memory
- A domain or subdomain with a DNS record pointing at your server, like
plausible.your-domain.com
1. Clone the Release
Clone the branch for the current release:
git clone -b v3.2.1 --single-branch https://github.com/plausible/community-edition plausible-ce
cd plausible-ce
2. Create the Environment File
Only two variables are required. BASE_URL is the address you'll use to reach Plausible, and SECRET_KEY_BASE needs to be at least 64 bytes long:
cat > .env <When HTTP_PORT is 80 and HTTPS_PORT is 443, Plausible gets and renews its own Let's Encrypt certificate. For that to work, the domain in BASE_URL has to resolve to this server, and ports 80 and 443 need to be reachable from the internet.
Keep a copy of .env somewhere safe. SECRET_KEY_BASE signs dashboard sessions, and the key that encrypts two-factor secrets is derived from it unless you set TOTP_VAULT_KEY separately.
3. Expose the Ports
Don't edit compose.yml. Put your changes in a compose.override.yml instead, which Git ignores, so pulling the next release won't conflict with them:
cat > compose.override.yml <4. Start It
docker compose up -d
docker compose logs -f plausible
On the first start, the container creates and migrates its databases before running the app. Then open https://plausible.your-domain.com and create your first account. After that, registration is invite-only by default (DISABLE_REGISTRATION=invite_only). Set it to true if you want to shut sign-ups off entirely.
Add your site, copy the snippet, and paste it into your website's <head>. The script will be served from your instance.
Using Your Own Reverse Proxy
If you already run a reverse proxy, like the Nginx Proxy Manager setup from my SSL certificates guide, let it handle HTTPS instead. Remove HTTPS_PORT from .env, set HTTP_PORT=8000, and only publish that port:
services:
plausible:
ports:
- 127.0.0.1:8000:8000
Then point your proxy at port 8000. Binding to 127.0.0.1 only works if the proxy runs directly on the host. If your proxy runs in another container, put both on a shared Docker network or publish the port on the server's LAN IP instead. Plausible's reverse proxy guide has Caddy, Nginx, and Apache examples. If you use Nginx, make sure WebSocket upgrades are passed through for /live/websocket.
Just want to try it on your own machine? Set BASE_URL=http://localhost:8000, HTTP_PORT=8000, leave out HTTPS_PORT, and publish 8000:8000.
Optional Configuration
A few things from the dashboard tour need extra setup on CE. They're all environment variables in .env:
| Feature | What to set |
|---|---|
| Email reports, invites, password resets | MAILER_EMAIL and SMTP_HOST_ADDR, SMTP_HOST_PORT, SMTP_USER_NAME, SMTP_USER_PWD, or set MAILER_ADAPTER to Bamboo.PostmarkAdapter with POSTMARK_API_KEY, Bamboo.MailgunAdapter with MAILGUN_API_KEY and MAILGUN_DOMAIN, Bamboo.MandrillAdapter with MANDRILL_API_KEY, or Bamboo.SendGridAdapter with SENDGRID_API_KEY |
| City-level locations | MAXMIND_LICENSE_KEY for a free MaxMind GeoLite2 database. Without it, CE uses a bundled country-level database. |
| Search Console and GA4 imports | GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET from your own Google Cloud OAuth app. There's a step-by-step guide. |
Run docker compose up -d again after changing .env so the container picks it up.
Security, Upgrades, and Backups
-
The databases aren't published. The compose file uses the default
postgrespassword for PostgreSQL, but neither database exposes a port to the host. Keep it that way, and don't addports:to them in your override. -
Upgrade promptly. Security fixes are not backported. v3.2.1 is a good example. It's a security release that fixes CVE-2026-8467, a possible remote code execution through the
/storybookendpoint that affected v3.0.0 through v3.2.0. If you're on anything older, upgrade. -
How to upgrade. Read the release notes first, especially for major versions. Then pull the new release branch and recreate the containers. The image tag is pinned in
compose.yml, so this moves you to the new version:code@techhut:~cd plausible-ce git pull origin vX.Y.Z docker compose up -dSwap
vX.Y.Zfor the new release, and watch the releases page for announcements. -
Back it up. Your data lives in the
db-data(PostgreSQL),event-data(ClickHouse), andplausible-datavolumes. Compose prefixes them with the project name, so they'll show up asplausible-ce_db-dataand so on. Back those up along with your.envandcompose.override.yml.
If you get stuck, CE support happens in the self-hosted discussions on GitHub.
Final Thoughts
There's nothing too complicated about Plausible, and that's kind of the point. It gives me visitors, sources, locations, devices, and pages in one clean dashboard, without tracking people across the internet. After running it next to Google Analytics, the numbers were close enough that I didn't feel like I was losing anything I'd use, so my plan was to dump Google Analytics once the video was done.
If you have a website, or know someone who does and needs an analytics recommendation, Plausible is the one I'd point them to. Paying for the cloud version supports the project directly. If you'd rather keep everything on your own hardware, Community Edition is a few commands away, as long as you're OK with keeping it updated.
Analytics was just one step for me. The next thing on my list back then was finding an ad platform for the site that isn't as invasive as Google AdSense. With all that, I do hope you have an absolutely beautiful day.
Official References
- Plausible Analytics
- Plausible Cloud vs Community Edition
- Plausible vs Google Analytics
- Plausible data policy
- Add the tracking script
- Updated script guide (October 2025)
- Public dashboards
- Embed the dashboard
- Google Search Console integration
- Bypass ad blockers with a proxy
- Plausible Community Edition announcement
- plausible/community-edition on GitHub
- CE wiki: configuration
- CE wiki: reverse proxy
- CE wiki: upgrading
- CE wiki: Google integration
- plausible/analytics on GitHub
- v3.2.1 release notes
- Changelog
- Google Analytics: Universal Analytics shutdown
- Google Analytics: IP addresses in GA4
- Google Analytics: data retention
- Google Analytics: cookie usage

