Atomic ownership
One caller owns execution. Other callers wait for or replay the durable outcome.
Go idempotency, built for real retries
A typed, storage-backed idempotency layer for HTTP APIs, workers, webhooks, and distributed workflows.
One caller owns execution. Other callers wait for or replay the durable outcome.
Leases reclaim abandoned work while fencing stops stale workers from writing late results.
Generics, standard-library HTTP middleware, and memory or SQLite stores with no required account.