Installer wasmedge avec Homebrew, apt, dnf, MacPorts, Nix, zypper, scoop, winget

Liens du projet

• Page d'accueil
• Dépôt

Commandes et alias

• wasmedge
• wasmedgec

Historique du projet

WasmEdge was originally known as SSVM and was created by Second State. In April 2021 it was accepted into the Cloud Native Computing Foundation at Sandbox maturity, and CNCF project metadata records April 28, 2021 as the acceptance date.

Second State announced the CNCF transition in June 2021 and described WasmEdge as the first official CNCF WebAssembly runtime project. That announcement framed the runtime as an edge-cloud and embedded alternative to heavier Linux containers and virtual machines, with extensions for TensorFlow inference, storage, command execution, and Ethereum-flavored WebAssembly.

The project later leaned further into cloud-native deployment. Official WasmEdge documentation describes using Kubernetes, Docker, CRI-O, containerd, and crun-style runtimes to deploy and manage lightweight WebAssembly applications with familiar container tooling.

Historique d'adoption

WasmEdge's adoption history is closely tied to CNCF and container ecosystem experiments around WebAssembly workloads. The WasmEdge homepage highlights serverless apps, embedded functions, microservices, smart contracts, and IoT devices, while the CNCF project page describes it as a runtime for cloud native, edge, and decentralized applications.

A major visibility moment came in October 2022, when Docker announced a Docker+Wasm technical preview in partnership with WasmEdge at Cloud Native Wasm Day during KubeCon North America. That put WasmEdge in front of developers who already understood images, compose files, and container runtimes but wanted a smaller sandboxed execution target.

Recent project messaging also emphasizes LlamaEdge and GenAI scenarios built on top of WasmEdge. That is a natural extension of its earlier edge-computing niche: run a small, sandboxed, accelerated workload near the user or device, but package and orchestrate it with cloud-native habits.

Modes d'utilisation

Developers use the wasmedge CLI to run WebAssembly modules and wasmedgec to compile modules ahead of time. In cloud-native workflows, WasmEdge is often selected as the runtime behind an OCI or Kubernetes path rather than invoked directly by end users.

Its practical differentiator is extension work: WASI-style system access, TensorFlow or WASI-NN style inference, host embedding APIs, and container integration. That makes it appealing when a team wants WebAssembly isolation but also needs real application hooks such as networking, AI inference, or orchestration.

Pourquoi les passionnés de paquets s'y intéressent

WasmEdge matters to package maintainers because it bridges two packaging cultures: language-level WebAssembly components and OCI/container distribution. Its documentation repeatedly presents Wasm workloads as deployable with existing Docker and Kubernetes tools, which is exactly where packaging metadata, runtime handlers, image annotations, and host capabilities start to matter.

It is also one of the WebAssembly runtimes with a formal CNCF home, making it a frequent comparison point alongside Wasmtime, Wasmer, WAMR, wazero, and Spin/runwasi when people evaluate server-side Wasm stacks.

Chronologie

• 2021-04-28: WasmEdge Runtime was accepted into CNCF at Sandbox maturity.
• 2021-06: Second State announced that WasmEdge, formerly SSVM, had become a CNCF project.
• 2021-09: Second State joined CNCF as a Silver member and reiterated WasmEdge's cloud-native and edge runtime goals.
• 2022-10: Docker announced Docker+Wasm technical preview support in partnership with WasmEdge.
• 2020s: WasmEdge documentation expanded around Kubernetes, Docker, CRI-O, containerd, and AI/LLM-oriented Wasm workloads.

Related projects

• Wasmtime is the Bytecode Alliance runtime most often compared with WasmEdge for WASI and component-model work.
• WAMR is another lightweight runtime, especially relevant to embedded and IoT deployments.
• runwasi, crun, containerd, Docker, Kubernetes, and CRI-O are adjacent cloud-native projects in WasmEdge deployment stories.
• LlamaEdge is an application framework built on top of WasmEdge for GenAI workloads.

Sources

• https://github.com/WasmEdge/WasmEdge
• https://wasmedge.org/
• https://wasmedge.org/docs/develop/deploy/intro/
• https://wasmedge.org/docs/start/wasmedge/features/
• https://www.cncf.io/projects/wasmedge-runtime/
• https://www.prnewswire.com/news-releases/second-state-joins-cncf-as-a-silver-member-301386885.html
• https://www.secondstate.io/articles/wasmedge-joins-cncf/