SysAdmin Weekly #22: The Open Source Lifeline
When Big Tech Tightens Its Grip, Open Source Holds the Keys
TL;DR – This Week in SysAdmin Land
· Big Tech is consolidating compute, cloud, and client hardware at an unprecedented pace and open source is increasingly the only viable counterweight.
· The Steam Deck is the clearest mainstream proof that open source can compete on quality, flexibility, and user freedom, even in a consumer market dominated by locked ecosystems.
· Open source isn’t just idealism. It’s a practical, career-relevant strategy for SysAdmins managing costs, avoiding lock-in, and maintaining operational control.
· This week’s Community Signal highlights open source tools worth building into your stack right now.
· Tool of the Week: A self-hosted alternative that punches well above its weight class.
From the Console
The Locked Room Problem
I want you to think back to a time… maybe recent, maybe not, where a vendor changed something fundamental about a tool you depended on. Maybe it was a licensing model. Maybe it was a feature that got paywalled. Maybe it was an acquisition that turned your go-to platform into a product roadmap you no longer recognized.
The most recent example for me, was Firefox. And if you’ve been listening to the podcast or have read my lengthy blog post on the subject, you already know how I feel about that particular saga.
That thing I keep coming back to: that feeling of helplessness….of being locked in a room where someone else controls the door, isn’t unique to Mozilla. It’s, sadly becoming the default state of modern enterprise IT, for a number of reasons.
In issue #21, we talked about the Great Compute Divide. Big Tech is hoarding GPUs, cloud vendors are pitching you on renting your own PC BACK from them, and RAM prices have quadrupled because the market for on-prem compute is being systematically starved (whether that’s the intention or not remains to be seen). That said, the consolidation is real, it’s accelerating, and it has consequences.
So what’s the counterweight? Despite my example above being Mozilla / Firefox (which has started catering to market demands) I’d argue that the long-term counterweight is in fact open source. It’s also worth noting that I don’t mean that in the idealistic, “free software should be free” sense (though that argument has merit). I mean open source as a practical, professional survival strategy for SysAdmins.
And if you want the clearest mainstream proof that this strategy works, look no further than Valve’s Steam Deck.
Here’s a consumer device running a custom Arch Linux distribution called SteamOS that ships with full terminal access, supports arbitrary software installation, and lets you configure, break, and rebuild it however you see fit. Valve didn’t lock it down. They handed you the keys. And the result? A device with one of the most enthusiastic and capable user communities in consumer tech, running games and workloads that “shouldn’t” work because the platform respects user freedom.
That’s the open source promise made tangible…. And it’s exactly the philosophy SysAdmins need to be applying to their own stacks right now.
This is the part where you all come at me with torches and pitchforks… “But, Andy! What about support”? I would make the argument that the support question can be worked around while vendor lock-in, hardware scarcity, planned obsolesence, and adversarial behaviour towards customers are much more difficult to contend with. At least with the support question you can:
· Train up internally
· Partner with a third party
· Some Linux distros have their own support mechanisms
The other issues I laid out above have more difficult solutions for the most part.
Whatever your stance on this issue is, I would urge you, at the very least, to conduct an audit of all functions within your environment where you depend solely on a single vendor. Which of those vendors have you locked in, in some way? Those are the areas you need to at least have a fallback plan in mind in the event that things go south.
A SysAdmin Clinging to an Open Source life preserver
And now, back to our regularly scheduled programming.
🎙 Recently on the SysAdmin Weekly Podcast
SysAdmin Weekly - 039 - BitLocker, Key Escrow, and the Microsoft Trust Question
All the relevant links for this episode can be found below:
· SysAdmin Weekly Github Discussions Board
The Case for Open Source in 2026 - Beyond the Ideology
I’ve been on a practicality kick lately with my content. So, let’s get practical for a second. Building on the “From the Console” section in this week’s issue of the newsletter, here’s why open source deserves a strategic seat at the table for every SysAdmin today:
1. You Own the Exit
Proprietary software comes with a quiet hostage clause, which is sometimes spelled out (and sometimes not). When the vendor raises prices, discontinues a feature, gets acquired, or simply decides your use case no longer aligns with their roadmap, you are stuck….full stop. Open source breaks that clause. You can fork it, self-host it, freeze it at a version that works, or migrate on your terms.
This isn’t hypothetical. Looking at a few examples:
· BookStack - Open Source Wiki / Documentation App
· Gitea - Self Hosted Open Source Code Repo Software (Note: owned by a for-profit org)
· Forgejo - Self Hosted Open Source Code Repo Software
· Nextcloud - Self hosted cloud filestorage
· Restic - Awesome CLI-based backup application
These are all tools that we’ve mentioned in this newsletter before and they exist because the proprietary alternatives became untenable for a meaningful number of organizations. The community voted with their forks.
2. Auditability Is a Security Feature
Putting my security brain in place for a second, I would also make the claim that, in general, you cannot fully trust what you cannot inspect. There are some exceptions to that rule for certain software suites, sure, but I feel it’s true when speaking generalities. The fact is, that with proprietary tooling, you’re accepting a black box at the foundation of your infrastructure. With open source, the code is accessible and viewable. Security researchers can (and do) find and fix vulnerabilities more quickly because the surface is visible. Now, it’s worth noting that this isn’t always comfortable. Visibility cuts both ways, but at least it’s honest, open, and everyone can see things for what they are, warts and all.
3. Cost Control in a World of Subscription Creep
SaaS subscriptions compound quietly. Open source tools, even with self-hosting overhead, frequently deliver better TCO at scale, especially for non-glamorous infrastructure services: documentation platforms, backup tools, monitoring stacks, identity providers.
4. The Talent Pipeline Recognizes It
The next wave of SysAdmins grew up on GitHub, Linux, and Docker. Open source fluency is increasingly a hiring signal, and building an open-source-forward environment makes your org more attractive to the people you want to retain.
Core Fundamentals: Reading an Open Source Project Before You Commit
Not all open source is created equal. Before you adopt a tool and build workflow around it, here’s a quick due diligence checklist:
· Commit frequency: Is the project actively maintained? When was the last commit?
· Issue response time: Are maintainers engaged with bug reports? Or are issues piling up unanswered?
· License: MIT, Apache 2.0, and GPL all have different implications for commercial use and modification. Know which one you’re working with.
· Community size: A project with thousands of GitHub stars and an active Discord/forum is less likely to be abandoned than a solo maintainer’s side project.
· Commercial backing: Projects with a company behind them (HashiCorp, Grafana Labs, Canonical, Gitea) have longevity. That said, watch for the “open core” model that some of them offer. Open core is where the good stuff is still generally paywalled.
· Documentation quality: Poor docs are a maintenance burden. Great docs are a force multiplier.
Community Signal
High-signal community content worth your attention this week > open source edition.
awesome-selfhosted – The Community’s Master List If you only bookmark one link from this edition, make it this one! Awesome-selfhosted is a community-maintained GitHub repository cataloging hundreds of free, open source network services and web applications you can host on your own infrastructure. Organized by category, it includes stuff like: analytics and backup tools to document management, monitoring, and identity providers…etc..etc. It’s the definitive reference for SysAdmins evaluating self-hosted alternatives to SaaS platforms. Think of it as the antidote to vendor lock-in, one category at a time.
Gitea Official Migration Documentation Full disclosure: There have been some community concerns around Gitea now existing under a for-profit company (See further down re: Forgejo). That said, Gitea remains a solid git repo hosting option that still retains the open source label. This documentation is a great resource for getting started if you’ve never used Gitea before. The official documentation covers installation, systemd service configuration, access, etc. That migration angle is the key differentiator here. It’s not just “here’s how to install a thing.” It’s “here’s how to actually move the thing.” If you’ve been meaning to get your repos off a platform you don’t control, this is your starting point.
TechReviewer – Linux Hits 90% Windows Game Compatibility Milestone The Steam Deck and Proton keep coming up in this edition for good reason. They’re the clearest mainstream proof that open source can compete at scale without compromising on user experience. This piece puts hard numbers to that argument: over 5.6 million Steam Decks sold by mid-2025, 21,694 Deck Verified games, and nearly 90% of Windows titles now running on Linux via Proton. The story here really shows what happens when a platform holder commits to openness and invests in the community infrastructure to back it up. Sound familiar?
Tool of the Week
Forgejo - A community-driven fork of Gitea, born after concerns about Gitea’s governance direction under a new for-profit organization. Forgejo is a fully self-hosted Git service. Like Gitea, you can think of it like GitHub, but it’s yours and it lives in your environment. Lightweight, fast, and increasingly the preferred choice for SysAdmins who want source control without handing data to Microsoft.
Quick Win of the Week
Audit one proprietary tool in your current stack this week. Ask these three questions:
1. What does it cost annually (licensing + admin overhead)?
2. Is there a credible open source alternative?
3. What would migration realistically take?
You don’t have to move anything. Just know your options. Because the time to evaluate alternatives is before your vendor sends you a renewal notice with a 40% price increase.
Fun Retro SysAdmin Fact
The GNU Project, which is the foundation of modern open source as we know it, was announced by Richard Stallman in September 1983. That means the open source movement is older than most of the Windows Server versions you’ve probably had to decommission. And unlike those servers, it’s not going anywhere.
Until Next Week
The tools to stay independent already exist. They’re battle-tested, community-supported, and increasingly production-ready. The question isn’t whether open source is viable, the Steam Deck is one project proved that argument is over, in my opinion. The question is whether you’re building your stack in a way that keeps the exit door unlocked.
Thanks for reading and stay frosty out there!
Andy @ SysAdmin Weekly