A post on Reddit, written by a user who wants to do things the old way, has reignited the debate about how open source projects distribute software. The request seems simple: where are the instructions to build Strata from source? But the discovery that the setup.sh script downloads a large unaudited binary turned a documentation question into a concrete case about trust and control.

In modern open source projects, many users run precompiled binaries without asking what they really contain. When a project offers only a binary, whoever runs it on their own machine takes on a risk: the source code does not necessarily match the program actually executed, unless the build is reproducible and verifiable. Asking to build from source is not a purist's whim, but a security practice for those who want to inspect the code or adapt it to specific contexts. In Strata's case, the lack of documentation on building from source makes this verification impossible, or at least much harder than it should be.

In on-premises and self-hosted contexts, where machines may handle sensitive data or LLM workloads, the issue is even more relevant. Installation scripts that download unaudited binaries represent a blind spot in the supply chain: if the binary contains changes not present in the source, no repository review can catch them. For teams evaluating a local pipeline for inference or fine-tuning, control over the build is an integral part of TCO and data sovereignty calculations, even if it never appears in VRAM or throughput specifications. An opaque binary shifts operational risk to the end user, who has no way to know what is being executed.

There is an interesting detail in the user's request: they admit they could ask an LLM to search the repository, but prefer to read it themselves and ask the FOSS community for help. It signals a deep need for understanding, not just a result. This attitude is consistent with those managing on-premises environments: documentation is not an accessory, but part of system maintainability. If documentation is missing, even the best automated assistant cannot replace human audit capability. The request to build from source is not nostalgia for a stricter past, but a prerequisite for those who consider software control a non-negotiable condition.

For those evaluating on-premises deployments, there are documented trade-offs on /llm-onpremise: it is not just about choosing a model, but about understanding how every component is distributed, verified, and updated. An unaudited binary is technical debt paid in trust and future operational costs. The user's question remains unanswered in the post, but its effect is clear: it made visible a lack of transparency that many took for granted. It is not the first time an open source project has been questioned over binary distribution, and it will not be the last. As local deployment becomes strategic, the community's patience is shrinking: building from source is no longer an option, but a minimum condition.