analytics

Sure, our main repository comes with a production-ready Dockerfile: https://github.com/plausible/analytics We also have a separate repository with examples and code for how to host Plausible Analytics with docker-compose: https://github.com/plausible/hosting The hosting repo includes everything you need including databases, MaxMind GeoIP database, reverse proxy for SSL, etc. We don't host with docker-compose ourselves because we want to scale our databases independently from the app server. I'm not sure I understand your question. Secrets should never be committed to source control, whether the repo is public or not. Being open source does not change how we manage secrets in the slightest. Does that answer your question?

Thanks for clearing this up. The general data points and metrics we store are not personal data. IP address is the only piece of data that we touch that is considered PII under some regulations including GDPR. The IP address is fully anonymized by hashing it together with a daily changing salt. Old salts are deleted to as to prevent re-identification: https://github.com/plausible/analytics/blob/master/lib/plaus... According to GDPR Recital 26, anonymized data does not fall within the GDPR at all because data is no longer considered “personal data” following anonymization: > The principles of data protection should therefore not apply to anonymous information, namely information which does not relate to an identified or identifiable natural person or to personal data rendered anonymous in such a manner that the data subject is not or no lo

thanks! makes sense and i'd like to see that change too! i've added the request to our github now so we'll see what can be done: https://github.com/plausible/analytics/issues/344

Plausible was not built to be a clone or a full on feature by feature replacement. It is an alternative that works for many people who think GA is complicated, slow, privacy intrusive and so on. We do try to add what we believe are 20% of GA features that 80% of GA users need without adding too much complexity. We already do support event / goal tracking and we have metadata for goals as the next big feature on our public roadmap: https://github.com/plausible/analytics/projects/1

I was curious what sort of Javasript wizardy was used to accomplish this. It appears to be lots of deleted code. Still, good for the contributor! Here is the PR https://github.com/plausible/analytics/pull/68/files

Plausible is not a Google Analytics alternative. Yes, it shows you traffic on pages, but it does not support some essential features, like proper events/goals with metadata. https://github.com/plausible/analytics/issues/134

Plausible Analytics [1] is an MIT Licensed alternative to Google Analytics. It is hosted at plausible.io but can also be self-hosted. The app server is written in Phoenix/Elixir. The self-hosted version is distributed as a Docker image. It is configured [2] with a PostgreSQL server for user data, a Clickhouse server for analytics data, and an SMTP server for transactional email. EDIT: according to markosaric, the data policy restricts the granularity of Active Users [3] to daily statistics for privacy reasons so the common Monthly Active Users (MAU) stat is not available. [1] https://github.com/plausible/analytics [2] https://docs.plausible.io/self-hosting-configuration [3] https://en.wikipedia.org/wiki/Active_users

we have the "top pages" report which includes all the pages users have viewed. you can click on any page to see the full drill down too. we only show browsers at this time but there's been a request to add browser versions too. we plan to do it but cannot promise anything in terms of timeline for when it will be done. See https://github.com/plausible/analytics/issues/151

thank you! our Self-Hosted version was possible thanks to several contributors on our GitHub https://github.com/plausible/analytics/issues One contributor from HN helped us reduce our script down to 0.7 KB from 1.4 KB or so earlier this year too... all contributions are very welcome!

I noticed that Plausible claims to measure traffic without being able to persistently identify users, but https://plausible.io/data-policy states that they store the following: hash(daily_salt + website_domain + ip_address + user_agent) There are optimizations that can help brute-force the enumeration of customer domains, browser UAs, and IP addresses (e.g. in some cases you could enumerate only residential ISPs). Update: I mis-interpreted "rotating salt" to mean something that could be re-computed on Plausible's backend. It appears that the salt is random[1] and generated on the client-side, which makes this hash much more secure. 1. https://github.com/plausible/analytics/blob/master/lib/plaus...

Fathom and Plausible are both open source: https://github.com/usefathom/fathom https://github.com/plausible/analytics

You claim that using your analytics doesn't require user consent: > "Plausible does not use cookies and does not collect any personal data. This makes us compliant with the different cookie laws and privacy regulations. It means that you are not required to annoy your visitors with a cookie notice if you’re using Plausible analytics." [1] > "Compliant with privacy regulations: Google Analytics places cookies and collects a lot of data from your visitors. You’re required to have a privacy policy, to show a cookie banner and to obtain consent for GDPR. Plausible Analytics doesn’t use cookies and doesn’t track personal data so you don’t need to annoy your visitors or worry about those prompts." [2] It would seem you are collecting PII and processing it server side (?), e.g. calculate_fingerprint here [3]. Care to explain how that doesn't req

There are also "tiny" solutions for analytics. I'm working on Plausible Analytics which is only 1.4 KB right now and provides a modern dashboard. It also doesn't use cookies and doesn't collect personal data so you're not required to show the cookie/GDPR prompts which would make tiny websites much less tiny. See https://plausible.io/ There's an issue on our Github which will help us perhaps reduce it to under 1 KB too. We're working on that https://github.com/plausible-insights/plausible/issues

I'm working on an open-source web analytics tool over at https://github.com/plausible-insights/plausible. It's currently bringing in $800/mo and growing pretty fast. The code is all MIT license and we're working to make it easier to self-host. I make money through providing a hosted version of the product. It's a similar model to Sentry or Gitlab. Open-source does not have to be libraries and frameworks, there are good opportunities to build more traditional SaaS products that can be self-hosted and you can make money by selling a hosted version. I understand that not all open-source projects can be funded this way. Once I can pay my own salary, I'm planning to set aside a percentage of revenue to fund open-source projects that Plausible itself relies on.