About OpsFox
Gadgets for fun. Tradecraft for real.
OpsFox is for the tinfoil-hat crowd. Devops, opsec, sigint, anonymity, and a healthy distrust of anything that phones home. We watch our own metal, run our own models, and bring dead machines back. Then we write down how, so you can too. Bring a bin of dead thin clients.
The mechanism
The fun isn’t decoration. It’s why anyone sticks with it.
Security that feels like a chore doesn’t get done. Nobody patches out of duty for very long.
That’s what keeps people coming back to the bench.
- Giving a Pi Zero a face.
- Racking thin clients out of a skip.
- Watching your own dashboards light up for the first time.
And coming back is the whole discipline.
So tinfoil hats are welcome.
Threat-model out loud. Being right about surveillance capitalism a decade early isn’t a personality disorder, and nobody here is going to tell you you’re overthinking it.
- Monitoring
- Detection
- OpSec
- Tradecraft
- SIGINT
- Anonymity
- Self-hosting
- Local AI
- E-waste rescue
- Threat modelling
In the open
Everything that leaves the bench leaves ungated.
No email wall, no “full version”, no lead-magnet PDF. When something comes off the bench, the write-up, the configs and the mistakes come with it. The code is Apache-2.0, all of it.
That’s not generosity. Gatekeeping this stuff is how people get breached. Once it’s out, read it, run it, and hand it to someone you trust to tell you if it’s any good.
Refining the tradecraft
Broken in a basement first. Trusted in production later.
The loop that turns a weekend experiment into something worth running on a network that matters. Nothing skips a step.
01. Break it in a lab.
Every technique gets proven on homelab gear first, where the blast radius is a ruined weekend instead of somebody's payroll system. That is where you find out the restore was never actually tested.
02. Write it down.
The write-up is the artifact, not a courtesy afterwards. Parts lists, configs, and the decisions that were wrong the first time. Especially those. A guide that only documents the happy path has never been followed by a stranger.
03. Clear the gate.
Nothing gets published that hasn't survived our own homelab first, and a human signs off on what clears the gate. What doesn't goes back on the bench and gets tried again.
Consultancies learn all that on someone else’s network and bill for it. The homelab crowd has done the unglamorous version for free for twenty years. All we add is the discipline to write down what happened.
Where it lands
Then it graduates onto hardware you own.
What survives the bench and the write-up gets published, whole. There’s no paid version behind it. What we publish is the tested part, and the only version there is.
- OpsFox tenancy
- None
- Nothing you run sits inside an account of ours. There is no shared plane to be a tenant of.
- Console to log into
- None
- No OpsFox pane of glass in the path between you and your own infrastructure.
- Telemetry pointed at us
- None
- Nothing phones home. Every config, runbook and dashboard lives on your box and nowhere else.
Envision. Create. Maintain.
Two doors. Take the free stuff, or come say hi.
Read the Grimoire and go. Or write to us with a question, a bug, or a dead machine you want to bring back.