I’ve been diving deep into the intersection of Wasm and Policy-as-Code, and I’m excited to share some of those thoughts in the blog post.

The big idea: policies shouldn’t be locked into a single DSL. With WebAssembly, we can bring speed, security, and flexibility to policy evaluation—letting developers write policies in the languages they already know (Go, Rust, TypeScript, and more).

It’s a step toward making DevSecOps more practical and developer-friendly. Would love your thoughts!

Red about it at: https://chainloop.dev/blog/introducing-webassembly-policy-engines

Best :)