Readit NewsUnlike Simple Analytics (the post authors), you deploy Counterscale to your own Cloudflare account and control the code + data end-to-end. It also uses no cookies, has no browser fingerprinting, and has no monetized SaaS offering.
It only has 90 days retention though, which could be viewed positively.
"Source Available" sounds like what it should.
It communicates that the code is public, so you can see it's high quality, actively worked on, and nothing nefarious. However, it's not meant to be a community project or used commercially for free.
"Fair Source" is abundantly less clear. It implies some sense of "fairness" which can mean drastically different things to people.
But they can?
Source available can mean everything from "proprietary, you can look but you can't touch" to "this source code is licensed under Creative Commons Attribution 4.0".
Creative Commons projects can be used in commercial projects, for free, provided you adhere to the license terms - but they do not meet the open source definition.
This is exactly the problem. "Source available" refers to such a massively wide gamut of possible licensing scenarios that it may as well be meaningless.
Sentry raised $90 million in a series E round in May 2022, and their total funding is sitting at $217 million.
No cloud provider even offers a hosted version of Sentry, so it's not like that's an issue for their business. Spinning up a VM and deploying your own version is incredibly straightforward. Which is exactly why they now need to switch licenses and put newer features behind more restrictive terms so users are forced to pay.
Sentry switched to BUSL in 2019, almost 5 years ago.[1]
Most of the aforementioned fundraising occurred after the license change (e.g. the $90MM round you mention from 2022, and another $60MM round in 2021).
The "restrictive terms" - which again, were introduced in 2019 - are that you can use the software but not use the code to compete against the software's authors. For 99.99% of users, this has been a non-issue, because most people have no interest in doing so.
Sounds like their own self-created problem.
https://opensource.google/documentation/reference/using/agpl...
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.
Probably. But it's not for that use case (for example, Counterscale intentionally strips IP addresses).
> There's also a newcomer called Plausible which has a FOSS Community Edition [1] which can be self-hosted.
One of the goals of Counterscale is that you can deploy it "fire and forget" with a single terminal command.
Contrast this to Plausible CE, which makes it clear you need some basic adminstrative skills to operate the software:
> you should have a basic understanding of the command-line and networking to successfully set it up
The point is that Counterscale is designed differently than traditional "self-hosted" solutions in order to promote ease of deploy. It comes with serious constraints (like a dependency on Cloudflare). But some people may prefer those tradeoffs.
Someone suggested "self-operated" elsewhere in the thread. Thoughts?
Deleted Comment
To say, "I can run a server that can handle a bunch of requests for free" doesn't mean much. Of course you can do that. But can you replicate the aforementioned system for free? Probably not.
The UK acts like a madman on fire trying to attack everybody.