Obeli

Obelisk 0.41 draws a firm line between what an operator controls and what a deployment can do. That line is what makes it safe to let an agent author, submit, and activate deployments: the operator sets secrets and outbound HTTP policy once in server.toml

Obelisk, Temporal and Restate all let a function keep making progress after its process disappears. The largest architectural difference is that Obelisk is a workflow runtime: it loads and runs application components itself. Temporal and Restate are orche

Obelisk 0.40 tightens two defaults that used to be wide open and improves how workflows see failed children. The API port now rejects requests without a token, host exec activities have to be enabled before they will run, and an awaited child failure now

Obelisk 0.39 makes deployments easier to inspect, reproduce, and move between environments. The server now stores the submitted deployment.toml together with deployment-owned source files, can reconstruct a deployment back to disk, and verifies deployment

DBOS recently argued that Postgres is all you need for durable execution : if you already trust your database, you do not need a separate orchestration tier. I agree with the direction, and I think the idea can be pushed further. For a large class of dura

Obelisk 0.38 adds native executable activities, step-through execution debugging with the replay/advance API, and self-contained deployments where JS and shell scripts live directly inside deployment.toml .

Obelisk 0.37 ships first-class JavaScript support for all three component types - activities, workflows, and webhook endpoints - running inside a fine-grained permission sandbox. It also introduces the Deployment concept with hot redeploy, and built-in cr

Obelisk 0.35 introduces workflow replay for debugging and version migration, execution pausing, persistent log storage, and streamlined component management with GitHub release support.

Obelisk 0.32 introduces cooperative cancellation for workflows and activities, a new WebAPI with multi-format support, and PostgreSQL support for multi-node deployments and high availability.

One of the big strengths of Rust is its use of automatic memory management. When a value gets out of scope, the compiler automatically calls its destructor and frees the memory. During my work on graceful shutdown I have stumbled on a less known interacti