← All posts
TAG

k8gentic

11 posts · browse all tags

  • 6 min readPaddy O'Cybear

    Sometimes I Don't Even Bother Running Claude Interactively

    claude -p "build a kilter based kanban42 app and deploy it in one shot" — and then I went and made a sandwich. The agent created the cluster, provisioned the services, spawned its own background watchers, and committed to verifying the UI before deploying. Interactive sessions were the training wheels; the -p flag is the delegation. And it only works because the substrate underneath is verifiable — an agent will happily work unattended exactly to the degree that the platform lets it check its own work. (Part 1 of 2 — the sequel is the post-mortem of this very run.)

    agentsk8genticdeveloper-experiencekilter
  • 6 min readPaddy O'Cybear

    The IaaS/PaaS/SaaS Singularity

    IaaS, PaaS, and SaaS were never really technology layers — they were labor layers. Each one priced a different amount of *someone else operating things for you*: raw metering when the labor was yours, a convenience markup when they ran the middle, per-seat rent when they ran the whole application. k8gentic engineering — agents operating canonical Kubernetes and open-source applications — collapses the labor that separated the layers. What's left to price when the operating expertise is an agent? Resources, plus a thin, published margin. That's the singularity, and it's why our pricing looks the way it does.

    architecturek8genticpaasagentspricing
  • 10 min readPaddy O'Cybear

    Infrastructure — Not Applications, Models, Harnesses, or Loops — Is the Product

    Your CEO vibe-coded a dashboard this morning. Then nine more. His marketing manager made him another. Where do they go? Not 'can we build it' — nobody asks that anymore. Where does it run, with auth, without leaking the revenue data it displays, without becoming ten unpatched liabilities? The industry keeps shipping developer tools — better models, harnesses, loops — but every one of those is now abundant. The scarce thing is a governed place for the output to live. THIS is the agentic revolution: infrastructure tools, not developer tools. We prove it at two scales — inside a single application (Squall, where the workflow engine is the product and the UI is AI-generated exhaust) and at the platform level, where Kilter lets you develop against the deployment and runtime infrastructure itself.

    infrastructurearchitectureagentskilterk8gentic
  • 7 min readPaddy O'Cybear

    The k8gentic Revolution: Kubernetes Made Simple, Not Easy

    Kubernetes never needed to be made easy — it needed to be simple, and it quietly became so. Easy is about you: how little you must learn before something works today. It's what PaaS sells, and the bill arrives later, as leaks and ceilings. Simple is about the system: few, coherent, composable primitives — which is what the modern substrate actually became. And agents don't need easy; effort is the one thing they have in infinite supply. They need simple, because coherence is what a read-edit-verify loop runs on. That's the k8gentic revolution: not another abstraction for the same human operator — a new operator for the real thing.

    agentsk8genticarchitecturepaas
  • 6 min readPaddy O'Cybear

    Modern Kubernetes Is Delightfully Elegant and Almost Even Small

    I mapped every Kubernetes artifact that touches one production app — an agentic ITSM platform I run — and all of its dependencies. I expected sprawl. The whole declared app is three files and about ten concepts. The elegance is real. The smallness is 'almost,' because the last mile — namespace, identity, credentials against every shared service — is synthesized at runtime by an operator, not committed to git. Two control planes, git as the handoff. A trade, not a bug — and the path to actually small is clear.

    architecturek8genticgitopsplatform
  • 5 min readPaddy O'Cybear

    Why Agentic DX and Human DX Converge on Kubernetes

    Kilter wasn't designed for agents — it was designed for Vercel-grade human developer experience. The surprise is that those turn out to be the same shape. Everything that makes a dev loop great for a human is, point for point, an agent-native property. Two audiences, one design — and the real reason a text-addressable platform ages better than a hosted console.

    developer-experienceagentsarchitecturek8gentic