Resuma OS (execution layer)

Durable workers, disk-backed queues, cron scheduler, webhooks, and an ops dashboard — self-hosted. No Redis or Cloudflare Workers required. Rate limiting for the whole app (actions, submits, exec) also lives on disk under {RESUMA_DATA_DIR}/rate-limit/.

When to use

• Background jobs (enqueue + multi-process consumers)
• Cron-triggered workers
• AI / fetch pipelines with map-reduce
• Ops visibility (graphs, queues, Prometheus metrics)

On-disk layout

.resuma/
├── durable/     graphs, events, checkpoints, tokens
├── queue/       pending → processing → done|failed
├── scheduler/   cron jobs (multi-process safe)
├── rate-limit/  per-IP limits on disk
└── webhooks/    outbound lifecycle hooks

Bootstrap

init_exec() runs automatically when you FlowApp::serve or ResumaApp::into_router. Configure data dir with RESUMA_DATA_DIR.

use resuma::prelude::*;

#[worker(intent = "summarize text with AI")]
async fn summarize(input: SummarizeInput) -> Result<Value> {
    Ok(json!({ "summary": input.text }))
}

FlowApp::new()
    .auto_pages("src/pages", PagesRegistry)
    .serve(FlowServeOptions::default())  // init_exec() inside
    .await

HTTP routes

Guides