Test

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."

To test a provider, we can run it in a local wasmCloud environment, interacting with a real host and real components. To set up the environment:

1. Run a local development environment with wash up
2. Build the provider with wash build
3. Using a wadm.yaml application manifest that includes the path to your provider, wash app deploy wadm.yaml to deploy your application
   1. Alternatively, start the provider with wash start provider ./path/to/provider.par.gz
   2. Start a component that interacts with the provider with wash start component, then link the two together
4. Invoke the component or provider directly to test

To see an example of this, refer to the create section for capability providers.