Category · 3 options
Choosing background jobs
Work that runs outside a web request: queues, retries, scheduled tasks, long multi-step workflows and AI calls that outlast a serverless timeout. On serverless hosting, pick a service that calls your existing routes and saves progress between steps, so nothing dies at the function timeout. Check what the free plan counts (runs, steps, messages or compute) and whether retries count too.
Free plans and prices
In Cuely's default order for the general case. Your needs change the order; see below.
| Tool | Free plan | Paid from | At 1,000 users |
|---|---|---|---|
Runs inside the routes your app already has, saving progress between steps so long work survives serverless timeouts. | Free: 50k executions, 5 concurrent steps, 5 seats, 500k events ingested, 24 hour trace history. | Pro: starting at $99/month for 1M executions, 100+ concurrent steps and 15 seats. | $0/month |
Long tasks run on Trigger.dev's machines, not your web host, so there is no function timeout to design around. | Free: $5/month free credits, 20 concurrent runs, 10 schedules, 1 day log retention. | Hobby: $10/month with $10 of credits, 50 concurrent runs, 100 schedules. Compute from $0.0000169/sec (Micro), $0.0000338/sec on the default Small 1x, plus $0.25 per 10,000 runs. | $0/month |
The simplest queue for serverless and edge code: publish over HTTP and QStash calls your route, retrying on failure. | Free: 1,000 messages per day, 1MB max message size, 10 active schedules, 15 minutes max HTTP response duration. | Pay as You Go: $1 per 100K messages, unlimited messages per day, 1,000 schedules included. Fixed 1M: $180/month. | $0/month |
Best pick by need
From the published scores Cuely ranks with. Only needs where one tool clearly leads.
- background jobs or long-running servers: Trigger.dev. Tasks run on managed workers with no function timeout, so hour-long jobs need no workarounds.
- fewer vendors: Upstash QStash. One Upstash account covers both Redis and the queue.
- global low latency: Upstash QStash. Publishing is one HTTP call, so it works from edge functions and Workers.
- keep costs as low as possible: Upstash QStash. $1 per 100,000 messages with no monthly fee.
- Next.js or React: Inngest. Functions live in your Next.js API routes; Inngest calls them, so there are no separate workers to deploy.
- prefers open source or self-hosting: Trigger.dev. Open source and self-hostable.