SaaSHub helps you find the best software and product alternatives Learn more →
Wasmtime Alternatives
Similar projects and alternatives to wasmtime
-
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
-
-
-
-
-
Oberon
Oberon parser, code model & browser, compiler and IDE with debugger, and an implementation of the Oberon+ programming language
-
InfluxDB
InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
-
-
SSVM
WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for cloud native, edge, and decentralized applications. It powers serverless apps, embedded functions, microservices, smart contracts, and IoT devices.
-
extism
The framework for building with WebAssembly (wasm). Easily load wasm modules, move data, call functions, and build extensible apps.
-
-
-
-
-
spin
Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
-
-
-
xz
Discontinued XZ Utils [GET https://api.github.com/repos/tukaani-project/xz: 403 - Repository access blocked]
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better wasmtime alternative or higher similarity.
wasmtime discussion
wasmtime reviews and mentions
Posts with mentions or reviews of wasmtime.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-03-17.
-
Go + WASM: Run Native Code in Your Browser
And if you're doing backend stuff, some platforms (like Wasmer or Wasmtime) let you run WASM on the server.
-
Looking Ahead to WASIp3
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh rustup target install wasm32-wasip1 cargo install --locked --version 1.227.1 wasm-tools cargo install --locked --git https://github.com/dicej/spin --branch wasi-http-p3-demo spin-cli git clone https://github.com/WebAssembly/wasi-http -n && (cd wasi-http && git checkout 505ebdb9) curl -OL https://github.com/bytecodealliance/wasmtime/releases/download/v30.0.2/wasi_snapshot_preview1.reactor.wasm
-
WebAssembly on Kubernetes
Wasmtime, developed by the Bytecode Alliance
- Yoke Is Cool
-
TinyCompiler: A Compiler in a Week-End
9x larger in LoC, 50x larger in comments.
I had a wall of supporting tokei but decided against it, but the short of it is, LLVM is phenomenally massive, and libfirm at 135kloc and 35kloc of comments is but a raindrop that is in the 15Mloc+ that is LLVM.
Perhaps instead of looking towards libfirm, we should look at cranelift. It is of comparable size and actually includes 12kloc of documentation, not just comments.
https://github.com/bytecodealliance/wasmtime/tree/main/crane...
-
Wild – A Fast Linker for Linux
Very similar, but Wasm has additional safety properties and affordances. I am trying to get away from dynamic libs as an app extension mechanism. It is especially nice when application extension is open to end users, they won't be able to crash your application shell.
https://wasmtime.dev/ https://github.com/bytecodealliance/wasmtime
-
Tilde, My LLVM Alternative
>So one of the main problems you run into is that your elegant solution only works about 60-80% of the time. The rest of the time, you end up falling back onto near-unmaintainable, horribly inelegant kludges that end up having to exist
This is generally true, though for small compiler backends they have the luxury to straight up refuse to support such use cases. Take QBE and Cranelift for example, the former lacks x87 support [1], the latter doesn't support varargs[2]; which means either of them support the full x86-64 ABI for C99.
[1]https://github.com/michaelforney/cproc?tab=readme-ov-file#wh...
[2]https://github.com/bytecodealliance/wasmtime/issues/1030
-
Introducing our Next-Generation JavaScript SDK
Standards help in a completely different way, too: since all of the HTTP support is now built using wasi-http, applications built with the new SDK that don’t make use of the Spin-specific APIs we also support can run in any environment that supports wasi-http, such as Wasmtime and Node.js (via JCO).
-
Building And Running WASM Apps
If you’re on Windows, check out the precompiled packages: https://github.com/bytecodealliance/wasmtime/releases
-
Query Your Python Lists
You should look at embedding Wasmtime into your C.
https://github.com/bytecodealliance/wasmtime/tree/main/examp...
-
A note from our sponsor - SaaSHub
www.saashub.com | 28 Apr 2025
Stats
Basic wasmtime repo stats
187
16,218
9.9
3 days ago
bytecodealliance/wasmtime is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of wasmtime is Rust.
Sponsored
CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai
Review ★★☆☆☆ 3/10
By the time I learned how to use the project I also learned that it wasn't any good for the job. API changes frequently, high overhead, little room for extensions.