wasmCloud is a universal application platform that helps you build and run globally distributed WebAssembly applications on any cloud or edge. Our goal is to make development more joyful and efficient by giving developers the tools to write only the code that matters—and making it easy to run that code anywhere.
wasmCloud leverages WebAssembly's security, portability, and performance to compose applications from tiny, independent building blocks.These building blocks are managed declaratively and reconfigurable at runtime. You shouldn't need to recompile your whole app to upgrade a database client or patch a vulnerability and you shouldn't need to recompile anything to move your app from development to production.
wasmCloud is designed around the following core tenets:
- Distributed from day one
- Run anywhere and everywhere
- Secure by default
- Faster iteration and lower maintenance
Move from concept to production without changing your design, architecture, or your programming environment.
Install the wasmCloud Shell (wash) using the installation guide.
If you're new to the wasmCloud ecosystem, a great place to start is the getting started walkthrough.
The following commands launch wasmCloud in a local development environment and deploy a simple "hello world" WebAssembly component, written in Rust, Go, TypeScript, or Python.
wash up -d
wash new component helloworld
wash build -p ./helloworld
wash app deploy ./helloworld/wadm.yaml
curl localhost:8080- Declarative WebAssembly Orchestration
- Seamless Distributed Networking
- Vendorless Application Components
- Completely OTEL Observable
- Defense-In-Depth Security By Default
wasmCloud is based on and implements WASI 0.2 (aka the Component Model). WebAssembly Components that run on wasmCloud consume interfaces defined in WIT.
Want to get something running quickly? Check out the examples directory of this repository. Examples are organized by programming language so you can easily find samples in your language of choice.
For even more examples, check out awesome projects using wasmCloud from our community members!
We have plenty of ideas and things going on in the wasmCloud project. Please check out the Roadmap doc for more information, and the wasmCloud Roadmap project to see the status of new features.
The latest release and changelog can be found on the releases page.
Want to get involved? For more information on how to contribute and our contributor guidelines, check out the contributing readme.
We host weekly community meetings at 1pm EST on Wednesdays. These community meetings are livestreamed to our Twitter account and to YouTube. You can find the agenda and notes for each meeting in the community secton of our webste. If you're interested in joining in on the call to demo or take part in the discussion, we have a Zoom link on our community calendar.
We host our own community slack for all community members to join and talk about WebAssembly, wasmCloud, or just general cloud native technology. For those of you who are already on the CNCF Slack, we also have our own channel at #wasmcloud.
wasmCloud uses some terminology you might not be familiar with. Check out the concepts section of our docs for a deeper dive.
wasmCloud uses an RPC API to enable seamless communication among the host runtime, components, and providers.
The wasmCloud Application Deployment Manager wadm uses the Open Application Model to define and deploy application specifications.
wasmCloud's standard runtime is built in Rust for its zero-cost abstractions, safety, security, and WebAssembly support.
For running a wasmCloud host in a browser or embedding in a JavaScript V8 host, use the JavaScript Runtime
wasmCloud provides an SDK for building capability providers in Rust.
provider-archive is a crate used to create Provider Archive (PAR) files. PARs are used to store, retrieve, and sign capability providers. Today, capability providers are distributed as binary files and run as system processes. In the future, wasmCloud aims to build capability providers as WebAssembly Components, which will remove the need for Provider Archives.
wasmcloud_actor is a wasmCloud actor library written in Rust which facilitates building of wasmCloud components.
The API of the crate matches closely what wit-bindgen would generate, meaning that one can switch from using plain wit-bindgen-generated bindings to wasmcloud_actor (and back) with minimal or no code changes.
wascap is a low-level library used to insert and retrieve claims on components and providers. Claims are part of wasmCloud's zero-trust security model.
We are a Cloud Native Computing Foundation sandbox project.