# WASI Published articles for WASI. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## wasmCloud 2.5.0: Wasmtime 46, WASI 0.3, and multiplexed WebAssembly host plugins DevFeed: [wasmCloud 2.5.0: Wasmtime 46, WASI 0.3, and multiplexed WebAssembly host plugins]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [wasm](), [Streaming]() Tags: [helm](), [release](), [streaming](), [wasi](), [wasm](), [webassembly]() ### AI overview wasmCloud 2.5.0 is released with Wasmtime 46 and WASI 0.3 enabled by default. It adds configurable top-level WebAssembly proposals, multiplexed host-plugin interfaces, async-shaped and WIT improvements, Helm chart hardening, a host-controller refactor, and quality-of-life fixes. ### Source excerpt wasmCloud 2.5.0 ships with Wasmtime 46, WASI 0.3 on by default, configurable WebAssembly proposals, and `(implements ..)` multiplexing for host plugins. ## WASI 0.3 Launched DevFeed: [WASI 0.3 Launched]() Original publisher: [Read original article]() Author: \["Bailey Hayes", "Yosh Wuyts"\] Published: 2026-06-11T00:00:00Z Content type: release Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [toolchain]() Tags: [async](), [component](), [components](), [native](), [support](), [toolchain](), [wasi](), [webassembly]() ### AI overview WASI 0.3.0 has been ratified as a stable specification. It rebases WASI on the WebAssembly Component Model's native async primitives, making most changes from WASI 0.2 mechanical and simplifying interface signatures. Runtime and toolchain support is beginning to land. ### Source excerpt WASI 0.3 is official, and async is now native to WebAssembly Components. The WASI Subgroup voted to ratify WASI 0.3.0, rebasing WASI onto the WebAssembly Component Model's async primitives. The 0.3.0 specification is now stable, and runtime and toolchain support is landing now. ## The Road to Component Model 1.0 DevFeed: [The Road to Component Model 1.0]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-06-08T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [wasm](), [browser]() Tags: [apis](), [architecture](), [async](), [binaries](), [browser](), [compatibility](), [interfaces](), [polyfill](), [production](), [wasi](), [wasm](), [webassembly]() ### AI overview This article explains the path toward a stable, formally specified WebAssembly Component Model 1.0. It reviews how the Component Model and WASI relate, describes the Component Model as a foundational layer with WASI providing system-resource interfaces, and notes that both are already used in production while their specifications continue to evolve. ### Source excerpt WASI P3 is almost here, bringing native async support to the WebAssembly System Interface (WASI) and Component Model. In this post, we're looking to the next big milestone: a stable, formally specified Component Model 1.0. At February's Bytecode Alliance Plumbers Summit, Luke Wagner and Alex Crichton gave a preview of what the path to a stable 1.0 actually looks like. At Wasm I/O 2026 in Barcelona in March, Luke expanded on that vision. So let's take a look at where the Component Model is heading. ## wasmCloud 2.2.0: TLS for WebAssembly, customizable HTTP egress DevFeed: [wasmCloud 2.2.0: TLS for WebAssembly, customizable HTTP egress]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-05-21T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [HTTP](), [TLS (Transport Layer Security)]() Tags: [config](), [handler](), [hardening](), [http](), [middleware](), [release](), [rpc](), [tls](), [wasi](), [webassembly]() ### AI overview wasmCloud 2.2.0 adds native TLS for WebAssembly components through WASI Preview 3, a pluggable HTTP egress handler, an expanded wash config command, and runtime-operator hardening. The release also supports customizable TLS providers and embedder-controlled outbound request handling. ### Source excerpt wasmCloud 2.2.0 brings WASI Preview 3 TLS to WebAssembly components, a pluggable OutgoingHandler trait for HTTP egress, an expanded wash config command, and runtime-operator hardening. ## wasmCloud 2.1.0: Namespaced hosts, native routing DevFeed: [wasmCloud 2.1.0: Namespaced hosts, native routing]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-05-07T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [Kubernetes](), [Routing (disambiguation)](), [networking](), [Deployment]() Tags: [benchmarks](), [kubernetes](), [plugin](), [preview](), [routing](), [services](), [wasi]() ### AI overview wasmCloud 2.1.0 introduces namespace-scoped Host CRDs, Kubernetes-native Service routing, plugin support in services, HTTP microbenchmarks, and a WASI P3 preview. The release also adds controls for multi-tenant host isolation and namespaced access management. ### Source excerpt wasmCloud 2.1.0 brings namespace-scoped Host CRDs, Kubernetes-native Service routing, plugin support in services, HTTP benchmarks, and a WASI P3 preview. ## Q2 2026 Roadmap Recap DevFeed: [Q2 2026 Roadmap Recap]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-04-15T00:00:00Z Content type: article Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [Kubernetes](), [Orchestration]() Tags: [kubernetes](), [wasi](), [wasmcloud](), [webassembly]() ### AI overview A recap of wasmCloud's Q2 2026 roadmap, focusing on bringing WASI P3 support toward production readiness and tracking related implementation work, while also covering Kubernetes integrations, host plugins, observability, and security priorities. ### Source excerpt The Q2 2026 wasmCloud roadmap: WASI P3 support, Kubernetes integrations, host plugins, observability, and security priorities. ## wasmCloud v2.0 is here DevFeed: [wasmCloud v2.0 is here]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-03-23T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [wasm](), [WebAssembly](), [Cloud Native Ecosystem](), [Kubernetes](), [Command-line interface](), [Containers](), [Development]() Tags: [cli](), [cloud-native](), [containers](), [go](), [kubernetes](), [native](), [operator](), [rust](), [typescript](), [vendor-lock-in](), [wasi](), [wasm](), [wasm-components](), [wasmcloud](), [webassembly]() ### AI overview wasmCloud v2.0 is a redesigned platform for deploying WebAssembly workloads across clouds, Kubernetes clusters, datacenters, and edge locations. The release introduces a simplified runtime architecture, Kubernetes-native scheduling, Wasm Shell, a workload API, and a Kubernetes Operator. ### Source excerpt wasmCloud v2.0 is a reimagining of the wasmCloud platform: Kubernetes-native, radically simplified, and more powerful than ever. ## Our Next Plumbers Summit event - February 25 & 26, 2026 DevFeed: [Our Next Plumbers Summit event - February 25 & 26, 2026]() Original publisher: [Read original article]() Author: David Bryant Published: 2026-02-11T00:00:00Z Content type: news Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [wasm](), [Maintainers](), [Go Language](), [JavaScript]() Tags: [2026](), [c-plus-plus](), [c-sharp](), [community](), [event](), [go](), [javascript](), [maintainers](), [remote](), [rust](), [summit](), [wasi](), [webassembly]() ### AI overview The Bytecode Alliance announces its next online Plumbers Summit, scheduled for February 25-26, 2026. The event will cover WebAssembly plans, hosted-project developments, Wasm tooling, and collaboration among maintainers, platform developers, and users. ### Source excerpt The Bytecode Alliance is pleased to invite you to the next installment in our ongoing Plumbers Summits event series, each designed to bring our members and community together to collectively contribute to the strategic planning for the upcoming year. Our next event will be held Wednesday and Thursday, February 25 and 26, 2026. This will be an all online event, supporting full remote participation for anyone anywhere, with sessions recorded so they can be watched anytime afterward via our YouTube channel ## WebAssembly as a Python extension platform DevFeed: [WebAssembly as a Python extension platform]() Original publisher: [Read original article]() Published: 2026-01-01T21:21:19Z Content type: article Language: en Sources: [Chris Wellons]() Topics: [Python](), [WebAssembly](), [Extension](), [Programming](), [C](), [SQLite]() Tags: [c](), [development-tools](), [extension](), [performance](), [python](), [wasi](), [wasm](), [webassembly]() ### AI overview The article examines WebAssembly as an extension platform for Python. It explains how architecture-independent Wasm modules can be distributed inside Python libraries without requiring a native toolchain, while noting that Wasm sandboxes cannot access external interfaces. It compares wasm3 and wasmtime-py, highlighting wasmtime-py's broader binary distribution and substantially better performance, alongside its larger installation size. ### Source excerpt Software above some complexity level tends to sport an extension language, becoming a kind of software platform itself. Lua fills this role well, and of course there's JavaScript for web technologies. WebAssembly generalizes this, and any Wasm-targeting programming language can extend a Wasm-hosting application. It has more friction than supplying a script in a text file, but extension authors can write in their language of choice, and use more polished development tools -- debugging, testing, etc. -- than typically available for a typical extension language. Python is traditionally extended through native code behind a C interface, but it's recently become practical to extend Python with Wasm. That is we can ship an architecture-independent Wasm blob inside a Python library, and use it without requiring a native toolchain on the host system. Let's discuss two different use cases and their pitfalls. Normally we'd extend Python in order to access an external interface that Python cannot access on its own. Wasm runs in a sandbox with no access to the outside world whatsoever, so it obviously isn't useful for that case. Extensions may also grant Python more speed, which is one of Wasm's main selling points. We can also use Wasm to access embeddable capabilities written in a different programming language which do not require external access. For preferred non-WASI Wasm runtime is Volodymyr Shymanskyy's wasm3. It's plain old C and very friendly to embedding in the same was as, say, SQLite. Performance is middling, though a C program running on wasm3 is still quite a bit faster than an equivalent Python program. It has Python bindings, pywasm3, but it's distributed only in source code form. That is, the host machine must have a C toolchain in order to use pywasm3, which defeats my purposes here. If there's a C toolchain, I might as well just use that instead of going through Wasm. For the use cases in this article, the best option is wasmtime-py. The distribution includes ## WasmCon NA 2025 Liveblog DevFeed: [WasmCon NA 2025 Liveblog]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2025-11-10T00:00:00Z Content type: news Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [wasm](), [Concurrency](), [Streaming]() Tags: [2025](), [concurrency](), [kubecon](), [kubecon-na](), [streaming](), [support](), [wasi](), [webassembly]() ### AI overview A liveblog from WasmCon at KubeCon + CloudNativeCon NA 2025 covers WebAssembly's evolution, WASI P3, the Component Model, language-integrated concurrency, streaming, and approaches to reducing unnecessary copying. ### Source excerpt Live coverage of WasmCon at KubeCon NA 2025 in Atlanta: WASI P3, the Component Model, language support, and the future of WebAssembly in production. ## wasmCloud at KubeCon + CloudNativeCon NA 2025 DevFeed: [wasmCloud at KubeCon + CloudNativeCon NA 2025]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2025-11-05T00:00:00Z Content type: news Language: en Sources: [wasmCloud Blog]() Topics: [Cloud](), [Cloud Native Ecosystem](), [Orchestration](), [Instrumentation](), [linkerd](), [webgpu](), [GitOps]() Tags: [cloud-native](), [gitops](), [instrumentation](), [kubecon](), [linkerd](), [maintainers](), [talks](), [wasi](), [wasmcloud](), [webgpu]() ### AI overview wasmCloud announces its presence at KubeCon + CloudNativeCon NA 2025 in Atlanta, including a project kiosk and maintainer and contributor presentations on service meshes, Wasm instrumentation, WASI WebGPU, GitOps with Wasm workloads, and related topics. ### Source excerpt Meet wasmCloud at KubeCon + CloudNativeCon NA 2025 in Atlanta: project booth, maintainer talks on service meshes, WASI WebGPU, GitOps, and more. ## Introducing the next-generation wasmCloud runtime DevFeed: [Introducing the next-generation wasmCloud runtime]() Original publisher: [Read original article]() Author: Brooks Townsend; Eric Gregory Published: 2025-11-05T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [wasm](), [Rust](), [API](), [Kubernetes]() Tags: [feature-flags](), [kubernetes](), [messaging](), [rust](), [wasi](), [wasmcloud](), [webassembly]() ### AI overview The article announces wash-runtime, a Rust crate that wraps Wasmtime to provide an ergonomic runtime and workload API for executing WebAssembly components with built-in WASI support. It describes how the design simplifies wasmCloud's architecture and supports embedding, plugins, NATS subscriptions, and future wasmCloud initiatives. ### Source excerpt The wash-runtime crate simplifies wasmCloud's architecture into an ergonomic WebAssembly host, paving the way for wasmCloud v2. ## Introducing wasi-grpc for Spin DevFeed: [Introducing wasi-grpc for Spin]() Original publisher: [Read original article]() Author: Brian Hardock Published: 2025-09-08T12:00:00Z Content type: release Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [gRPC](), [Cloud Native Ecosystem](), [Cloud APIs]() Tags: [2](), [apis](), [components](), [http](), [service](), [wasi]() ### AI overview Spin 3.4 adds outbound HTTP/2 support, allowing components to function as gRPC clients and enabling Spin applications to connect directly to existing gRPC systems, cloud APIs, and service meshes. ### Source excerpt Spin 3.4 introduces outbound HTTP/2 support, enabling components to act as first-class gRPC clients. Spin applications can now call into existing gRPC-based systems, cloud APIs, and service meshes directly, without workarounds. ## Securely Signing WebAssembly Components with Cosign (OIDC) DevFeed: [Securely Signing WebAssembly Components with Cosign (OIDC)]() Original publisher: [Read original article]() Author: Liam Randall Published: 2025-09-02T00:00:00Z Content type: tutorial Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [sigstore](), [GitHub Container Registry](), [OpenID connect (OIDC)](), [Rust](), [Command-line interface](), [Authentication](), [Security]() Tags: [authentication](), [cli](), [cosign](), [github-container-registry](), [integrity](), [oci-registry](), [oidc](), [registry](), [security](), [signing](), [sigstore](), [supply-chain](), [supply-chain-security](), [verify](), [wasi](), [wasm-components](), [wasmcloud](), [webassembly](), [webassembly-wasmcloud-security-cosign-oidc-signing-oci-registry-supply-chain-security-wasi-wasm-comp]() ### AI overview A tutorial showing how to build a Rust-based WebAssembly component, sign it with Sigstore Cosign using OIDC identity, push it to GitHub Container Registry, and verify it before execution. ### Source excerpt Build, sign, and verify WebAssembly component artifacts using Sigstore's cosign with OIDC identity--secure, registry-native signatures for wasmCloud. ## The Current State of the WebAssembly System Interface (WASI) Standard and WASIp3 DevFeed: [The Current State of the WebAssembly System Interface (WASI) Standard and WASIp3]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2025-05-14T12:00:00Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly]() Tags: [standard](), [wasi](), [webassembly]() ### AI overview The article discusses the current state of the WebAssembly System Interface (WASI) standard and the upcoming WASIp3 release. ### Source excerpt Learn about the current state of the WebAssembly System Interface (WASI) standard, and the upcoming WASIp3 release ## Node.js 20.16.0 (LTS) DevFeed: [Node.js 20.16.0 (LTS)]() Original publisher: [Read original article]() Published: 2024-07-24T12:29:52Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [cross-platform](), [Open Source](), [tracing](), [Command-line interface](), [Chrome]() Tags: [chrome](), [command-line](), [cross-platform](), [javascript](), [lts](), [node-js](), [open-source](), [openssl](), [servers](), [tracing](), [wasi](), [web]() ### AI overview Node.js 20.16.0 is an LTS release that adds a way to conditionally load built-in modules from a globally available function. It also updates OpenSSL-related behavior, improves profiling behavior with Chrome DevTools, and includes documentation, networking, WASI, test runner, utility, buffer, benchmarking, and build changes. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Announcing Spin 2.6 DevFeed: [Announcing Spin 2.6]() Original publisher: [Read original article]() Author: Mikkel Mørk Hegnhøj Published: 2024-06-24T12:00:00Z Content type: release Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly]() Tags: [components](), [registries](), [wasi](), [webassembly]() ### AI overview An announcement for Spin 2.6 covering experiments with WebAssembly Components, WASI 0.2.0, and registries. ### Source excerpt Experimenting with WebAssembly Components, WASI 0.2.0 and Registries in Spin 2.6 ## Announcing Spin Test DevFeed: [Announcing Spin Test]() Original publisher: [Read original article]() Author: Melissa Klein Published: 2024-05-08T12:00:00Z Content type: release Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly]() Tags: [announce](), [plugin](), [release](), [wasi](), [webassembly]() ### AI overview Fermyon announces the first alpha release of spin-test, a plugin for testing WebAssembly applications built with Spin using configurable mocks for Spin and WASI APIs. ### Source excerpt Today we're happy to announce the very first alpha release of spin-test, a plugin for that runs tests written in WebAssembly against a Spin application where all Spin and WASI APIs are configurable mocks. ## WebAssembly, WASI, and the Component Model DevFeed: [WebAssembly, WASI, and the Component Model]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2023-10-09T12:00:00Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly](), [Serverless](), [browsers]() Tags: [component](), [serverless](), [wasi](), [webassembly]() ### AI overview WebAssembly has expanded beyond browser use to support multiple languages and environments. WASI provides system interaction capabilities, and Fermyon's Spin platform uses WebAssembly for serverless functions. ### Source excerpt WebAssembly has evolved to support many languages and environments beyond browsers, enhanced by WASI for system interactions, and is utilized in Fermyon's Spin platform for serverless functions. ## Fermyon Spin with Rust setup guide DevFeed: [Fermyon Spin with Rust setup guide]() Original publisher: [Read original article]() Author: James Sinkala Published: 2023-06-27T00:00:00Z Content type: tutorial Language: en Sources: [Turso Blog]() Topics: [Deployment](), [Turso](), [Rust](), [libSQL](), [Command-line interface](), [SDKs](), [Database]() Tags: [cli](), [curl](), [database](), [deployment](), [guide](), [libsql](), [rust](), [sdk](), [toolchain](), [turso](), [tutorial](), [wasi]() ### AI overview A setup guide for deploying a Rust route component to Fermyon Spin that queries a Turso database. It covers installing the required CLIs and WASI toolchain, creating a Turso database, generating a Spin project, building and testing it locally, deploying it remotely, and adding the libSQL Rust client and application variables or secrets. ### Source excerpt Setup guide for configuring Turso for deployment using Fermyon Spin and Rust.