Community Calls
wasmCloud Q3 2025 Roadmap: Component Model, wRPC & a Simpler Host
The July 9, 2025 wasmCloud community call was the Q3 2025 community roadmap planning session. Brooks Townsend recapped a Q2 driven largely by community contributors, then walked a slate of proposals that all push toward a simpler, more standards-aligned platform built on the Wasm component model: in-process component-to-component calls, dropping wasmCloud-specific signing for standards like Sigstore, shared platform-level capability providers, reframing providers as wRPC servers, trimming built-in WASI interfaces, reducing host responsibilities so an external scheduler drives the host, and making wasmCloud's distributed networking intentional rather than implicit. WASI Preview 3, expected in August, frames much of the work.
whamm: Wasm Instrumentation and the Component Model
The June 25, 2025 wasmCloud community call welcomes Elizabeth Gilbert, a Carnegie Mellon PhD student researching WebAssembly instrumentation, who demos whamm — a DTrace-inspired DSL for dynamic analysis that rewrites Wasm bytecode (or hooks an engine at runtime) to count calls, profile branches, and build flame graphs. The conversation turns to bringing whamm to the Wasm component model, then the maintainers declare "pull request bankruptcy" — a plan to unblock a backlog of high-quality PRs stuck behind flaky tests — and congratulate two new maintainers.
wasmCloud Postgres Transactions & the Monorepo CI Debate
The June 18, 2025 wasmCloud community call pairs a live demo with a candid project-structure debate. Brooks Townsend demos new transaction support in the wasmcloud:postgres interface — committing several SQL updates atomically through a single WebAssembly component and showing how an invalid query rolls the whole thing back. The team then opens a wide-ranging discussion on the wasmCloud monorepo: whether to keep it and invest in monorepo tooling or split repositories along language lines, how to replace Nix-based CI with GitHub Actions, and how to make contributing to wasmCloud simpler.
Building an ETL Pipeline from Wasm Components on wasmCloud
The June 11, 2025 wasmCloud community call opens with a fast-turnaround demo from Mike Nikles, who in seven days went from boxes on a whiteboard to a working drag-and-drop ETL pipeline builder running on wasmCloud. Each pipeline stage is a Wasm component — composed with wac, deployed as a wadm manifest, and wired together over NATS messaging. The discussion that follows digs into composing components statically vs. linking them dynamically with wRPC, the case for WASI P3 streams, and HTTP/2 support for agentic protocols. Brooks Townsend then kicks off the Q3 2025 roadmap planning and walks through a new consolidated NATS reference doc.
ETL Pipelines on the Wasm Component Model with wasmCloud
The June 4, 2025 wasmCloud community call is a design review for a data-processing platform built on the Wasm component model. Mike Nikles walks through an architecture diagram for a drag-and-drop ETL pipeline platform built on wasmCloud, where each pipeline step composes trusted in/out components around an untrusted customer-authored business-logic component. Brooks Townsend recognizes the design as wasmCloud's platform harness pattern, and the group works through capability providers, HTTP-server density, and lattice-per-customer versus lattice-per-pipeline isolation. With many maintainers at a Cosmonic off-site doing roadmapping, this is a lighter, feedback-focused call.