Community Calls
wasmCloud 2.11: Wasm Runtime Autoscaling at 42,000 Workloads per Core, and TypeScript via Perry
The October 21, 2026 wasmCloud community call came the day after the wasmCloud 2.11 release, which turns its policy enforcement points to deny by default. Victor Adossi showed that a single pinned CPU core and a 512 MiB memory budget now hold 4,000 warm or 42,000 scale-to-zero HTTP components. These numbers are the kind of evidence that wasm runtime autoscaling depends on. He then demonstrated JCO running TypeScript compiled to a kilobyte-sized WebAssembly component by Perry, with no JavaScript engine inside.
Deny-by-Default Hosts, a Rust WebAssembly Toolchain Trap, and a RISC-V Sandbox
On the October 14, 2026 wasmCloud community call, Bailey Hayes warned that the next host release turns its newest policy controls (guest memory, socket egress, and hostPath volumes) to deny by default. She also explained a Rust WebAssembly guest-toolchain bug that makes some WASI P3 components trap on Wasmtime 48. Aditya Salunkhe then proposed a host component plugin that gives every workload its own RISC-V Linux sandbox, and the call turned into a discussion of why open standards win.
wasmCloud Q4 Roadmap: Python SDK, Wasm vs. Containers, AI Policy
The October 7, 2026 wasmCloud community call was the Q4 planning session. Bailey Hayes named three big rocks for the quarter: a Python SDK, workload identity, and an expanded k6 suite that benchmarks WebAssembly on Kubernetes against the same app in containers and microVMs. The second half became a long discussion with Aditya Salunkhe, Yordis Prieto, and Frank Schaffa about AI-assisted contributions. It ended with a fourth rock: a permissive, written AI policy and agent stack for the project.
wasmCloud Q4 Roadmap: Python, Workload Identity, Wasm Components
The September 30, 2026 wasmCloud community call was the last of Q3 and a preview of the Q4 roadmap before next week's collaborative planning session. Bailey Hayes walked through the draft in discussion #5619. It has four themes: the wasm component model ecosystem (a Python SDK is the likely next language), performance (a customizable precompiled-component cache, exploded components that deduplicate language runtimes, and k6 load tests), integration (S3 for WASI Blobstore and declarative storage grants), and workload identity with credential brokering, which she called the quarter's biggest rock. Jeremy Fleitz showed a k6 load-test harness that has already found a local-routing bug.
wasmCloud 2.10, S3 Blob Storage, and Wasm Component Model Design
The September 23, 2026 wasmCloud community call opens the day after wasmCloud 2.10 shipped: Bailey Hayes walks the release (spec-conformant OpenTelemetry, host-wide mTLS client identity with rotation, enforced plugin egress, Wasmtime 48, Go 1.27, and a published all-features image) and sketches Q4. Aditya Salunkhe proposes S3, Azure, and GCP support for WASI Blobstore through Apache's object_store crate, and that turns into the call's real subject — a wasm component model design question: when do you write a WIT interface, when do you reach for gRPC or HTTP, and which implementation should back it? Bailey's answer is one question: does it need to compose?