Yesterday I bragged that a single claude -p prompt built and shipped kanban42 while I made a sandwich. Then I looked at the namespace: zero pods. Here's the post-mortem — why headless agents die politely in the background — and the seven optimizations (an agent definition, blocking verbs, proof-of-done) that made the second shot land for real.
Paddington.io now runs three regions — Canada (ca-central, the original instance), USA (us-east), and EU (eu-west). Each region is an independent Miniscaler instance: its own cluster, its own data plane, the same canonical kilter stack, and your data stays where you put it. And because sovereignty is the point, the regions are only the beginning of the answer to 'where can my apps live?' — there's also on-prem kilter, any Miniscaler in the network, and your own existing Kubernetes via kilter package's operator-free ArgoCD bundles.
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.)
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.
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.
One CLI, one command, and your app is running on real Kubernetes — database, auth, and TLS wired up for you. No YAML, no lock-in, no platform tax.