Skip to main content

Command Palette

Search for a command to run...

Why I am Moving my AI "Agents" to the Edge (and Why You Should Too)

The "Offline" Advantage for First Responders

Updated
3 min readView as Markdown
Why I am Moving my AI "Agents" to the Edge (and Why You Should Too)
K
I'm a systems engineer in a public safety environment. The systems I keep running are the ones people reach after something has already gone wrong, which sets a different bar than most IT work — the failure isn't a bad quarter, it's a call that doesn't connect. My work sits in three places: the network and virtualization layer under emergency communications, the security posture around it, and the practical question of where AI belongs in systems that can't afford to be confidently wrong. What I keep returning to are the failures that don't announce themselves — degraded service that still passes an availability check, a vendor dependency nobody inventoried, a monitor measuring the wrong layer entirely. I run my own infrastructure for the same reason: local inference stacks, self-hosted services, hardware I own end to end. It's the only way to see how something actually fails rather than how the documentation says it will. I write that up as field notes at blog.theknowngood.com, and maintain a reference dataset on AI model evaluation at theknowngood.com. Licensed amateur radio operator, KO6JKE. Troubleshooting an RF path and debugging a network stack are closer than they look, and both matter most when the usual channels are down.

I have been watching the "Agentic AI" trend blow up on Hashnode lately. It seems like every other post is about how AI is moving from just answering questions to actually doing things—writing code, managing QA, and even handling incident triage. It is exciting stuff, but as someone who works in public safety, my first thought is always the same: What happens when the cloud goes dark?

In my line of work, we talk about "resilience" a lot. Whether it is my day job or volunteering with Sacramento CERT, you learn pretty quickly that if your tools depend on a perfect internet connection and a third-party server's uptime, you do not actually own those tools.

That is why I have been spending my nights in my home lab (shoutout to my trusty Dell T3610) moving away from the "cloud-first" mindset.

The Shift to the Edge

With the release of Gemma 4 and Qwen 3.5, the gap between "cloud AI" and "local AI" has basically evaporated for most practical tasks. I have been testing these models via Ollama, and the performance on consumer-grade hardware is getting insane.

Here is why this matters for those of us building infrastructure:

  1. Privacy is non-negotiable: If you are working with sensitive data—whether it is public safety info or just your own personal projects—sending that to a proprietary cloud model is a risk. Keeping it local means you keep the keys.

  2. True Resilience: If the grid goes sideways or the fiber gets cut, my local LLM keeps running. For an "Agent" to be useful in a real emergency, it has to be reachable.

  3. Latency: When you are running a local model on your own metal, you are not waiting on API calls or rate limits. It just works.

What is in my Stack?

I am currently leaning heavily on a self-hosted setup that looks something like this:

  • Hypervisor: VMware ESXi 8 (standard stuff, but rock solid).

  • Model Runner: Ollama, pulling the latest Qwen and Gemma weights.

  • Orchestration: Exploring how to use these local models for basic "agentic" tasks like automated log analysis and system hardening.

Why this matters

I have always liked platforms that focus on community and shared knowledge. The tech sector needs more of that "civic" mindset. We should be building systems that empower people, not just systems that make us dependent on a few giant corporations.

If you are just starting with local LLMs, my advice is to stop worrying about the benchmarks and just start building. Setup an old workstation, install Linux, and see what you can make it do without an internet connection. You might be surprised at how much power you actually have sitting under your desk.

I am curious—how many of you are actually running your "Agents" locally vs. relying on Claude or GPT-5? Let’s talk about it in the comments.

More from this blog

T

The Known Good — Field Notes

29 posts

Field notes from Kerry Kier — the writing side of The Known Good. I'm a systems engineer working across infrastructure resilience, emergency communications, and practical AI deployment. Notes on what I'm building, breaking, and figuring out: outages and how they actually fail, security architecture, self-hosted AI stacks, and the gap between what a system claims and what it does. The reference data lives at theknowngood.com. This isn't thought leadership. It's field notes.