The Wasm Micro Runtime (WAMR) project will begin transitioning to a new home on Monday, July 27, 2026, with the process expected to be completed by Friday, July 31, 2026.
This marks the beginning of an exciting new chapter for WAMR. Following discussions between the WAMR maintainers and the Bytecode Alliance, it was jointly agreed that WAMR would continue its development as an independent open source project. While this changes the project's organizational home, it does not change WAMR's mission, maintainers, or commitment to the community. The same people and teams who have built and supported WAMR will continue to lead the project, and we're excited about the opportunities ahead as we continue to grow WAMR together with our community.
During the week in transition (Monday 27 July - Friday July 31) we will be moving the GitHub repositories we use to new locations. We hope to keep the disruption to a minimum during this week, and as our GitHub repositories are moving, we will be posting updates on our progress via our mailing list - please feel free to join this to stay informed. Please visit this URL https://groups.google.com/g/wamr-dev, and click “join group”.
Once this transition process completes there will be no impact for users of WAMR. The project will continue to be run and continue to be supported by the same people and teams that support WAMR today. The only visible change will be the new GitHub repository locations we will use. GitHub should redirect you automatically, but just in case the table below lists the old and new locations of the repositories we use.
The WAMR project joined the Bytecode Alliance on May 3rd 2019 - about 7 years ago. The Bytecode Alliance is home to some amazing projects and people and we’d like to thank them for all the help and support, and to wish our friends at the Bytecode Alliance all the best for the future.
Speaking of the future, the WAMR team has some exciting plans for the project. Once this transition is complete we hope to share these plans with the wider community via our mailing list and new GitHub repositories. Please do join the mailing list as we’d love to hear your feedback https://groups.google.com/g/wamr-dev.
| Description | Current Location | New Location |
|---|---|---|
| Wasm Micro Runtime | https://github.com/bytecodealliance/wasm-micro-runtime | https://github.com/wasm-micro-runtime/wasm-micro-runtime |
| wamr-rust-dsk | https://github.com/bytecodealliance/wamr-rust-sdk | https://github.com/wasm-micro-runtime/wamr-rust-sdk |
| wamr-app-framework | https://github.com/bytecodealliance/wamr-app-framework | https://github.com/wasm-micro-runtime/wamr-app-framework |
| wamr-python | https://github.com/bytecodealliance/wamr-python | https://github.com/wasm-micro-runtime/wamr-python |
A Bytecode Alliance project
Build WAMR | Build AOT Compiler | Embed WAMR | Export Native API | Build Wasm Apps | Samples
WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime with small footprint, high performance and highly configurable features for applications cross from embedded, IoT, edge to Trusted Execution Environment (TEE), smart contract, cloud native and so on. It includes a few parts as below:
- VMcore: A set of runtime libraries for loading and running Wasm modules. It supports rich running modes including interpreter, Ahead-of-Time compilation(AoT) and Just-in-Time compilation (JIT). WAMR supports two JIT tiers - Fast JIT, LLVM JIT, and dynamic tier-up from Fast JIT to LLVM JIT.
- iwasm: The executable binary built with WAMR VMcore which supports WASI and command line interface.
- wamrc: The AOT compiler to compile Wasm file into AOT file
- Useful components and tools for building real solutions with WAMR vmcore:
- App-framework: A framework for supporting APIs for the Wasm applications
- App-manager: A framework for dynamical loading the Wasm module remotely
- WAMR-IDE: An experimental VSCode extension for developping WebAssembly applications with C/C++
- Full compliant to the W3C Wasm MVP
- Small runtime binary size (core vmlib on cortex-m4f with tail-call/bulk memory/shared memory support, text size from bloaty)
- ~58.9K for fast interpreter
- ~56.3K for classic interpreter
- ~29.4K for aot runtime
- ~21.4K for libc-wasi library
- ~3.7K for libc-builtin library
- Near to native speed by AOT and JIT
- Self-implemented AOT module loader to enable AOT working on Linux, Windows, MacOS, Android, SGX and MCU systems
- Choices of Wasm application libc support: the built-in libc subset for the embedded environment or WASI for the standard libc
- The simple C APIs to embed WAMR into host environment, see how to integrate WAMR and the API list
- The mechanism to export native APIs to Wasm applications, see how to register native APIs
- Multiple modules as dependencies, ref to document and sample
- Multi-thread, pthread APIs and thread management, ref to document and sample
- wasi-threads, ref to document and sample
- Linux SGX (Intel Software Guard Extension) support, ref to document
- Source debugging support, ref to document
- XIP (Execution In Place) support, ref to document
- Berkeley/Posix Socket support, ref to document and sample
- Multi-tier JIT and Running mode control
- Language bindings: Go, Python, Rust
- wasm-c-api, ref to document and sample
- 128-bit SIMD, ref to samples/workload
- Reference Types, ref to document and sample
- Bulk memory operations, Shared memory, Memory64
- Tail-call, Garbage Collection, Exception Handling, Branch Hinting
- Extended Constant Expressions
The WAMR VMcore supports the following architectures:
- X86-64, X86-32
- ARM, THUMB (ARMV7 Cortex-M7 and Cortex-A15 are tested)
- AArch64 (Cortex-A57 and Cortex-A53 are tested)
- RISCV64, RISCV32 (RISC-V LP64 and RISC-V LP64D are tested)
- XTENSA, MIPS, ARC
The following platforms are supported, click each link below for how to build iwasm on that platform. Refer to WAMR porting guide for how to port WAMR to a new platform.
- Linux, Linux SGX (Intel Software Guard Extension), MacOS, Android, Windows, Windows (MinGW, MSVC)
- Zephyr, AliOS-Things, VxWorks, NuttX, RT-Thread, ESP-IDF(FreeRTOS)
- Build VM core and Build wamrc AOT compiler
- Build iwasm (mini product): Linux, SGX, MacOS and Windows
- Embed into C/C++, Embed into Python, Embed into Go, Embed in Rust
- Register native APIs for Wasm applications
- Build wamrc AOT compiler
- Build Wasm applications
- Port WAMR to a new platform
- VS Code development container
- Samples and Benchmarks
- End-user APIs documentation
- Blog: The WAMR memory model
- Blog: Understand WAMR heaps and stacks
- Blog: Introduction to WAMR running modes
- Memory usage tuning: the memory model and how to tune the memory usage
- Memory usage profiling: how to profile the memory usage
- Performance tuning: how to tune the performance
- Benchmarks: checkout these links for how to run the benchmarks: PolyBench, CoreMark, Sightglass, JetStream2
- Performance and footprint data: the performance and footprint data
The WAMR PTSC Charter governs the operations of the project TSC. The current TSC members:
- dongsheng28849455 - Dongsheng Yan, dongsheng.yan@sony.com
- loganek - Marcin Kolny, mkolny@amazon.co.uk
- lum1n0us - Liang He， liang.he@intel.com
- no1wudi Qi Huang, huangqi3@xiaomi.com
- qinxk-inter - Xiaokang Qin， xiaokang.qxk@antgroup.com
- ttrenner - Trenner, Thomas， trenner.thomas@siemens.com
- wei-tang - Wei Tang， tangwei.tang@antgroup.com
- wenyongh - Wenyong Huang， wenyong.huang@intel.com
- woodsmc - Woods, Chris， chris.woods@siemens.com
- xujuntwt95329 - Jun Xu， Jun1.Xu@intel.com
- xwang98 - Xin Wang， xin.wang@intel.com (chair)
- yamt - Takashi Yamamoto, yamamoto@midokura.com
WAMR uses the same license as LLVM: the Apache 2.0 license with the LLVM
exception. See the LICENSE file for details. This license allows you to freely
use, modify, distribute and sell your own products based on WAMR.
Any contributions you make will be under the same license.