Everruns Runtime
The Rust and PostgreSQL durable execution engine that powers the platform — and that you can embed directly in your own application.
Crate: crates.io/crates/everruns-runtime · GitHub: github.com/everruns/everruns · License: MIT
What it is
The Everruns Runtime is the durable execution engine at the core of Everruns. It owns the agent loop and persists every step, so long-running work survives restarts, network failures, and worker loss instead of losing progress.
Most of what we publish about Everruns is the server side — a control plane, workers, and an operator console. But the same engine ships as a library, so the durability story does not require standing up a cluster.
Embedding the runtime
The everruns-runtime crate exposes an InProcessRuntimeBuilder for running agents inside a single process:
- In-memory sessions and local filesystem storage, with no external services to operate
- The full durable agent loop, embedded directly in your binary
- An
everruns-clitool for scripting deployments
This is what lets a terminal coding agent like Yolop ship as one binary while reusing the same execution semantics as the hosted platform.
When to use the runtime
- Embed the runtime when you want durable agents inside a desktop app, CLI, or single service without running separate infrastructure.
- Run the platform when you need multi-tenant deployment, a control-plane / worker split, an operator console, and delivery channels like Slack or HTTP.
Both share the same core, so you can start embedded and graduate to the platform without changing how your agents are defined.
Getting started
Add the crate to a Rust project:
cargo add everruns-runtime
Related
- Embedding the Everruns Runtime — a local coding agent in one binary, the worked example
- Everruns Platform — the server-side deployment of the same engine
- Yolop — a coding agent built on the runtime