Skip to content
inetGeek

Upstash QStash vs Inngest

A comparison of Upstash QStash and Inngest built from values read directly from each provider's own documentation, with the source recorded against every figure.

Updated 9 criteria compared

The short answer

Pick Upstash QStash if
HTTP-first workloads that want scheduling and delay measured in months rather than a day, without running a consumer process.
Pick Inngest if
Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.

3 sourced criteria separate them:

Pricing model
Upstash QStash: Per message rather than per operation, metered against a daily ceiling on the free plan and priced at $1 per 100,000 on Pay as You Go, with monthly bandwidth caps alongside — 50 GB on the smaller plans, 1 TB and 5 TB above.
Inngest: Per execution, where a step counts the same as a run, plus separate meters for events ingested, span data, scores and realtime connections. The pricing page ships a calculator because the execution count is not the run count.
Included per month
Upstash QStash: 1,000 messages a day on the free plan. Pay as You Go is $1 per 100,000 messages with no daily cap; fixed plans run $180 a month for 1M a day and $420 for 10M.
Inngest: 50,000 executions a month on the free Hobby plan and 1,000,000 on Pro, pay-as-you-go to 20M. An execution is one function run or one step, so a run with two steps counts as three.
Message retention
Upstash QStash: Dead letter queue retention of 3 days on the free plan, 7 days on Pay as You Go, 30 days and 3 months on the fixed plans.
Inngest: Queue depth rather than a time window: 100,000 queued items on the free plan and 1,000,000 or more on Pro. Trace retention is 7 days on Pro and 90 on Enterprise.

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

01.

At a glance.

CriterionUpstash QStashInngest
Pricing
Free tierYesYes
Pricing modelPer message rather than per operation, metered against a daily ceiling on the free plan and priced at $1 per 100,000 on Pay as You Go, with monthly bandwidth caps alongside — 50 GB on the smaller plans, 1 TB and 5 TB above.Per execution, where a step counts the same as a run, plus separate meters for events ingested, span data, scores and realtime connections. The pricing page ships a calculator because the execution count is not the run count.
Queues
Included per month1,000 messages a day on the free plan. Pay as You Go is $1 per 100,000 messages with no daily cap; fixed plans run $180 a month for 1M a day and $420 for 10M.50,000 executions a month on the free Hobby plan and 1,000,000 on Pro, pay-as-you-go to 20M. An execution is one function run or one step, so a run with two steps counts as three.
Message retentionDead letter queue retention of 3 days on the free plan, 7 days on Pay as You Go, 30 days and 3 months on the fixed plans.Queue depth rather than a time window: 100,000 queued items on the free plan and 1,000,000 or more on Pro. Trace retention is 7 days on Pro and 90 on Enterprise.

Only criteria both providers publish appear here; a tinted cell marks a real difference. Criteria only one of them documents are listed below, and an absence there means we found no source — not that the feature is missing. How we source this.

The small bar above a value is inetGeek's own lean toward that side — computed from the same facts shown, never a number the provider published. See the picker below "The short answer" to weigh only the criteria you care about.

02.

Where they differ.

Pricing model

Upstash QStash
Per message rather than per operation, metered against a daily ceiling on the free plan and priced at $1 per 100,000 on Pay as You Go, with monthly bandwidth caps alongside — 50 GB on the smaller plans, 1 TB and 5 TB above.
Inngest
Per execution, where a step counts the same as a run, plus separate meters for events ingested, span data, scores and realtime connections. The pricing page ships a calculator because the execution count is not the run count.
Sources (2) →
  • QStash Pricing — Upstash ↗

    “$1 per 100K messages [...] Max Messages per Day 1,000 Unlimited 1 M 10 M 100M+ [...] Max Monthly Bandwidth 50 GB 50 GB 1 TB 5 TB Unlimited”

    Read 2026-09-06 · official pricing

  • Pricing — Inngest ↗

    “TOTAL EXECUTIONS PER MONTH (30,000 runs × 2 steps per run) + 30,000 runs = 90,000 executions [...] 500 MB span data ingested [...] 10K scores [...] 500k events ingested [...] 50 realtime connections”

    Read 2026-09-06 · official pricing

Included per month

Upstash QStash
1,000 messages a day on the free plan. Pay as You Go is $1 per 100,000 messages with no daily cap; fixed plans run $180 a month for 1M a day and $420 for 10M.
Inngest
50,000 executions a month on the free Hobby plan and 1,000,000 on Pro, pay-as-you-go to 20M. An execution is one function run or one step, so a run with two steps counts as three.
Sources (2) →
  • QStash Pricing — Upstash ↗

    “Free $0 [...] Messages per Day 1,000 [...] Pay as You Go $1 per 100K messages [...] Messages per Day Unlimited [...] $180 / month [...] 1M [...] $420 [...] 10M”

    Read 2026-09-06 · official pricing

  • Pricing — Inngest ↗

    “50k executions [...] 1M executions included Pay as you go up to 20M [...] (30,000 runs × 2 steps per run) + 30,000 runs = 90,000 executions [...] A single durable function run or step execution”

    Read 2026-09-06 · official pricing

Message retention

Upstash QStash
Dead letter queue retention of 3 days on the free plan, 7 days on Pay as You Go, 30 days and 3 months on the fixed plans.
Inngest
Queue depth rather than a time window: 100,000 queued items on the free plan and 1,000,000 or more on Pro. Trace retention is 7 days on Pro and 90 on Enterprise.
Sources (2) →
  • QStash Pricing — Upstash ↗

    “Max DLQ Retention 3 days 7 days 30 days 3 months Custom”

    Read 2026-09-06 · official pricing

  • Pricing — Inngest ↗

    “100k queue depth [...] 1M+ queue depth [...] Granular tracing, metrics, alerts + 7 day trace retention [...] Advanced tracing, metrics, alerts + 90 day trace retention”

    Read 2026-09-06 · official pricing

03.

Which should you choose?

Choose Upstash QStash if…

HTTP-first workloads that want scheduling and delay measured in months rather than a day, without running a consumer process.

Editorial · Palash Bagchi · approved

Choose Inngest if…

Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.

Editorial · Palash Bagchi · approved

Consider something else if…

  • Upstash QStash: The free plan is capped per day rather than per month, so a single burst can exhaust it while a monthly allowance elsewhere would absorb the same volume.
  • Inngest: Every step is a billable execution, so a three-step workflow costs three times what the run count implies, and the free plan allows five concurrent steps.
04.

Documented by only one.

These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing.

Entry paid planInngest: $99/month for Pro, described as a starting price with usage above the included allowance billed on top.
Maximum message sizeUpstash QStash: 1 MB on the free plan, 10 MB on Pay as You Go and 50 MB on the fixed plans.
Maximum delayUpstash QStash: 7 days on the free plan; 1 year on Pay as You Go and unlimited on the fixed plans.
ConcurrencyInngest: 5 concurrent steps on the free plan, 100 or more on Pro, custom on Enterprise.
Dead letter queueUpstash QStash: Supported
05.

Questions this comparison answers.

Should I choose Upstash QStash or Inngest?

Pick Upstash QStash if HTTP-first workloads that want scheduling and delay measured in months rather than a day, without running a consumer process.

Pick Inngest if Multi-step workflows that need durable execution and retries between steps, rather than a bare queue you write a consumer for.

Provider pages

Related comparisons

sentry vs glitchtipsentry vs betterstackglitchtip vs betterstackcloudflare r2 vs backblaze b2cloudflare r2 vs wasabicloudflare r2 vs tigrisbackblaze b2 vs wasabiwasabi vs tigrisneon vs supabaseneon vs planetscalesupabase vs planetscalevercel vs cloudflare pagesvercel vs netlifynetlify vs cloudflare pagesrailway vs fly iofly io vs herokurender vs railwayrender vs fly iodigitalocean vs hetznerdigitalocean vs hostinger vpshetzner vs hostinger vpsvultr vs hostinger vpslinode vs hostinger vpsdigitalocean vs vultrdigitalocean vs linodevultr vs linodehetzner vs vultrhetzner vs linodeheroku vs renderheroku vs railwayhostinger vs dreamhostsiteground vs dreamhostkinsta vs pressablewp engine vs pressablekinsta vs flywheelwp engine vs flywheelpressable vs flywheelvercel vs aws amplifyaws amplify vs netlifyaws amplify vs cloudflare pageskinsta vs wp enginehostinger vs sitegroundanthropic vs openaianthropic vs google geminianthropic vs deepseekopenai vs google geminiopenai vs deepseekgoogle gemini vs deepseekresend vs postmarkresend vs mailgunresend vs amazon sespostmark vs mailgunpostmark vs amazon sesmailgun vs amazon sesclerk vs auth0clerk vs workosclerk vs better authauth0 vs workosauth0 vs better authworkos vs better authcloudflare queues vs qstashcloudflare queues vs inngestcloudflare queues vs trigger devqstash vs trigger devinngest vs trigger dev