Intro

Planned changes to providers

The wasmCloud Q3 2025 Roadmap sets out plans for an overhaul to capability providers in the next major release of wasmCloud. This overhaul transitions providers to a "wRPC server" model in which WIT interfaces are served via one of the transports available with wRPC (e.g., TCP, NATS, QUIC, or UDP), enabling capability implementations to be written in any language and to be deployed independently in containers.

For more information, see the Roadmap, Issue #4642: “Transition the capability provider model into support for wRPC servers,” and Issue #4636: "Support configuring a wasmCloud host with shared capability providers."

Providers are executable host plug-ins—stateful, standalone processes that fulfill non-functional requirements for stateless components. For a high-level introduction to providers and why you might want to build one, see Providers in the Concepts section.

Here, you can learn how to build your own provider. We'll walk you through implementing your own messaging provider for NATS, and you can use the same process to implement a capability provider using standard interfaces like wasi:http, wasi:keyvalue, wasi:blobstore, and wasmcloud:messaging.

We'll work through the following steps:

• Create: Create a new messaging provider from a template using wash and implement the wasmcloud:messaging interface.
• Build: Compile the provider artifact.
• Test: Test the provider in a local wasmCloud environment.
• Publish: Publish the provider to an OCI registry.