WASI 0.3: async becomes native in WebAssembly components

2026-06-11 · Publisher : Bytecode Alliance · Domain : Cloud & DevOps

On 11 June 2026, the Bytecode Alliance releases WASI 0.3.0: WebAssembly's system interfaces are rebased on the component model's async primitives (async func, stream, future), replacing WASI 0.2's polling mechanisms.

### Background On 11 June 2026, the Bytecode Alliance announces **WASI 0.3**, with version 0.3.0 released the same day: the WASI Subgroup voted to ratify it. The release rebases WebAssembly's system interfaces on the component model's async primitives. The announcement's line: WASI 0.3 is official, and async is now native to WebAssembly components. ### Key facts - `async func`, `stream<T>` and `future<T>` become first-class constructs; they replace `pollable` resources and WASI 0.2's three-step pattern. - Completion-based async model, comparable to io_uring or IOCP, with stream error handling through independent futures. - Redesigned HTTP: new `wasi:http/service` and `wasi:http/middleware` worlds, which let you compose services directly. - Wasmtime 45 runs the latest release candidate; Wasmtime 46 will ship WASI 0.3.0 with async enabled by default. The jco toolchain supports all of WASI 0.3. - Guest toolchains for Rust, Go, JavaScript, Python and C# are in progress. ### Why it matters The lack of native async was one of the technical brakes on writing network services in composable WebAssembly. With WASI 0.3, the specification gets closer to production service needs, but the runtime and toolchain ecosystem still has to follow: release candidates and in-progress guest toolchains show adoption is at the start. For platform teams, it is a milestone to watch, not a migration trigger. ### Takeaway WASI 0.3 fixes WASI 0.2's main gap, native async; adoption will depend on the pace of runtimes and toolchains.

Tags : WebAssembly, Cloud natif, Edge, Open Source