I'm Kenneth, and I build things that matter.
Companies gave AI the same capabilities as their employees — read email, open files, pull customer records, modify and delete work — and skipped the part where you decide what it's allowed to do. Most still can't answer three questions: What AI is running? What can it access? Can we stop it before it does something damaging?
I'm co-founder and CEO of OpsCompanion. We build Standpipe, the on-device control layer for AI: visibility into every AI tool running across your fleet, and control over what each one can see, send, and do. Enforcement runs on the machine, because the machine is the last thing you still own.
We were early. Here's the receipt.
Standpipe was already in development in May 2026. By June 2nd I had the thesis on tape — that context is king, so the only question that matters is where your context lives and who owns the box the inference runs in.
Google's Beyond Zero landed in the June 2026 issue of ACM Queue, arguing that zero trust breaks under AI agents and the trust boundary has to shrink from the application down to the individual action. Cloudflare's Agent Access Model followed in August, arguing that enforcement belongs in the harness and the network — never in the prompt.
Both are right. Both describe the machine we were already building. And both stop one step short of the conclusion: if the layer enforcing your agents is somebody else's cloud, you didn't shrink the trust boundary — you rented it. That last step is the one we took first, and it's why Standpipe runs on your hardware instead of ours.
We call it sovereign intelligence: you own the data going in, the box it runs in, and the output that comes out. End to end, bolt to bolt. Anything less and you cannot say who else has been in the chain.
Before this, I spent years in the trenches — infrastructure at Cloudflare, AI-driven platforms at Balto, advising startups, and doing technical due diligence for VCs. I know what breaks at scale because I've been the one paged at 3am to fix it.
Your business is too important to run on someone else's terms.
Find me on x (twitter) and LinkedIn — my DMs are open.