bentlegen

It stopped being relevant because its content became acceptable on major social networks, beginning in late 2022.

> However, it's not meant to be a community project or used commercially for free.

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.

> Is it possible to run Counter scale on-prem against logs from HAProxy, Nginx, or Apache?

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.

What terminology would you use instead to differentiate it from a SaaS solution?

Someone suggested "self-operated" elsewhere in the thread. Thoughts?

Because those are the underlying services that the above software is built on. And they allow the system to handle both very few to many many requests/sec for basically $0. That's the point of the article.

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.

Maybe self-operated is better terminology -- that's fair. (Though I think one of the key points is that there is almost nothing to operate.)

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.

I don't work for Cloudflare?

Can you do 100k requests/day for free running Kafka, Clickhouse, nginx, some queue-draining code, etc?

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?