Insights - Operations as Code — SWAMP

At the Agentic Conf 2026 in Hamburg, I attended Paul Stack ’s talk “Operations follows Development” and immediately knew I had to try out SWAMP .

Said and done — my impressions:

The concept is elegant: CEL expressions wire models together, secrets come from an integrated vault, extensions extend existing types without boilerplate.

Extensions are written in TypeScript — via Deno, without the Node overhead. TypeScript is where most developers already are, the type system fits well with the model concept, and Deno solves the npm chaos.

But — I ran into bundling issues: stale caches, missing helpers after extension migrations, runtime errors instead of compile-time errors. I probably would have reached for Python sooner — but that’s always a matter of taste.

SWAMP’s architecture is well thought out. CEL expressions, vault integration, the extension model — conceptually strong.

SWAMP itself still needs to mature: validation kicks in too late, stale cache errors are hard to diagnose, I struggled with small inconsistencies.

What really convinced me is the idea itself. I’ll keep at it. SWAMP has my attention.