Counterscale and the New Self-Hosted
benv.ca
benv.ca
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.
For me, the fundamental issue is whether I am controlling what code is out there, I'm paying the pure infrastructure costs, etc. So whether it's self-hosted or self-operated doesn't matter.
For some it sounds like if you aren't managing it at the operating system level then it isn't self-hosted.
AWstats hasn't been updated since the times when screens were tiny. Try GoAccess for a more modern look (it has nothing to do with the Go language) but still a bog standard static log analyzer that can generate HTML reports periodically.
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.
Clickhouse says the minimum amount of RAM it needs is 8gb. Kafka also needs multiple GB of ram. How small an instance will you get away with?
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.
I wouldn't choose kafka for this setup as you could just use ch for everything
My definition of self-hosted isn't the same as your definition.
Lot of folks walked on cloudflare after they tried to shake down $120k from one of its customers that was publicized on the internet
There is stream of unhappy (rightfully so) cloudflare enterprise users that CF seems oblivious about.
But the damage is done. We are moving to Fastly. Sucks because we built so much around Cloudflare.
Are there concerns about getting locked into Fastly’s cloud services instead of Cloudflare’s? Will you use some level of abstraction to make the deployment more portable, or that’s another bridge to cross if needed?
It is the single solitary only lever anyone has in the world we've built.
Someone suggested "self-operated" elsewhere in the thread. Thoughts?
I'm not sure where to draw the line to differentiate it from a SaaS. For example Salesforce is clearly SaaS, but is also an application platform with a built-in database.
There is also SST for instance which is also sitting in there somewhere with a similar thing. It’s not quite self hosted but also not quite PaaS.
For my analytics platform [0], I chose to go only with a paid self-hosted version. This way, the business model is aligned with the success of the self-hosted product. It's also nice to be able to provide support for self-hosting, to those who need it.