Hi! I’m the author of Lunatic and a huge Elixir fan .

I started working on Lunatic when I moved to Rust and missed the features from the BEAM world. Especially being able to just spawn a lightweight process that is self isolated. It’s impossible to do this in Rust using just libraries because all the code shares the same memory space.

I came up with the idea to use WebAssembly instances as process replacements. Contrary to Lumen, LAM and other implementations, Lunatic doesn’t run inside one WebAssembly instance, but runs thousands of instances as lightweight processes.

This gives Lunatic also a bit more powerful per process isolation than you get on the BEAM. E.g:

1. You can spawn a process that can only use a limited amount of memory or CPU.
2. You can use C bindings without fear. Once everything is compiled to WebAssembly, long running code will still be preempted and crashes don’t escape the process boundary.
3. You can limit syscalls on a per process level, e.g. spawn this process but don’t let any code running in it open a network connection.
4. Redirect syscallls, e.g. if this process writes to a log file redirect the stream over the network to an Elastic cluster.
5. You can use it from you favourite language if it compiles to WebAssembly. Currently we only provide libraries for Rust and AssemblyScript.

The project is still in its early stage and not all features are implemented yet, but we got initial funding from YC and are working full time on it.

At the moment we don’t provide any APIs for GUIs (or wrappers) and solely focus on backend applications, but it could be an addition in the future.

The runtime works on Windows, MacOs and Linux (x64 & arm64).

This has an updated website now: https://lunatic.solutions/

Similar to Lumen, but instead of Erlang compiling to WebAssembly, this is just inspired by Erlang, and written in Rust.