Open source covers a wide spectrum in practice. At one end, Radar is a clean example: Apache 2.0 licensed, single-binary, self-hostable, no telemetry, no cloud account required. The license and the architecture reinforce each other. Ivan Velichko’s container tutorial sits in the same tradition: open knowledge, reproducible from Linux primitives, no proprietary surface.

The local-LLM space complicates the picture. Zetaphor’s critique of Ollama argues that Ollama obscures its dependence on llama.cpp, ships a closed-source GUI alongside its open core, and has drifted toward cloud monetization. The critique is essentially that the open-source label does not guarantee transparency about dependencies or business direction. oobabooga/textgen is offered as a contrasting tool: no telemetry, fully offline, with a straightforward dependency chain.

Taken together, these sources suggest that open-source status is a starting condition, not a guarantee. Licensing terms, dependency transparency, telemetry posture, and monetization trajectory all determine whether a project delivers on what the label implies.