LOCKED: The TrueNAS Build System Debate

Note: This post reflects community discussion and iX statements up to Saturday, March 14, 2026 at approximately 8:00 AM EST.

Lighting the Fuse

Around March 10, 2026, iXsystems deprecated the public truenas/scale-build GitHub repository, moving the TrueNAS build system to internal infrastructure. The initial deprecation notice cited Secure Boot requirements and platform integrity features as the reason, but a day later, the Secure Boot reference was quietly removed, leaving just a brief deprecation notice. This kicked off a firestorm across Reddit, Lemmy, Hacker News, the TrueNAS forums, and tech press.

Since then, the conversation has been pulled in many different directions about what it means to be "open source" and whether or not this signals the beginning of paywalled features or the end of updates to the Community Edition (CE). For this post, I will try to stay on the topic of the consequences of making the build process closed while addressing secondary concerns raised by the community at the end.

Tell Me Why

What I'm going to try to gloss over is iX's reasoning behind the change. As noted above, this was initially cited as needed for Secure Boot requirements. This was a bad statement by iX, as the community quickly cited many examples of other enterprise vendors who have Secure Boot and do not have closed-source build systems.

Then the reasoning pivoted to "bad actors forking TrueNAS and selling closed-source commercial derivatives without attribution or GPL compliance, often in regions with no legal recourse."

While this is probably disturbing to a company like iX, people doing this in countries where iX has no jurisdiction is an unfortunate side-effect of having open-source software: it can be stolen at will. The community reaction to this was basically that anyone using an LLM could continue this behavior and the change will barely slow them down. Valid.

Honestly, it doesn't matter why iX did this since it's done and it's not going back. I will not try to justify or pick apart their reasoning as much as parse out what this means for myself and the homelab community going forward.

Here Comes the Boom

The T3 podcast, Episode 57 released in the midst of this controversy gave some answers which I will repeat here.

On the topic of verifying the validity of the build: one of the nice parts of open-source software is if someone builds it for me, I can build it myself from its constituent parts and we should end up with the same results. I can verify that with hashes and checksums and such. By making the build process closed source, this robs me of my ability to validate that nothing was added during the build which may be nefarious.

Kris Moore addressed this head-on by telling everyone that was never the case for TrueNAS since it's a non-deterministic build, so even doing two compilations back to back would not have yielded the same results. Therefore, there has never been a way to verify. His answer was simply, "You have to trust your vendor."

This was a tone-deaf answer in a world where people are spied on and exploited by big corporations (as well as governments) for sport. "Trust us" is a tough pill to swallow. However, his justification for this was interesting — "We use TrueNAS ourselves" was basically the cover for we won't ruin our own product out of selfishness.

I, for one, do actually trust iX. While Kris' reasoning can have some holes poked in it, unless I want to start rolling my own vibe-coded solution (I have seriously considered it and am still considering it, since I think a hybrid TrueNAS/Proxmox would be adopted at the speed of light by the community) at some point I am going to have to trust someone. Nothing in the code is hidden from inspection by the community, and the argument that we cannot verify the build (according to Kris) is invalid because we have never been able to verify it.

I don't ever stand on the idea of blind trust, but trusting iX is far from blind as all components of TrueNAS are still as open source as they ever were and just as inspectable as ever. Closing the build system hasn't removed any visibility, so while this reaction is strong, it may be a little overblown.

Battle Damage Assessment

There are other concerns brought up by the community which I will now address.

Does this mean TrueNAS will stop being free? No. The Community Edition will always be free.

Does this mean there will be no more features added? False. Features will continue to be added to the CE. iX is shifting to an "enterprise-first" development model with more internal testing before release, but still values the community for catching edge cases across diverse hardware environments.

What about paywalls? To be fair, the Enterprise Edition (EE) is a paywall, and that will remain. No features currently in CE will be paywalled. iX will continue to evaluate what features go to EE and which go to CE, and that has been the way it has always been — so no cause for alarm there.

What is all this talk about TrueNAS Connect? iX views TrueNAS Connect as a way to bring EE features to CE users willing to pay. They call it a "bridge." Users will have to evaluate for themselves whether or not there is a feature in Connect they are willing to pay for.

You Need to Calm Down

I don't see this as a the-sky-is-falling announcement. I will not stop using TrueNAS. But I will echo a sentiment expressed by Jeff Geerling on the TrueNAS forums: the reasoning here feels an awful lot like Red Hat's behind killing off CentOS. As Jeff put it, the move is directed against nefarious business opponents, but the flak tends to hit the homelabbers and hobbyists in the meanwhile. He's written extensively about this pattern before — companies making similar changes which ended up having negative consequences for the community or a product as a whole.

I truly hope that will not be the case here and history will not repeat itself. There's that trust thing again....