Community Calls
WebGPU Demos, Namespace-Level Hosts & MySQL Connection Pooling
The May 6, 2026 wasmCloud community call packed in four demos showcasing WebGPU integration with TensorFlow.js and raw GPU compute, a major Kubernetes deployment change that moves wasmCloud hosts to namespace-level scope, a new workload configuration system for environment variables and secrets, and a MySQL connection pooling component built on WASI sockets. The call also covered the first successful automated release of wasmCloud v2.07 with CI hardening improvements.
Template Refactor, Workload Config & Environment Variables, WASI TLS
The April 29, 2026 wasmCloud community call covered a template refactor bringing Rust language support into parity with TypeScript using new handler terminology, a detailed proposal for workload configuration supporting environment variables and secrets in the wash dev loop, roadmap updates on microbenchmarking infrastructure and automated releases, and discussions on WASI TLS adoption and host component plugin architecture.
WASI WebGPU Demo, Train Release Model, HTTP Reuse & NATS Interface Proposal
The April 22, 2026 wasmCloud community call opens with Colin Murphy's WASI WebGPU demo running an Adobe TrustMark watermarking model as a Wasm component — about 20% faster than the CPU path and the first end-to-end WebGPU-from-a-component demo on wasmCloud. Bailey Hayes then walks through the proposed two-week automated train release model, micro-benchmark results showing a 5x throughput win from Wasmtime's HTTP reuse path, and the plan to push WebAssembly component composition into the workload deploy step. Aditya opens up his proposed first-class NATS WIT interface, which leads into a long, deep discussion with Yordis Prieto and Frank Schaffa about specifying capabilities, non-functional behavior, idempotency, and how Protobuf could become a strict subset of WIT for event sourcing.
WASI P3 Roadmap, wasmCloud Secrets Plugin & NATS Messaging Interface
The April 15, 2026 wasmCloud community call centered on the finalized Q2 roadmap, with full WASI P3 support as the headline goal for the quarter. The team walked through HTTP routing changes using the component model's External ID spec, introduced a new wasmCloud secrets plugin with typed declarative resource management, and discussed a proposed NATS-specific WIT interface for durable messaging beyond the generic event bus.
Q2 Roadmap Planning: Componentize the World, WASI P3, Multipath Routing & MCP Sandboxing
The April 8, 2026 wasmCloud community call is a full Q2 roadmap planning session, run as a collaborative Excalidraw whiteboard with DIY dot-voting. Bailey Hayes seeds high-level themes — componentize-the-world, WASI P3 readiness, LLM fuzzing, operator/platform experience — and the community fills in the gaps: SQLite/Lightstream integrations, microcontroller and tiny-device support via a slimmer Wasmtime, sandboxed MCP workloads on WebAssembly, multipath routing for workloads, named interfaces for backend selection, and a richer cron job provider. Jeremy Fleitz walks attendees through wasmCloud v2's built-in SIG store attestation and provenance for OCI artifacts, and the session closes with attendees voting on which initiatives shape the Q2 plan.