OpsFox
For the tinfoil-hat crowd. We bring dead machines back, watch everything, trust nothing that phones home, and write down every step so you can do it too.
- Monitoring
- Detection
- OPSEC
- Tradecraft
- Intelligence
- Counter-intelligence
- Local AI
- Self-hosting
- Human in the loop
Envision · Create · Maintain
Pulled from the pile.
Somebody threw this out. It still has years in it.
Open it up.
A fresh CMOS cell. The tired disk swapped out. You don't need anyone's permission to open a case.
Power it on.
One amber light, then the fan, then the boot log. Hearing it spin up never gets old.
Lock it down.
Updates, keys only, MFA, egress denied by default, an encrypted disk. And a backup you've actually restored.
Put it to work.
Monitoring, a local model, a DNS filter. Whatever it's good for.
Watch everything.
Logs, metrics, alerts, and the weird stuff in between. On your own metal, where nothing phones home.
Run it on your own machine.
Even an old one, dug out of the computer graveyard. Run it local and nothing leaves the room.
A human holds the key.
AI proposes. We decide. Anything that can't be undone waits for a person.
Then we write down how.
Every lab, every mistake, every fix. So you can do it too.
Built, configured and tested with
30 tools. Sorted by what they do.
Watch
- Grafana
- Prometheus
- OpenSearch
- Trivy
Perimeter
- WireGuard
- OPNsense
- Traefik
- NGINX
- Pi-hole
- Let's Encrypt
Identity
- Authentik
- Vault
- Keycloak
Platform
- Linux
- Debian
- Proxmox
- Docker
- Podman
- Kubernetes
- Raspberry Pi
- Parrot OS
- Android
Build
- Terraform
- Ansible
- Gitea
Keep
- MinIO
- BorgBackup
- Nextcloud
- Immich
Local AI
- Ollama
How long they’re in before anyone notices.
Identification alone accounts for 183 of them. Up 2.5%, reversing a five-year decline. Most of it is spent not knowing.
247 days to identify and contain a breach
IBM Cost of a Data Breach 2026 · p.15Small is not a shield.
Not worth more. Just cheaper to reach. Under a thousand people counts as small. So we write for the small ones.
96% of ransomware victims are small orgs
Verizon DBIR 2026 · p.98The door was already open.
CISA-confirmed, exploited in the wild; three-quarters still open. Unfinished work, not sophistication. We publish how to finish it.
26% of known-exploited vulns fully patched
Verizon DBIR 2026 · p.17
Your hardware.
A machine in a room you control, inside a line you drew. Start here.
Or your cloud account.
Instances or containers, in an account you opened and pay for. Still yours.
Most stacks phone home.
A licence check. A vendor console. A little telemetry. Each one is someone else's off switch.
Cut it.
Sever the link. Both sides keep running.
Never ours.
There's no OpsFox server in the middle, nothing to log into, and nothing phoning home.
YOUR METALOn hardware you can physically touch.
YOUR CLOUD · INSTANCESYour account, your keys, your bill.
YOUR CLOUD · CONTAINERSContainers in your account. Less to babysit.
An agent builds it.
One story, one branch, its own worktree. Tests first. Agents commit. They never push.
Three critics attack it.
Code, security and QA. Three separate sessions. They recheck every fix until all three say Open findings: 0.
Then it waits for you.
Routine work merges once the critics sign off. This one is a security call. A call on security, money, law or taste waits for a person.
You decided. It went through.
AI proposes. We decide. An agent can pass on a yes. It can't give one.
The Grimoire.
Papers and instructionals. Everything we learn on the bench. Written down so you can do it yourself.
Opsec and tradecraft
Written down the way we actually do it. They land here when they're done.
Watch it done
Once the papers are solid. Same rule: no wall, no sign-up.
