Facts read November 20, 2026
Inngest vs Upstash QStash
Inngest is Cuely's default background jobs pick when your description doesn't favor either one: runs inside the routes your app already has, saving progress between steps so long work survives serverless timeouts. Pick Upstash QStash if you care most about global low latency.
Side by side
| Fact | ||
|---|---|---|
| What it is | A workflow and queue service that calls functions in your own app, step by step, with retries and scheduling. | An HTTP message queue and scheduler: it delivers messages to your endpoints with retries, delays and cron schedules. |
| Free plan | Free: 50k executions, 5 concurrent steps, 5 seats, 500k events ingested, 24 hour trace history. | Free: 1,000 messages per day, 1MB max message size, 10 active schedules, 15 minutes max HTTP response duration. |
| Paid from | Pro: starting at $99/month for 1M executions, 100+ concurrent steps and 15 seats. | Pay as You Go: $1 per 100K messages, unlimited messages per day, 1,000 schedules included. Fixed 1M: $180/month. |
| At 1,000 users | $0/month | $0/month |
| Open source | No | No |
| Self-hostable | Yes | No |
| Best for | Next.js or serverless apps that need queues and retries; Multi-step workflows (signup flows, AI pipelines); Cron jobs without a server | Fire-and-forget jobs and webhooks; Cron on serverless or edge hosting; Apps already on Upstash Redis |
| Watch out | Executions are counted per run and per step: a run with 5 steps uses 6 executions. The free plan allows 5 concurrent steps; bursts queue up behind that limit. Pro starts at $99/month, a big step up from Free. Traces are kept for 24 hours on Free. | Free stops at 1,000 messages a day, and every retry counts as another message. Your endpoint does the work, so your host's function timeout still applies. Free holds failed messages for 3 days and allows 10 schedules. |
Where they differ
The published scores, from −3 to +3, that decide which one Cuely picks for each need.
| Need | Inngest | Upstash QStash |
|---|---|---|
| background jobs or long-running servers | +2 Each step is retried and saved, so a workflow can run for hours across many short serverless calls. | −1 QStash calls your endpoint, so the work is still bound by your host's timeout. |
| Next.js or React | +2 Functions live in your Next.js API routes; Inngest calls them, so there are no separate workers to deploy. | 0 No particular strength here. |
| global low latency | 0 No particular strength here. | +2 Publishing is one HTTP call, so it works from edge functions and Workers. |
| keep costs as low as possible | +1 50,000 executions a month on the free plan. | +2 $1 per 100,000 messages with no monthly fee. |
| fewer vendors | 0 No particular strength here. | +1 One Upstash account covers both Redis and the queue. |
Sources: Inngest pricing (read November 20, 2026), Upstash QStash pricing (read November 20, 2026). No vendor pays for placement.