Plausible Analytics: a cookie-free Google Analytics replacement you can run yourself
Open source, privacy-first web analytics. Lightweight, cookie-free Google Analytics alternative. Self-hosted or cloud.
At a glance
- What is it?
- Plausible Analytics is an open source, privacy-first web analytics tool written in Elixir. This review covers what it does, how it works, how to run it, and where the self-hosted Community Edition falls short.
- Who is it for?
- Adopt Plausible if you want cookie-free, GDPR-friendly analytics and are willing to either pay for the managed cloud or operate your own infrastructure. Do not adopt it if you need deep custom reporting, raw event-level data, or a zero-maintenance self-hosted setup, because the Community Edition puts all operations on you.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Elixir, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What Plausible actually solves
Plausible targets a specific pain: Google Analytics is free, but it tracks individuals, sets cookies, and creates compliance overhead. Plausible measures traffic without personal data, IP addresses, cookies, or persistent identifiers. The README claims full compliance with GDPR, CCPA, and PECR. That claim is the core product. The tool is for site owners who want basic metrics like page views, referrers, and conversions without a consent banner. It is also for teams that want to leave the AdTech ecosystem entirely. The project is backed by a subscription model, not by advertising. That is the whole pitch, and it is a coherent one.
How the tracking mechanism works
Plausible uses a lightweight JavaScript script that you embed on your pages. The README says the script is tiny and that you can also send events directly to an events API. The script supports SPAs out of the box, including pushState and hash-based routing. That means it does not rely on page reloads to count views. Instead of setting cookies, it sends anonymous events to the Plausible backend. The backend aggregates those events into stats. The dashboard shows all key insights on a single page, with no custom report builder. There is also a stats API and CSV export, so you can pull data out programmatically. The design choice is to discard individual-level data at collection time, which is what makes it privacy-friendly, but it also means you cannot ever go back and segment users after the fact.
Running the Community Edition: what the README tells you
The README points to a separate self-hosted solution called Plausible Community Edition (CE). It is free as in beer, but the README is explicit that you manage everything yourself: installation, maintenance, upgrades, server capacity, uptime, backup, security, and loading time. The cloud version takes about two minutes to set up and includes a CDN, high availability, and backups. The CE does not. The README does not give the actual docker-compose commands or config keys in the truncated portion, so you need to go to the docs for those. What is clear is that the CE is not a turnkey appliance. You need a server and you need to operate it. The release schedule also differs: the cloud gets updates multiple times per week, while the CE is described as a long-lived release. That gap matters if you want new features quickly.
The real limitations of the self-hosted path
The biggest limitation is operational burden. The README lists infrastructure management as your job, and that is not a small list. You are responsible for backups, uptime, and security. The CE uses a stack that likely includes ClickHouse and Postgres, based on the project's architecture, but the README does not confirm exact components in the truncated text. If your site has high traffic, you need to scale the database and the web server yourself. Another limitation is the data model. Because Plausible does not store IP addresses or persistent identifiers, you cannot do user-level analysis, session replay, or cross-device tracking. That is by design, but it means the tool is wrong for anyone who needs those features. Also, the AGPL-3.0 license means that if you modify the code and offer it as a network service, you may need to release your changes. That is a real constraint for companies that want to fork it internally without sharing.
Alternatives and the difference in approach
The obvious alternative is Google Analytics, which is free but tracks individuals and requires consent management. The difference is not just price, it is the data model. Google Analytics stores user-level data and lets you build custom funnels and audiences. Plausible aggregates at the event level and throws away identifiers. Another alternative is Matomo, which is also open source and privacy-focused, but Matomo historically allows you to store raw logs and do more granular analysis. Matomo is heavier and more complex, which is the trade-off. Plausible chooses simplicity over depth. If you need advanced segmentation or custom reports, Matomo or Google Analytics are better fits. If you want a single-page dashboard and no cookies, Plausible is the cleaner choice.
Integrations and reporting features
The README lists several integrations that extend the basic dashboard. You can track goals, conversions, revenue attribution, and funnels using custom events and dimensions. There is codeless tracking for outbound link clicks, form completions, file downloads, and 404 pages. That means you do not have to write JavaScript for common conversion events. For reporting, you get weekly or monthly email or Slack reports, including traffic spike and drop notifications. You can invite team members with role-based access, and you can share dashboards publicly via a link. Google Search Console integration brings keyword data into the dashboard. The events API lets you send events directly from your backend, which is useful for server-side tracking. These features are all documented as available, but the README does not specify which ones are in the Community Edition versus the cloud. That is a gap you need to check in the docs before self-hosting.
Maintenance, upgrade cost, and license implications
Maintenance cost is the main hidden expense of the Community Edition. The README says you handle installation, upgrades, and backups. Upgrades are not trivial because the project has a database schema that evolves with each release. You need to test migrations and manage downtime. The cloud version avoids that entirely, but you pay a subscription. The license is AGPL-3.0, which is a strong copyleft license. If you modify the source and run it as a network service, you may be required to offer the modified source to users. That is a legal consideration, not a technical one, but it affects how you can use the code internally. For most self-hosters who do not modify the code, the license is fine. For SaaS companies that want to embed Plausible into their own product, the AGPL is a serious constraint. The README does not offer a commercial license, so the cloud subscription is the only way to support the project financially.
Editorial conclusion
Adopt Plausible if you want cookie-free, GDPR-friendly analytics and are willing to either pay for the managed cloud or operate your own infrastructure. Do not adopt it if you need deep custom reporting, raw event-level data, or a zero-maintenance self-hosted setup, because the Community Edition puts all operations on you. Before committing, verify that your traffic volume fits the single-server model, that you can handle ClickHouse and Postgres upgrades, and that the AGPL-3.0 license fits how you distribute or modify the software.
Community notes