About Black Mesa
An engineer who doesn't take "no" from a computer.
Black Mesa is a technical contracting practice. Linux, cloud, automation, monitoring, and lately the AI that ties them together. Small enough that you talk to the person doing the work. Stubborn enough that "that's not possible" rarely survives the week.
The story
From clicking in portals to shipping platforms
Black Mesa started with a simple annoyance: enterprise-grade infrastructure work was priced for enterprises, and most of the actual value came from open source tools and a handful of engineers who understood them properly.
We made the transition from portal-based cloud management to infrastructure as code ourselves, in production, with real consequences. That is why the IaC work here is not a Terraform tutorial. It is module repos with their own release cycles, deployment repos that bump versions on their own, firewall rules in CSV files that get validated before they get applied, and the scripts nobody talks about that make it all tick.
The same instinct runs through everything else. Monitoring that reports what a check means, not just that it fired. Automation that raises its own change ticket. AI that is only allowed to touch production through the same approvals a human would need.
When the tool says it can't, we read the source. When the vendor says it won't, we write the check. When the documentation says it shouldn't, we test it. It usually can.
How we work
Four rules we don't bend
Open source first
Ansible, Terraform, CheckMK, Prometheus. Lower cost, no vendor lock-in, and when the tool can't do it, we can read the source and make it.
The whole package
Nobody buys Terraform. They buy a platform that deploys, a fleet that patches itself, a pager that stays quiet. We build the package, not the demo.
Refuse the first 'no'
'The product doesn't support that' is where we start reading the API docs. A lot of what we've fixed exists because we didn't believe the system worked the way it claimed.
Hand over the keys
Documentation that writes itself, code in your repos, a walkthrough for your team. You should be able to fire us and keep everything working.
Toolbelt
What's on the bench
Tools are how, not what. But you'll want to know we speak yours.
Working with us
What to expect
- ✓ Remote-first, working in your time zone and your repos.
- ✓ A direct line to the engineer. No account manager between you and an answer.
- ✓ Fixed scope where scope can be fixed, honest day rates where it can't.
- ✓ Everything as code, in your name, from the first commit.
- ✓ If we think something's a bad idea, we'll say so before you pay for it.
Next step
Got something a vendor said can't be done?
A short conversation is enough to know whether we can help. No sales deck, no discovery workshop, just an engineer on the other end.