wasmCloud

A WebAssembly component runtime that runs the same host locally and on Kubernetes, wiring components to swappable capability plugins.

• Category: Runtime
• CNCF maturity: Incubating
• Language: Rust (with a Go Kubernetes operator and gateway)
• License: Apache-2.0
• Repository: wasmCloud/wasmCloud
• Documented at commit: 0c6315b (2026-06-24, near tag v2.4.0)

What it is

wasmCloud runs WebAssembly components built against the WASI 0.2 / 0.3 Component Model. A component declares the capabilities it needs through WIT interfaces (wasi:* for standard capabilities, wasmcloud:* for project-specific ones), and the host supplies those capabilities as plugins at instantiation time. The component itself stays free of vendor SDKs and transport details.

At the pinned commit the repository is built around wash (The Wasm Shell), a single CLI for scaffolding, building, inspecting, and running components. The README opens with # wash - The Wasm Shell (README.md:1). The Cargo workspace has three members: the wash CLI, the wash-runtime embedded runtime, and a benchmark crate. A Go Kubernetes operator and HTTP gateway sit alongside in runtime-operator/ and runtime-gateway/.

The point of the v2 design is that one runtime serves two front ends. Locally, wash dev drives the runtime with hot reload. In production, the Kubernetes operator drives the same runtime over gRPC. The code below the entry point is identical.

When to use it

• You want to write business logic as a polyglot WebAssembly component and let the platform inject capabilities (HTTP, key-value, blob, messaging, config) rather than linking SDKs.
• You want the same component to run on a laptop during development and on Kubernetes in production without rewriting the host wiring.
• You need a zero-trust default for outbound traffic: egress is denied unless an allowlist is set (crates/wash-runtime/src/types.rs:92).
• It is a weaker fit if you need a mature, battle-tested control plane today: the v2 runtime is a recent rewrite (see History), and several public adopters are at PoC stage.
• It is not a general container runtime; it executes Wasm components, not OCI container images.

In this deep-dive

• History: origin, milestones, and why it exists.
• Architecture: components and how requests flow.
• Adoption & Ecosystem: who runs it and what surrounds it.
• Internals: the code paths that matter, read from source.
• Getting Started: install and a first working setup.

Sources

1. wasmCloud/wasmCloud (GitHub)
2. wash - The Wasm Shell (README)
3. CNCF welcomes wasmCloud to the CNCF Incubator
4. wasmCloud (CNCF projects)
5. wasmCloud 1.0 Brings the WebAssembly Component Model to Enterprise (Cosmonic)
6. Cosmonic Componentizes wasmCloud Ecosystem
7. wasmCloud Operator: Open Source Wasm on K8s (Cosmonic)
8. WebAssembly Adoption Grows across Telco, Manufacturing, Tech
9. First look: wasmCloud and Cosmonic (InfoWorld)
10. Actors in the Cloud with wasmCloud (b-nova)