Put WebAssembly to work
Choose a practical path through Wasmd based on what you are building.
Embed a controlled guest runtime
Add Wasm execution to a Rust service. Resolve host imports explicitly and keep per-invocation state in a Store.
Build an embedding →SERVICE DEVELOPERSRun a WASI HTTP service
Host standard incoming handlers with explicit port mapping, persistent volumes, and outbound authority grants.
Run an HTTP component →PACKAGE AUTHORSPublish a version people can reproduce
Ship immutable semantic versions, publish a package Overview, and reuse digest-verified artifacts across pull and run.
Publish a package →TOOLING AND CIValidate before execution
Inspect required features and import/export metadata. Use JSON diagnostics and pinned conformance suites in automated workflows.
Explore the commands →PLATFORM DEVELOPERSBudget repeated execution
Prepare imports once and use bounded instance admission. Reuse cleared buffers while retaining fresh Store identities and request limits.
Explore instance lifecycles →RUNTIME EVALUATIONEvaluate the exact support scope
Compare locked baselines, backend coverage, WASI interface inventories, and local platform evidence before adoption.
Review the evidence →