Community Calls
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.
Wasm Autoscaling on Kubernetes, wasmCloud 2.3.0, and the WASI Preview 3 Vote
The June 10, 2026 wasmCloud community call demonstrates Wasm runtime autoscaling on Kubernetes. Jeremy Fleitz scales a single Wasm workload from one instance to 38 at roughly 460 requests per second using KEDA and the standard HPA scale subresource on the workload deployment CRD, then Bailey Hayes demos multi-subscription workloads with wash dev, letting one workload host multiple components subscribed to distinct NATS topics with per-component config. The team discusses wasmCloud 2.3.0 with Helm-configurable NATS, a Kubernetes-native ingress story, and a new egress-control example, and looks forward to the ** launch vote** scheduled for the following day, with JCO joining Wasmtime as the second reference implementation.
wasmCloud 2.3: wasmCloud Benchmarks, WASI P3 Canary & SQLX Native Async
The June 3, 2026 wasmCloud community call walks through the wasmCloud 2.3 release — Bailey Hayes demos configurable OpenTelemetry exporters and distributed trace propagation across multiple wash dev hosts, then tours the new bare-metal Hetzner benchmarking pipeline running Criterion and iai-callgrind on every release. The team previews the WASI Preview 3 canary image (P3 launch expected next week), Jeremy Fleitz walks the Kubernetes HPA alignment work for wasm runtime autoscaling, and Bailey closes with a clean SQLX component in Rust using Tokio's native-async backend, paving the way for a deeper host-component-plugins discussion driven by Liam Randall and Victor Adossi.