Not a ranking: each option is described by the situation it fits, with its trade-off, whether it's open source or free to start, whether AI coding agents can work with it, and how many makers' products use it for this job.
Hosted job platform or a queue you run. Hosted platforms work on serverless hosting and give you retries, schedules and a dashboard, at the cost of a vendor in your critical path; a queue library is free and fully yours, but needs a long-running worker process and Redis or Postgres to hold the jobs. A durable workflow engine sits between: you run the workers, it keeps each workflow's state so long processes resume after failures.
Inngest (Hosted job platform): Event-driven, multi-step workflows where each step retries on its own and your code stays in your existing app. Trade-off: Pricing scales with executions and steps, so chatty workflows cost more.
Best forLong-running, multi-step workflows — payments, onboarding, AI agent loops — whose state must survive crashes and deploys, in Go, Java, Python, TypeScript and more.
Trade-offYou run worker processes, plus the Temporal server or Temporal Cloud billed per action; workflow code must be deterministic.
Used by 29 makers' products for this · Inngest vs Temporal →
Best forLong-running TypeScript tasks — AI calls, media processing — that would time out in a serverless function.
Trade-offYour job code is deployed to and runs on Trigger.dev's infrastructure unless you self-host it.
Used by 23 makers' products for this · Inngest vs Trigger.dev →
Best forSimple scheduled calls and delayed HTTP jobs on serverless or edge hosting, via QStash.
Trade-offA message is an HTTP call to your endpoint, so the endpoint's time limit still applies to the work.
Used by 2 makers' products for this
Best forNode apps on a long-running server that already have Redis — free and fully in your control.
Trade-offYou run the worker processes and Redis yourself, and there is no hosted dashboard by default.
Used by 1 makers' products for this
Best forA dedicated message broker for queues and pub/sub between services, in any language, or as the broker behind Celery.
Trade-offAnother server to run and monitor, and it only moves messages — retries, schedules and job dashboards are up to your worker library.
Used by 2 makers' products for this
Best forNode apps that already run on Postgres and want a job queue with retries and cron without adding Redis.
Trade-offEvery job is database writes, so very high job volumes put load on your main database; Node only.
No maker product tracked for this yet
Best forPython backends — Django, FastAPI, AI pipelines — that need background tasks and schedules on worker processes.
Trade-offYou run the workers, the broker and a separate scheduler process for periodic tasks; configuration has many knobs and failure modes to learn.
No maker product tracked for this yet
