Community Calls
Host Components, Epoch Interruption, and the Q3 Roadmap for WebAssembly on Kubernetes
The July 15, 2026 wasmCloud community call is a long, unusually technical one. Bailey Hayes opens with the Q3 roadmap board that came out of the previous week's planning session — host components, macro benchmarking, a Kubernetes secrets plugin, async messaging, and epoch interruption for both cancellation and yielding long-running work — then walks the stack of PRs behind host components: trigger services with their own P3 exports and their own store, passing WASI Preview 3 values across stores, and host component plugins that add capabilities at host tenancy. Frank Schaffa pushes hard on resource boundaries, which turns into the best discussion of the call: how to bound CPU without writing a scheduler, why epochs beat fuel, and where throttling metrics belong when you run WebAssembly on Kubernetes. Mike Williamson closes with a demo that compiles an rsbuild static site straight into a .wasm component.
The wasmCloud Q3 Roadmap: Build Stuff, Agentic AI, and Platform Engineering Reference Architectures
The July 8, 2026 wasmCloud community call is the Q3 roadmap planning session. Bailey Hayes opens with a Q2 retrospective — WASI Preview 3 shipped and is enabled by default, the implements feature is essentially complete, and the SQLx example landed along with upstream fixes in mio, Tokio, and socket2 — then hands the board to the community. The number one theme for Q3 is simply build stuff on top of wasmCloud, with agentic AI and MCP pulled forward, WASI WebGPU and long-running compute alongside them, and a strong pull from platform engineering teams for reference architectures that explain when a concern belongs in a workload, a service, or a host component. Jeremy Fleitz, Aditya Salunkhe, Yordis Prieto, Bharat, Colin Murphy, and Eric Gregory fill in the rest: polyglot CI tracking, NATS queue groups for autoscaling, exploded components, and a hard argument against generic messaging interfaces.
wasmCloud 2.5: Wasm Component Model implements, WASI P3 Streaming, and Cancelling Long-Running Invocations
The July 1, 2026 wasmCloud community call opens on the 2.5 release, cut the day before: Wasmtime 46, WASI Preview 3 on by default, async support, and the Wasm component model implements feature that lets one component multiplex several backends behind a single named interface. Jeremy Fleitz demos implements with Postgres — one component importing the same query interface twice as pg-user-a and pg-user-b, each bound to a different database role with different table grants — then Bharat shows cross-component streaming on WASI P3 with a Whisper model transcribing an hour-long podcast. The back half is a deep architecture discussion with Aditya Salunkhe, Bailey Hayes, and Frank Schaffa on cancelling long-running invocations with Wasmtime epoch interruption, where health checks belong, and how breaking apart stores turns a long-lived service into a workload's front door.
New People Pages, Multi-Backend Named Interfaces, and WASI Preview 3 on main
The June 24, 2026 wasmCloud community call is a short one with a couple of focused updates. Bailey Hayes opens with the new maintainer people pages and a quickstart fix from Eric Gregory, then walks through a packed status update on main: Wasmtime 46 brings the WASI 0.3.0 APIs with WASI Preview 3 enabled by default — no feature flag needed — alongside a new implements feature flag and a PR that lets a single named interface (like a key-value store) be backed by multiple plugins at once, for example Redis and NATS. The call wraps with Aditya Salunkhe's work on component-to-component linking using Wasm component model P3 types and an announcement of the July 8 roadmap planning session.
Tracking Wasmtime 46, the Component Model implements Feature, and WASI P3 Concurrency
The June 17, 2026 wasmCloud community call digs into the runtime work landing on the back of WASI Preview 3 (WASI P3). Bailey Hayes walks through wasmCloud closely tracking Wasmtime 46 — the first release to ship the WASI 0.3.0 interfaces, with WASI P3 about to be enabled by default — and demos the component-model implements feature, using static bindings to multiplex a single Postgres plugin across two isolated database users with Testcontainers. Aditya Salunkhe presents his PR for WASI P3 HTTP streaming, resource linking across components, and cross-component async streams, which opens a deep discussion of core-instance concurrency under long-running streams and how elastic hosts and autoscaling can absorb the load.