← All posts
TAG

architecture

15 posts · browse all tags

  • 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
  • 14 min readPaddy O'Cybear

    How to Build an Agentic Blog Engine for Complex Regulatory Environments in Under 45 Minutes

    A HIPAA-aligned publishing platform — per-post PHI sensitivity, a two-stage clinical/compliance approval, an immutable six-year audit trail, and AI reviewers — stood up in under an hour. The speed isn't the story. The story is that almost none of the compliance lives in the application. Kilter made the *right* architecture as cheap to reach as the convenient one, so the compliance surface moved off the app and into infrastructure primitives you can read: Postgres RLS, statement-level immutability triggers, Temporal workflows, Ory. And once your controls are canonical, inspectable infrastructure instead of application if-statements, a tool can walk them into the dance. That tool is Chaperone.

    architecturecomplianceagentskilterhealthcare
  • 7 min readPaddy O'Cybear

    Building an Inner-Enterprise Loop with Kilter

    Enterprises don't have one software loop — they have two. A governed outer loop for the high-risk systems facing the outside world, and a vast, fast, transient inner loop: departmental tools, harness engineering, coordination portals, per-PR previews. Source-code management was built for the code. The inner-enterprise loop is bottlenecked on something else entirely — the orchestration and configuration of *running* software. That's the artifact that now matters, and it's where Kilter lives. `kilter package` is the seam that lets the inner loop feed the outer one without either compromising the other.

    architectureplatformgitopsdeveloper-experience
  • 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
  • 7 min readPaddy O'Cybear

    GitOps Is the Control Plane

    Every platform team asks the same thing when a new deploy tool arrives — does it replace my GitOps, or feed it? Most tools answer wrong; they want to be the control plane. Kilter answers the other way. GitOps is the control plane; Kilter is an authoring tier that feeds it. Coming in late Q3, kilter apps promote seamlessly from a kilter-provisioned middle environment into pure-Kubernetes production reconciled by your ArgoCD — through your PRs, your RBAC, your audit. Same image, same chart, declared not injected.

    gitopsarchitectureplatformpaas
  • 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

    The Agentic Infrastructure Category Was Empty

    Bold claim: there is a category — the application infrastructure platform for the agentic era — and it has no occupant. Not because we missed someone, but because the economics guarantee one. Capital flows to the agent runtime, which has a clean wedge and one buyer; the infrastructure layer has the opposite — a diffuse buyer and free, agent-friendly primitives. Nobody can monetize it. That's exactly why it can be owned without a product rival.

    agentsarchitectureplatformpaas
  • 6 min readPaddy O'Cybear

    Why IDPs Are the Wrong Abstraction for the Agentic Era

    Internal Developer Platforms — Backstage, Port, Cortex — were the hottest infrastructure investment of the last five years: unify the sprawl behind one portal. Then agents arrived. Run an IDP through the agent-native test and every capability either fails read-edit-verify or becomes a second, drifting copy of the truth. The portal optimized the one surface neither human nor agent wants.

    agentsarchitectureplatformpaas
  • 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
  • 9 min readPaddy O'Cybear

    What Makes a Platform Agent-Native?

    A platform can run agents and still not be built for them. The difference is one design test, not a feature checklist: can an agent read a capability, edit it, and prove the edit worked — through text files and composable commands? Six principles fall out of that constraint, and they describe a product that looks nothing like a hosted console.

    agentsarchitectureplatformgitops