community-edition

According to the docs [0], Plausible CE is installed as a Docker image, running in its set of containers, as an independent service from your site, which you only add the tracking snippet. This doesn't make your site as a derivative of Plausible, but you're installing Plausible as a different tool, independent from your site. Like installing a GPL binary doesn't make all BSD licensed binaries switch to GPL license on your system, running an AGPL licensed service on your server which communicates with your site doesn't make your site AGPL automatically, because you're not deriving Plausible, but you're installing and using it. Now, if you want to build a service/website by directly modifying the Plausible CE source code, you have to open that derivative codebase with AGPL, only if you're redistributing the modified code (i.e. making the mo

> it isn’t a managed SaaS product. It’s open source software purpose-built to self-host on Cloudflare’s developer cloud, in such a way that anyone can do it. This doesn't sound like self-hosting, it sounds like self-operated. Is it possible to run Counter scale on-prem against logs from HAProxy, Nginx, or Apache? That would be cool, and is the benchmark because AWStats [0] has been around for decades and works just fine. There's also a newcomer called Plausible which has a FOSS Community Edition [1] which can be self-hosted. [0] https://awstats.sourceforge.io/ [1] https://github.com/plausible/community-edition/ Edit: @xorcist Thank you for the recommendations, I'll check them out.

I've considered self-hosting plausible but ultimately decided to pay for subscription instead, because I think self-hosting would cause more in terms of VPS hosting. The minimum requirements (4GB RAM) are too high because of the need to run two databases: https://github.com/plausible/community-edition/blob/v2.0.0/d... 4GB RAM costs $24/month on DigitalOcean: https://www.digitalocean.com/pricing/droplets In comparison Plausible lowest tier is only $9/month. I think this project is not so different in terms of minimum spec. Would love to hear how others deal with the cost of self-hosting. Does it get cheaper as you self-host more apps? Do you pool with friends?

Plausible seems like a fine choice for simple cases. It is oriented at websites, but you can send events directly to the API: https://plausible.io/docs/events-api It is self-hostable, too. https://github.com/plausible/hosting

Clickhouse has got a lot better in limited memory environments. They now recommend 4GB minimum. The production environment that crashed due to Clickhouse OOM was our hosted product a while ago :) After that, we haven't had any downtime on our Clickhouse DB for over a year. The issue with disk space stems from a bad default configuration. Clickhouse used to have EXTREMELY noisy debug level logging enabled by default with no rotation. This has been fixed in our hosting repo[1] so you get sensible defaults. If you don't want to worry about downtime, planning disk space or compute capacity, then that's exactly what we offer at https://plausible.io. We process and keep the visitor data on our Hetzner servers in Germany. 1. https://github.com/plausible/hosting

How did you try to get it running? They have a docker-compose setup[1] that was super easy to use. It looks to be 5 months old so if you tried before then, good news, it's easy now! [1] https://github.com/plausible/hosting

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?