If you manage Linux infrastructure at scale, you’ve likely experienced “The Script-Reader Wall.”
It happens when you hit a complex issue – a kernel panic under specific network loads, or a race condition in your automation – and you call for support. You quickly realise the person on the other end is simply reading a knowledge base that you’ve already searched. They aren’t troubleshooting the system; they’re troubleshooting the ticket.
For a senior sysadmin, this is more than frustrating; it’s a risk to your uptime. At Tiger Computing, we take a different approach. We believe that if you’re going to support Linux, you need to be at the coal face of developing it.
The Open Source “Upstream” Difference
In the Linux world, “Upstream” is the source. It’s where the code is born. Most support providers sit downstream, waiting for updates to arrive and hoping they work.
We choose to live upstream.
Our CTO, Chris Boot, isn’t just an enthusiast; he is an official Debian Developer. That isn’t a badge you buy; it’s a status earned through years of contributing code and maintaining the integrity of the distribution. When our team finds a bug, we don’t just “work around” it. We write the patch and send it upstream to the Debian project or the Linux kernel.
Why This Matters to Your Linux Infrastructure
You might wonder why a support provider spends billable time contributing to open-source projects like OpenVox, Claws Mail, or the kernel itself. It isn’t just about “giving back”; it’s about technical sovereignty.
- We see the bugs before you do: By being involved in the development of the tools, we know about potential regressions before they hit your production environment.
- We don’t guess: When you have a specialised team that has actually written code running in the kernel (or, in one case, on the Mars Rover), you aren’t paying for “best guesses.” You’re paying for people who can read the source code to find out exactly why a process is hung.
- We fix it for everyone: By pushing fixes upstream, we ensure that the next update won’t break your fix. We solve the problem once, properly.
We’re Your Wingmen, Not Your Replacement
We know that the majority of IT support providers don’t have the Linux skills you need. In fact, we know that you are often the most skilled person in the room.
We aren’t here to replace you or tell you how to do your job. We’re here to be the specialised resource you tap into when things get deep. We’re the people you call when you want to discuss the nuances of a filesystem, the stability of a new OpenVox release, or how a kernel update will impact your specific workload.
No Fluff, Just Linux
Tiger Computing is a “Linux-only” house. We don’t do Windows, and we don’t treat your infrastructure like a commodity. We’re a team of engineers who respect your role and the precision and care you’ve invested in your Linux estate.
When you work with us, you’re talking to peers who are as invested in the health of the Linux ecosystem as you are. We’re in the trenches, we’re submitting pull requests, and we’re active in the mailing lists where the future of the OS is decided. And we’re ready to help you push your infrastructure further.
Does your current Linux support provider speak “Kernel”?
If you’re tired of being the smartest person on the support call, let’s have a technical conversation. We can talk about migrating to OpenVox, hardening your Debian stable builds, or just how we can complement your existing team.
Get in touch with a Tiger engineer.
