Community Calls
WASI WebGPU Demo, Train Release Model, HTTP Reuse & NATS Interface Proposal
The April 22, 2026 wasmCloud community call opens with Colin Murphy's WASI WebGPU demo running an Adobe TrustMark watermarking model as a Wasm component — about 20% faster than the CPU path and the first end-to-end WebGPU-from-a-component demo on wasmCloud. Bailey Hayes then walks through the proposed two-week automated train release model, micro-benchmark results showing a 5x throughput win from Wasmtime's HTTP reuse path, and the plan to push WebAssembly component composition into the workload deploy step. Aditya opens up his proposed first-class NATS WIT interface, which leads into a long, deep discussion with Yordis Prieto and Frank Schaffa about specifying capabilities, non-functional behavior, idempotency, and how Protobuf could become a strict subset of WIT for event sourcing.
WASI P3 Roadmap, wasmCloud Secrets Plugin & NATS Messaging Interface
The April 15, 2026 wasmCloud community call centered on the finalized Q2 roadmap, with full WASI P3 support as the headline goal for the quarter. The team walked through HTTP routing changes using the component model's External ID spec, introduced a new wasmCloud secrets plugin with typed declarative resource management, and discussed a proposed NATS-specific WIT interface for durable messaging beyond the generic event bus.
Q2 Roadmap Planning: Componentize the World, WASI P3, Multipath Routing & MCP Sandboxing
The April 8, 2026 wasmCloud community call is a full Q2 roadmap planning session, run as a collaborative Excalidraw whiteboard with DIY dot-voting. Bailey Hayes seeds high-level themes — componentize-the-world, WASI P3 readiness, LLM fuzzing, operator/platform experience — and the community fills in the gaps: SQLite/Lightstream integrations, microcontroller and tiny-device support via a slimmer Wasmtime, sandboxed MCP workloads on WebAssembly, multipath routing for workloads, named interfaces for backend selection, and a richer cron job provider. Jeremy Fleitz walks attendees through wasmCloud v2's built-in SIG store attestation and provenance for OCI artifacts, and the session closes with attendees voting on which initiatives shape the Q2 plan.
wasmCloud v2 Launch, Pod Finalizer Demo, WASI P3 Q2 Planning & Cooperative Threads
The April 1, 2026 wasmCloud community call opens with Jeremy Fleitz demoing a host pod finalizer change that cuts wasmCloud's reconciliation loop from over two minutes to roughly four seconds when a host pod dies — a bug found at KubeCon. Bailey Hayes walks through wasmCloud v2's scheduling architecture, kicks off Q2 planning with a tracked WASI P3 implementation behind a feature flag, and shares progress on the JCO reference implementation, cooperative threads in LLVM, and Joel's just-landed WASI socket support in Tokio and Mio. The call wraps with takeaways from KubeCon Europe and Wasm I/O, including a clear shift in the conversation from "what is WebAssembly?" to "how do I deploy it in production?"
wasmCloud v2.0.1 Released, KubeCon EU & Wasmcon Recap
A short March 25, 2026 wasmCloud Wednesday hosted by Jeremy Fleitz from KubeCon EU in Amsterdam. The main news: wasmCloud v2.0.1 is out (a quick follow-up to v2.0 to move wash into the wasmCloud monorepo and clean up the release build), the docs site is updated to match the v2 release, and WebAssembly is getting markedly more attention at the conferences this year — at both the Cosmonic booth and the CNCF wasmCloud Project Pavilion booth.