It uses deterministic replay over durable state, with a BEAM-based kernel for coordination and durability and disposable TypeScript workers for execution.
The idea is:
the code reruns
the state does not
I’d especially love feedback on the execution model, durability semantics, and where this should go next.
GitHub: https://github.com/vilano-ai/runtime Install: https://runtime.vilano.ai
mcl0vinit•1h ago
The main thing I wanted was a stronger execution model than scripts + retries.
In Vilano Runtime, the kernel owns durable truth and coordination: waits, timers, retries, service inbox state, supervision, and replay state. Workers are disposable and rerun orchestration code from the top, resolving durable operations through the kernel.
That split is what lets workflows and long-lived keyed services recover cleanly across failure and restart.