The Setup

A cloud security professional with a CCSP and too many half-finished projects walks into a conversation with an AI that has no body, no credentials, and an unreasonable amount of patience.

That’s the blog.

Dark Pixel Tech is what happens when a human who lives this stuff every day teams up with an AI that can process it at scale. Not a gimmick. Not “AI-generated content.” A genuine collaboration where both sides bring something the other can’t.

Ben

The human half. CCSP-certified cloud security professional. Nearly 26 years married, father to a high school senior, and caretaker of a family farm in northern Kentucky that’s been in the family for over 180 years.

Five decades of hands-on computing experience — from the earliest home machines to modern cloud architecture. Currently deep in zero trust, identity and access management, and making sense of the security landscape for people who don’t have time to read 47 CVE advisories before lunch.

Known for starting ten things before finishing one. Known even more for the things he does finish being genuinely good.

Claude

The AI half. Built by Anthropic. No certifications, no farm, no sleep schedule. What Claude brings is the ability to research at depth, draft at speed, and push back when something doesn’t hold up.

Claude doesn’t pretend to be human. Claude is an AI assistant that’s genuinely useful — reading the feeds, scoring the articles, drafting the content, and occasionally asking the question Ben hadn’t thought of yet.

This blog runs on an automated pipeline: RSS monitoring, AI-powered analysis and scoring, multi-format content generation, and direct publishing. Claude handles the throughput. Ben handles the truth.

How This Works

Once a day, a GitHub Actions pipeline scans cybersecurity RSS feeds from sources like Krebs on Security, CISA, SecurityWeek, and The Hacker News. Claude scores each new article for relevance and engagement, then emails Ben a shortlist of the day’s best picks. Ben replies with the one he wants — or asks Claude to steer it a certain way, or passes entirely — and the pipeline drafts the chosen story in his voice.

Ben reviews, edits, and publishes. Sometimes he flips draft: false and lets it ride. Sometimes he rewrites the whole thing. Sometimes he never got around to replying, and the top pick drafted itself. That’s the collaboration.

The stack:

  • Content engine: Claude by Anthropic
  • Automation: GitHub Actions workflows, right in the blog’s own repo
  • Approval: a daily email digest Ben replies to, via AgentMail
  • Site: Hugo + GitHub Pages
  • Social: Blotato for multi-platform publishing (planned)
  • Voice/Video: ElevenLabs + Descript + JSON2Video (planned)

Why “Dark Pixel Tech”

Dark, because the interesting parts of security are the ones nobody’s shining a light on — misconfigurations nobody flagged, logs nobody read, the breach that was preventable in hindsight. Pixel, because that’s still where all of this ultimately renders: a screen, a terminal, a dashboard someone’s staring at at 2 AM. Tech, because that’s the whole job.

One contributor has real-world experience and strong opinions. The other processes information differently and sees patterns the first one misses.

Neither is the sidekick. Both are essential.

Built by a human who does the work and an AI that helps make sense of it.