HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wasmerio
wasmer
Rust2018–2026
wasmerio / wasmer

wasmer

🚀 Fast and lightweight sandboxes for your apps and AI agents

34Distinct people
56Mentions
0Explicit recommenders
21.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🚀 Fast and lightweight sandboxes for your apps and AI agents

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year56 dated mentions

Observed mentions: 2018-12-08 03:04:12 UTC to 2026-01-29 03:41:46 UTC.

0369122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC312
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC12210
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC606
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1019
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC10010
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC918
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Lightweight sandboxes for your apps and AI agents Run with the CLI ¡ Embed with the SDK ¡ Try in your browser Wasmer runs your apps in fast, secure, and lightweight sandboxes: locally, in the cloud, or in your browser. Secure by default. You control file, network, and environment access. Lightweight. Fast startup with a small memory footprint. Ready to run. Python, JavaScript, Bash, and more from the registry. Embeddable. Add sandboxes to your app with the Wasmer SDK. Run your first sandbox Install the CLI on macOS or Linux: curl https://get.wasmer.io -sSfL | sh Windows and other installation options Windows (PowerShell) iwr https://win.wasmer.io -useb | iex Homebrew (macOS / Linux) brew install wasmer See the installation guide for more options. Run Python in a sandbox: wasmer run python/python -- -c "print('Hello from Wasmer')" Hello from Wasmer Or try a shell command and Cowsay: wasmer run wasmer/bash -- -c "echo 'Hello from Wasmer'" wasmer run syrusakbary/cowsay -- "Hello from Wasmer" Wasmer downloads the package and caches it for future runs. Use -- to separate Wasmer options from the arguments passed to your program. To work with local files, grant access to a directory with --volume; enable host networking with --net when your program needs it. See the CLI guide for details. No installation needed: open wasmer.sh to try a sandbox in your browser. Wasmer SDK Create a sandbox, choose your tools, and run code directly in your app with the Wasmer SDK. Install the SDK JavaScript / TypeScript (Node.js 20 or newer): npm install @wasmer/sdk Rust The Rust SDK currently uses a source dependency. Clone wasmerio/wasmer-sdk, then point your application at its rust directory: [dependencies] wasmer-sdk = { path = "../wasmer-sdk/rust" } tokio = { version = "1", features = ["macros", "rt-multi-thread"] } Follow the Rust setup guide for the required toolchain and workspace patches. Crates.io publishing is currently disabled. Python python -m pip install wasmer-sdk The SDK's Python wheels support macOS and Linux on Intel and ARM64. See the Python guide. Swift (iOS and macOS) Use Swift 6 or newer. The SDK supports macOS 12+ and iOS 27+; iOS apps require Xcode 27 or newer. Add the package to your Package.swift dependencies: .package( url: "https://github.com/wasmerio/wasmer-sdk.git", revision: "wasmer-sdk-swift-v0.4.0" ) Then add the product to your target's dependencies: .product(name: "WasmerSDK", package: "wasmer-sdk") In Xcode, you can instead add the repository URL, select wasmer-sdk-swift-v0.4.0 as a revision, and choose the WasmerSDK product. SwiftPM downloads the prebuilt macOS binaries and iOS runtime resources. For iOS, set the deployment target to iOS 27.0 and allow local networking in your app's Info.plist: <key>NSAppTransportSecurity</key> <dict> <key>NSAllowsLocalNetworking</key> <true/> </dict> Both platforms use import WasmerSDK and the same API. On iOS, the SDK manages a hidden WKWebView; your app does not need to display one. See the Swift guide and iOS setup guide for more details. Run code in a sandbox JavaScript / TypeScript Save this as sandbox.mjs: import { Wasmer } from "@wasmer/sdk/node"; const wasmer = new Wasmer(); const sandbox = await wasmer.sandboxes.create({ packages: ["python/python@=3.13.20"], }); const output = await sandbox .command("python", ["-c", "print('Hello from Wasmer')"]) .run(); console.log(output.text()); Run it with node sandbox.mjs. Python executes inside the sandbox; you don't need Python installed on the host. See the JavaScript guide. Python example Save this as sandbox.py: import asyncio from wasmer_sdk import Wasmer async def main(): wasmer = Wasmer() sandbox = await wasmer.sandboxes.create( packages=["python/python@=3.13.20"], ) output = await sandbox.command( "python", ["-c", "print('Hello from Wasmer')"] ).run() print(output.text()) asyncio.run(main()) Run it with python sandbox.py. See the Python guide. Swift example (iOS and macOS) Use this code in an async throws context: import WasmerSDK let wasmer = try Wasmer() let sandbox = try await wasmer.sandboxes.create( packages: ["python/python@=3.13.20"] ) let output = try await sandbox.command( "python", ["-c", "print('Hello from Swift!')"] ).run(timeout: 30) print(try output.text()) See the Swift guide for embedding in an iOS or macOS app and more examples. JavaScript in the browser Use the same JavaScript sandbox API with the @wasmer/sdk/browser import. Execution happens in the browser. Your page needs cross-origin isolation (Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp) for worker-backed execution. Follow the browser setup guide or explore wasmer.sh. Rust example use wasmer_sdk::{Result, Wasmer}; #[tokio::main] async fn main() -> Result<()> { let wasmer = Wasmer::new()?; let sandbox = wasmer .sandboxes() .create() .package("python/python@=3.13.20") .await?; let output = sandbox .command("python") .args(["-c", "print('Hello from Wasmer')"]) .run() .await?; println!("{}", output.text()?); Ok(()) } See the Rust guide for workspace setup and more examples. Go further Build more with the sandbox API: Commands. Run code and capture output. Processes. Stream output and manage long-running tasks. Files. Read and write the sandbox workspace. Tools. Combine languages and packages in one sandbox. Services. Run servers with explicit network access. The SDK is currently alpha. See the language guides for platform support and capabilities, and the SDK examples for Python scripts, an Edge.js HTTP server, PostgreSQL, and multiple tools sharing one sandbox. Software you can run Start with packages from the registry: Software Package Python python/python JavaScript / Node.js-compatible app
Read the full README on GitHub

What Hacker News says

12 sources
wasmer [1] has a LLVM backend, WAVM [2] uses LLVM as the bakend, I could be wrong but last time I checked, cranelift is only meant to be the next generation WASM engine used in Firefox, it is not yet in production. And actually the argument is: all of v8, Firefox/Cranelift and LLVM used in wasmer requires non-trivial work to make WASM fast, which shouldn't be needed given a different model. [1] https://github.com/wasmerio/wasmer/tree/master/lib/llvm-back... [2] https://github.com/WAVM/WAVM
In WASM as a Platform for Abstraction
First of all, congrats on forming the alliance! > Imagine extensions for applications or databases, written in any language you want, with no ability to exfiltrate data That's what we are working towards on Wasmer, the server side WebAssembly runtime - https://github.com/wasmerio/wasmer In fact, we already have a lot of different language integrations (maintained by us and the community) and our software is the pioneer on the space. Is there any reason on why you think is a good idea to do a side-alliance instead of collaborating with us and the community so users and developers can be the ultimate beneficiaries? (it's good, it just seems is not an alliance made for the users, which it's a bit weird from my perspective)
In The Bytecode Alliance: Building a secure, composable future for WebAssembly
We don't support that yet, but we are working on it. It's not that easy even if the theory is kind of simple to explain. The implementation in the different backends is mostly the challenge. The Python extension uses the Wasmer runtime (https://github.com/wasmerio/wasmer) which supports 3 backends to generate executable code: Singlepass, Cranelift, and LLVM. Cranelift is the easiest one to embed, and it brings a great balance between compilation time and execution time. That's the one used in the Python extension right now. The “import functions” feature is also missing in the PHP extension (https://github.com/wasmerio/php-ext-wasm), but yeah, as I said, we are working on it. It's coming soon!
In Wasmer: A Python library for executing WebAssembly binaries
Thanks for asking! I'm Syrus, I started the Wasmer project. Lucet just released, but so far these are the current differences as far as I can tell: 1. Wasmer is meant to execute any WebAssembly file and run on any platform. Wasmer currently runs on Mac, Linux and Windows. Lucet only works on Linux at the moment, since its main goal is to be executed on Fastly's infra. 2. We support multiple compiler backends: dynasm, cranelift and LLVM. Each with a tradeoff between runtime speed and compilation speed (more info here https://github.com/wasmerio/wasmer/tree/master/lib#backends ). Lucet's architecture only supports one backend at the moment. 3. Wasmer has multiple interfaces/ABI integrations, including Emscripten, and soon WASI. Lucet initially shipped with WASI support, which is awesome. 4. Wasmer has a C/C++ API and its runtime can be inte
Read the rest
grated with other languages (C/C++, Rust and PHP at the moment) And, of course... a link to the project if anyone else wants to take a look! https://github.com/wasmerio/wasmer
In Lucet: Native WebAssembly Compiler and Runtime

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.