Wasmer

What if you could run ANY Node.js app unmodified, safely anywhere… without Docker, containers, or security headaches? 🔥 Introducing Edge.js • Fully compatible with Node.js • Sandboxed by design • Pluggable with any JS engine Node.js, but actually safe. And everywhere 👇

@rbbydotdev @Wasmer It should be fully possible. Would you mind dropping by Wasmer's Discord and asking the question there so someone from the team can follow up with you? discord.gg/rWkMNStrEW

heyyyy @wasmer, recently I had a wordpress deploy with a dep which used php ffi. How difficult would it be to achieve this on wasmer? Would be neat to leverage wasm somehow since it was rust and could compile to wasm ...

@cramforce Thanks! We have this for our Edge platform, but is not publicly released 🤗

@wasmerio This looks cool. Beyond sandboxing, is there a mechanism to intercept and virtualize things like the filesystem, networking, etc.?

What if you could run ANY Node.js app unmodified, safely anywhere… without Docker, containers, or security headaches? 🔥 Introducing Edge.js • Fully compatible with Node.js • Sandboxed by design • Pluggable with any JS engine Node.js, but actually safe. And everywhere 👇

The interesting things to me are: - New JS runtime with 100% Node compat and passing 99% of Node's tests (the most compatible that I know of) - Was essentially vibecoded in a few weeks by gpt-5.4 and a small team with minimal experience with Node internals and C++ From reading the blog post and briefly glancing at the code, the runtime works by running using WASIX (basically WASI but supports all Posix system calls). What's cool is the actual JS engine (V8 right now, but conceptually could support any) is *not* compiled to Wasm but is instead exposed as a native host function so it's still fast and can JIT The sandboxing comes from re-implementing every single Node module and swapping out all IO to use Edge.js's own implementation These are actually NAPI functions exposed to JS, and there's a compilation step that compiles them to Wasm. When they're called it brings execution back into Wasm where system calls can be sandboxed by the Wasmer runtime It looks like they made some changes to Wasmer runtime to directly support that by intercepting napi function registration calls and registering those functions in the runtime: github.com/wasmerio/wasme…

@manol_ai Agreed. Docker is a great piece of software that brought us where we are, and if you want to run apps affordably at scale, you can simply use other kind of sandboxing technologies! (such as Wasmer! 😉)

@wasmerio Docker is not a headache

@NathanFlurry @imrane We love Secure Exec SDK as well 🥰 Lets continue pushing the boundaries forward 💪

@imrane @wasmerio v cool stuff! different approach, since they're using wasm instead of isolates. love wasix.

🤘 Securely execute AI-generated Node.js code without a sandbox - 17.9ms coldstarts p99 - 3.4 MB RAM - 56x cheaper than sandboxes - Built on the same tech as Cloudflare Workers - Just a library, no external vendor - Our most metal website yet

@Berrygradient But better 😎

@wasmerio So like webcontainers ?

@wasmerio Well that’d be big if true

@benhylak We have to work a bit on our video editing skills!

bad video but this is really good

guys cooked like rent is due

Apps are sandboxed using WebAssembly instead of Docker. Perfect for Agentic and serverless workloads. Built using @OpenAI Codex agents. Read more about the announcement here! wasmer.io/posts/edgejs-s…

I had lots of fun doing this podcast 🤗

Syrus Akbary, Founder & CEO of @wasmerio, on why WebAssembly is bigger than browsers. Built to overcome JavaScript’s performance limits, WebAssembly enables near native speed apps to run safely in the browser and beyond. Episode out soon. Stay tuned. #WebAssembly #JavaScript #WPLegends

@WinixRun 🤗

¡Muchas gracias! Os quise etiquetar ayer, pero tampoco quería hacerlo de forma tan directa que podría parecer que os estaba echando la culpa o algo así. Da gusto cuando las empresas colaboran en hacer internet un poquito mejor.

@WinixRun Acabamos de deshabilitar la aplicación web para que nadie más se vea afectado. Gracias por reportarlo

El frontend está alojado en Wasmer, que es un hosting serverless, esto significa que en vez de pagar por un servidor, los malos solo pagan cuando alguien lo usa. En este caso tienen una suscripción gratuita bastante limitad en número de ejecuciones al día.

Una estafa más de correos que va a tener complicado molestar a más gente y..quizás estos acaben rindiendo cuentas legales. Voy a intentar explicarlo un poco "para todos los públicos" no solo para gente con gafas. 🤓👿

🔥 Dynamic linking in WebAssembly with WASIX. An in-depth article about how we made possible Native Python Packages in Wasmer. wasmer.io/posts/dynamic-…

@moonbitlang That's impressive! Congrats!

We recently completed Fastcc — a self-hosting C compiler built from scratch with minimal human involvement. In ~10 days, an AI agent implemented ~35k LOC, reached self-hosting, and compiled real-world C code, including tcc and quickjs. Repo：github.com/moonbit-commun… Full Write-up：moonbitlang.com/blog/fastcc-ai…

Check it out @__CalPy__!

✨ Here are the slides of our presentation today in CalPy, where we chatted about Python, WebAssembly and AI! speakerdeck.com/syrusakbary/we…

We will be speaking tonight in the CalPy meetup about Wasmer and why is the future of containerization. Join us! 🚀