Community Calls
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?
Native WASI P3 for Go, Node.js in JCO, and Couchbase Plugins
The September 16, 2026 wasmCloud community call is three demos deep. Victor Adossi shows JCO's new Node.js SDK support running a gRPC server and an MCP server as WebAssembly components with one component-specific line each. Bailey Hayes builds two Couchbase host components — one embedding the vendor's Rust SDK, one speaking the HTTP Data API — behind a single WIT interface, and then shows the result of an all-nighter: a fork of Go that targets WASI P3 natively with component model cooperative threads, no wasip1 adapter, and no garbage-collector reentrancy trap. Yordis Prieto closes with Erik, a WebAssembly-only OpenAPI generator and linter, and a case for WIT annotations. If you care about Go WebAssembly, this is the call.
wasmCloud 2.9, Component Model 1.0, and Node.js APIs in JCO
The September 9, 2026 wasmCloud Wednesday walks through wasmCloud 2.9, shipped the day before: NATS-native workloads, a guest memory budget that is now enforced rather than advisory, and a stack of lifecycle changes that make host pods behave like ordinary Kubernetes citizens. Eric Gregory presents the release, Bailey Hayes argues wasmCloud is now the only open source multi-tenant WebAssembly on Kubernetes platform and maps the road to Component Model 1.0 and cooperative threading, and Victor Adossi demos newly landed Node.js API support in JCO — real node:path, node:dns, and node:child_process calls from inside a WebAssembly component.
wasmcloud:nats on main, Custom Go Host Plugins, Warm Pool Reclaim
September's first wasmCloud community call is a landing-week call: the wasmcloud:nats interface and its native host plugin are on main, and with them a single unified plugin configuration block, a new guest invocation duration metric, and a run of hardening fixes for draining, unbinding, and concurrent starts. Jeremy Fleitz demos a custom Go host plugin built with componentize-go, Eric Gregory ships two reference docs, and Bailey Hayes walks the warm-pool reclaim knobs that make wasm runtime autoscaling work on a real Kubernetes host — while Liam Randall reports roughly 100 workloads running in 50–60 MB of memory.
wasmCloud 2.8 Ships, a Native NATS Host Plugin, and Seven Messaging Patterns Under Test
The August 26, 2026 wasmCloud community call opens the day after wasmCloud 2.8 shipped with epoch cancellation and an async wasmcloud:messaging API. Jeremy Fleitz demos the native NATS host plugin (PR #5494) — Core NATS, JetStream, and KV as first-class host interfaces with per-workload credentials and subject grants — Eric Gregory walks the new concurrency and connections doc, and Liam Randall presents a seven-pattern NATS test matrix run on WebAssembly on Kubernetes, where six of seven patterns are clean at stock settings and a deliberately OOMed host still lost zero JetStream messages.