Community Calls
WebAssembly on Kubernetes: the New wasmCloud Runtime Operator & WASI P3
The September 24, 2025 wasmCloud community call is all about running WebAssembly on Kubernetes. Lucas Fontes walks through a new Kubernetes-native runtime operator for wasmCloud v2 that stores all workload state in Kubernetes via custom resources (CRDs), aligns naming with pods, replica sets, and deployments, and replaces external capability providers with secure in-process host plugins. Bailey Hayes covers a wave of wash and setup-wash-action improvements for the next major version, and shares that Wasmtime has shipped the first WASI P3 release candidate.
wasmCloud V2: The Wasm Component Model & a Simplified Host
The September 17, 2025 wasmCloud community call is a deep dive into wasmCloud V2 — also called wasmCloud Next — Brooks Townsend's proposal for a "radical simplification" of the platform. He walks through a pull request that introduces a consolidated wasmcloud crate (merging the host, runtime, and core libraries), a simplified Host API focused on scheduling workloads built from WebAssembly components, host plugins that replace built-in capability providers and make the wRPC transport opt-in, and in-process component-to-component calls for components running on the same host. Brooks presents C4-style architecture diagrams for the new model, and Eric Gregory previews a next version of the docs.
Wasm Component Model: Plugins, Shared Memory & WASI 0.3
The September 10, 2025 wasmCloud community call started as "the quickest wasmCloud Wednesday ever" — no agenda, with the team heads-down on the last items of the Q3 roadmap — and then turned into a wide-ranging hallway conversation about the hard edges of the Wasm component model. Brooks Townsend, Colin Murphy, and Victor Adossi dig into why adding system time-zone support to Wasmtime takes a year and a half, how a wasmCloud host plugin could route around runtime bottlenecks, Christophe's shared-memory proof of concept, and why first-class functions in WIT are the missing piece for generating polyglot SDKs — all while looking ahead to what WASI 0.3 (Preview 3) unlocks.
In-Process Component Calls & the Wasm Component Model
The September 3, 2025 wasmCloud community call digs into the Wasm component model as the foundation for a leaner, more modular runtime. Brooks Townsend walks through in-process component-to-component calls — letting two components on the same host talk directly instead of going over wRPC/NATS, dropping latency from hundreds of microseconds to single-digit nanoseconds — and a broader effort to shrink the wasmCloud host's responsibility down to component lifecycle management, with capabilities provided through an optional plugin layer. Bailey Hayes closes with a quick demo of new shell auto-completions in the wash CLI.
Wasm Component Model vs Capability Providers & the wash Plugin System
The August 27, 2025 wasmCloud community call digs into how the Wasm component model is reshaping wasmCloud's architecture. Brooks Townsend tours the new wash plugin system — hooks, dev register plugins, and top-level commands, all powered by WebAssembly components — and opens a Q3 roadmap discussion with maintainer Aditya on rethinking the application abstraction and increasing provider density. Brooks and Bailey Hayes make the case for leaning into wRPC over the capability-provider SDK and for letting components, with WASI P3 on the horizon, take over many jobs that native providers do today through bin packing, dynamic linking, and Cranelift optimizations.