Say it sta-FETT. A relay runner carries the baton for one leg, hands it off cleanly, and confirms the exchange. That is the whole product: Stafett accepts a job from your app, carries it to your HTTPS endpoint, confirms the handoff, and reruns the leg if the baton drops.
Every codebase eventually grows the same machinery: a retry loop, a backoff table, a signature scheme, and a page that answers "what happened to job 42". It gets rebuilt per project and tested by outages. Stafett hosts that machinery behind one HTTP API, so any language can enqueue work without operating a queue or deploying a delivery worker.
The delivery engine is pgqueuer, an open-source job-queue library by the same maintainer. Stafett wraps it in plain HTTP and a delivery contract: at-least-once, signed, retried, and never silently dropped.
Boring on purpose. One focused delivery service, limits stated up front, and a public "when not to use" list. Stafett is pre-alpha and developed in the open; the delivery contract is the part we treat as stable.