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 👇
@FrancescoCiull4 Indeed, we were super happy with the result!
And also very thankful for being able to stand on the shoulders of a great software like Django for so many years!
🔥 Hot out of the oven: we ported Wasmer's 7-year-old Django backend to Rust.
The result:
• 220 CPUs → 24
• 800 GB RAM → 64 GB
• p95 API latency: 120ms → 30ms
• Query timings: 5��10x faster
• Startup: >60s → ~1s
Django served us well. Rust is powering what comes next! 💪
Porting our Django backend to Rust improved the infra usage by 90%
>> Wasmer rewrote their 7-year Django backend in Rust, slashing infra by ~90% (220→24 CPUs, 800→64 GB RAM) with 5-10x faster queries in 3 months.
#rustlang#rust
cc: @wasmerio
From "impossible" to shipped in 2 weeks 🚀
With Codex, we built Edge.js: full Node.js workloads running inside a WebAssembly sandbox at the edge (no Docker required!)
The future of cloud is fast, secure, and WebAssembly-native.
https://t.co/Xe3yJJy9pY
@mountainbhoy@dmitryiv_ We are working on a big refactor to make our backend more reliable, and the PHP server as well.
Apologies for not meeting the bar on the support side.
What do you need help with?
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 👇
Edge.js was created with a secret weapon: @OpenAI Codex.
🤯We just compressed years of development work into a few weeks. Mind-blowing what we were able to achieve.
The golden age of software is officially here! 🚀
@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?
https://t.co/ztS1M4HO9Y
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: https://t.co/rMBY25AGHH
@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! 😉)