Skip to content

Best Background Jobs of 2026

Updated · 7 picks · live pricing · affiliate disclosure

Durable-execution platform with 5 SDKs (Go, Java, Python, TypeScript, .NET) and per-action pay-as-you-go.

BEST OVERALL9.8/10

Temporal Cloud

Durable-execution platform with 5 SDKs (Go, Java, Python, TypeScript, .NET) and per-action pay-as-you-go.

$1K credits 14-day trial; pay-as-you-go after

How it stacks up

  • Free trial $1K

    vs Inngest Step Functions

  • $0.42/1M actions

    vs Hatchet OSS Postgres

  • Enterprise custom

    vs Trigger.dev TS-only

#2
Upstash QStash8.2/10

From $10/mo

View
#3
Defer7.3/10

From $15/mo

View

All picks at a glance

#PickBest forStartingScore
1Temporal CloudBest durable-execution platform with 5 SDKs across major languagesFree9.8/10
2Upstash QStashBest HTTP-based serverless queue with pay-per-message pricing$10.00/mo8.2/10
3DeferBest simple TypeScript SDK background jobs with cron and retries$15.00/mo7.3/10
4InngestBest event-driven background jobs with Step Functions and per-event pricing$30.00/mo6.0/10
5HatchetBest open-source PostgreSQL-based background jobs with TypeScript and Python$50.00/mo5.8/10
6Trigger.devBest TypeScript indie-friendly background jobs with cheap Hobby tier$10.00/mo5.3/10
7BullMQ ProBest Redis-based background jobs with BullMQ Pro observability$249.00/mo4.5/10

Quick pick by use case

If you only have thirty seconds, find your situation below and skip to that pick.

Compare all 7 picks

Top spec
#1Temporal Cloud9.8/10FreeFree trial $1K
#2Upstash QStash8.2/10$10.00/mo$120.00/yrSave $240/yrFree 500/day
#3Defer7.3/10$15.00/mo$180.00/yrSave $180/yrFree 1K execs
#4Inngest6.0/10$300.00/mo$3,600.00/yr$3,240/yr moreFree 50K events
#5Hatchet5.8/10$50.00/mo$600.00/yr$240/yr moreOSS MIT
#6Trigger.dev5.3/10$50.00/mo$600.00/yr$240/yr moreFree 10K runs
#7BullMQ Pro4.5/10$249.00/mo$2,988.00/yr$2,628/yr moreOSS BullMQ MIT
#1

Temporal Cloud

9.8/10

Best durable-execution platform with 5 SDKs across major languages

Durable-execution platform with 5 SDKs (Go, Java, Python, TypeScript, .NET) and per-action pay-as-you-go.

PlanMonthlyWhat you get
Free trialFreeOne-thousand-dollar credits with 14-day evaluation.
Pay-as-you-goFreePer-action pricing with 5 SDKs across major languages.
EnterpriseCustomCustom regions with dedicated cells and premium support.

Temporal Cloud is the durable-execution pick for teams running long-running workflows that need to survive process restarts, deployments, and infrastructure failures. Founded in 2019 by ex-Uber Cadence engineers, Temporal built the canonical durable-execution platform where workflow state persists across compute failures and steps replay deterministically from event history.

Three tiers serve three buyers. Free trial ships $1,000 in credits with 14-day evaluation and all features unlocked. Pay-as-you-go ships $0.42 per 1M actions plus $0.039 per GB-day storage with 5 SDKs across Go, Java, Python, TypeScript, .NET. Enterprise ships custom pricing with custom regions plus dedicated cells, premium support, and dedicated CSM.

The load-bearing wedge is durable-execution semantics plus polyglot SDKs. Where Inngest Step Functions retry steps independently and Trigger.dev focuses on TypeScript-first runs, Temporal stores complete workflow history and replays from any point on failure; for long-running workflows (multi-day approvals, multi-week ETL pipelines, distributed sagas), Temporal's history replay handles partial failure differently from event-driven retries. The catch is the conceptual learning curve. For teams running long-running workflows across polyglot services, Temporal is the proven path; for short-lived background jobs, alternatives cost less and learn faster.

Pros

  • 5 SDKs across Go, Java, Python, TypeScript, .NET
  • Durable-execution semantics with full history replay
  • Pay-as-you-go $0.42 per 1M actions plus storage
  • Custom regions plus dedicated cells on Enterprise
  • Built by ex-Uber Cadence team since 2019

Cons

  • Conceptual learning curve for replay-based execution model
  • Per-action pricing compounds for high-step-count workflows
Free trial $1K$0.42/1M actionsEnterprise custom$1K credits 14-day trial; pay-as-you-go after

Best for: Teams running long-running polyglot workflows across multiple languages. Free trial $1K credits; Pay-as-you-go $0.42/1M actions; Enterprise custom.

Self-host posture
9
Job dispatch latency
9
Setup complexity
7
Value
9
Support
9
#2

Upstash QStash

8.2/10Save $240/yr

Best HTTP-based serverless queue with pay-per-message pricing

HTTP-based serverless queue with pay-per-message and 7-day retention on Free tier.

PlanMonthlyAnnualWhat you get
FreeFreeFive-hundred messages daily with HTTP-based delivery.
Pay-as-you-goFree$1.00/yrPer-message pricing with no max throughput.
Pro$10.00/mo$120.00/yrHigher rate limits with 30-day retention and priority.
EnterpriseCustomCustomBYOC option with SAML SSO and dedicated CSM.

Upstash QStash is the HTTP-based serverless pick for teams running on Vercel, Cloudflare Workers, or AWS Lambda where the application stack is already serverless. Built by Upstash founded 2020, QStash treats every job as an HTTP webhook that fires at a scheduled time or after a delay, which fits naturally into serverless functions without long-running worker processes.

Four tiers serve four buyers. Free ships 500 messages per day with no card required, 7-day retention, and HTTP-based delivery. Pay-as-you-go ships $1 per 100K messages with 14-day retention and no max throughput. Pro ships $10/mo plus usage with higher rate limits and 30-day retention. Enterprise ships custom with BYOC option, SAML SSO, and dedicated CSM.

The load-bearing wedge is HTTP-as-job-protocol. Where Inngest, Trigger.dev, Defer, and Hatchet require running worker processes, QStash fires HTTP webhooks at scheduled times; for serverless apps where every endpoint is already an HTTP function, QStash adds nothing new beyond a webhook trigger plus retry. The catch is the lack of step orchestration; multi-step workflows require chaining HTTP calls manually rather than using a Step Functions abstraction. For serverless teams running simple delayed or scheduled tasks, QStash is the proven path; for multi-step workflows, alternatives cover better.

Pros

  • HTTP-as-job-protocol fits serverless natively
  • Free 500 messages/day with no card required
  • Pay-as-you-go $1 per 100K messages
  • 30-day retention on Pro tier
  • Bundled with Upstash Redis ecosystem

Cons

  • No step orchestration for multi-step workflows
  • HTTP-only delivery limits worker-process patterns
Free 500/dayPAYG $1/100KPro $10/moFree 500 messages/day; cancel-anytime

Best for: Serverless teams on Vercel, Cloudflare Workers, AWS Lambda running scheduled tasks. Free 500/day; Pay-as-you-go $1/100K; Pro $10/mo; Enterprise BYOC.

Self-host posture
9
Job dispatch latency
9
Setup complexity
10
Value
10
Support
8
#3

Defer

7.3/10Save $180/yr

Best simple TypeScript SDK background jobs with cron and retries

Simple TypeScript SDK platform with cron jobs and retries on Pro $15/mo.

PlanMonthlyAnnualWhat you get
FreeFreeOne-K executions with TypeScript SDK and one environment.
Pro$15.00/mo$180.00/yrTen-K executions with cron jobs, retries, multiple environments.
Business$99.00/mo$1,188.00/yrHundred-K executions with higher concurrency and dedicated workers.
EnterpriseCustomCustomBYOC option with SAML SSO and dedicated support.

Defer is the simple-TypeScript pick for solo developers and small teams who want a minimal background-jobs SDK without Step Functions complexity. Founded in 2022 in France, Defer built a TypeScript-only SDK that treats each background job as a single function call with optional cron and retry decorators rather than the multi-step durable-execution model of Inngest or Temporal.

Four tiers serve four buyers. Free ships up to 1K executions monthly with TypeScript SDK and 1 environment. Pro ships $15/mo with 10K executions plus multiple environments, cron jobs, and retries. Business ships $99/mo with 100K executions plus higher concurrency and dedicated workers. Enterprise ships custom with BYOC option and SAML SSO.

The load-bearing wedge is API simplicity. Where Inngest ships Step Functions abstraction and Temporal ships durable-execution semantics, Defer ships a single decorator that turns any TypeScript function into a background job; for solo developers building Next.js apps where async work is bounded to single-step tasks, Defer's API is the easiest learn in lineup. The catch is the limited feature surface; no Step Functions, no polyglot SDKs, no durable execution. For solo TypeScript developers building Next.js apps with simple async needs, Defer is the proven entry; for multi-step workflows, alternatives cover better.

Pros

  • Simplest TypeScript SDK in lineup with single decorator
  • Free 1K executions covers small-team evaluation
  • Cron jobs plus retries on Pro $15/mo
  • Dedicated workers on Business $99/mo
  • BYOC plus SAML SSO on Enterprise

Cons

  • No Step Functions for multi-step workflows
  • TypeScript-only SDK excludes polyglot teams
Free 1K execsPro $15/mo 10KBusiness $99/moFree 1K executions; cancel-anytime

Best for: Solo TypeScript developers building Next.js apps with simple async needs. Free 1K executions; Pro $15/mo 10K; Business $99/mo 100K; Enterprise BYOC.

Self-host posture
9
Job dispatch latency
9
Setup complexity
10
Value
9
Support
8
#4

Inngest

6.0/10$3,240/yr more

Best event-driven background jobs with Step Functions and per-event pricing

Event-driven leader with Step Functions, retries, and concurrency limits across Basic and Pro tiers.

PlanMonthlyAnnualWhat you get
FreeFreeFifty-K events monthly with Step Functions and retries.
Basic$30.00/mo$360.00/yr250K events with concurrency limits and standard support.
Pro$300.00/mo$3,600.00/yrFive-M events with higher concurrency and custom retention.
EnterpriseCustomCustomBYOC option with SAML SSO, audit, and dedicated CSM.

Inngest is the default event-driven background-jobs platform for modern TypeScript and Python teams in 2026. Founded in 2021, Inngest built around the Step Functions abstraction where async workflows are defined as durable steps that survive function restarts and retry on failure with per-step idempotency.

Four tiers serve four buyers. Free ships 50K events plus 5K function invocations per day with Step Functions and retries. Basic ships $30/mo with 250K events and 50K invocations per day plus concurrency limits. Pro ships $300/mo with 5M events plus higher concurrency and custom retention. Enterprise ships custom with BYOC option, SAML SSO, audit, and dedicated CSM.

The load-bearing wedge is Step Functions plus event-driven model. Where Trigger.dev and Defer treat each background job as a single function invocation, Inngest treats workflows as multi-step durable executions where each step is independently retryable; for SaaS apps with multi-step user-flows (signup with email plus billing plus provisioning), Inngest's step model handles partial failure naturally. The catch is the per-event pricing compounding past 5M events; Pro $300 covers 5M events but the next tier jumps to Enterprise. For modern SaaS teams running multi-step async workflows, Inngest is the proven path; for simple task queues, alternatives cost less.

Pros

  • Step Functions for multi-step durable workflow execution
  • Free 50K events plus 5K invocations daily covers SMB
  • Concurrency limits plus standard support on Basic $30
  • BYOC option plus SAML SSO on Enterprise
  • Brand-recognition leader for event-driven background jobs

Cons

  • Per-event pricing compounds past 5M events
  • Step Functions abstraction over-engineered for simple jobs
Free 50K eventsBasic $30/moPro $300/moFree 50K events; cancel-anytime

Best for: Modern SaaS teams running multi-step async workflows with retries and idempotency. Free 50K events; Basic $30/mo; Pro $300/mo; Enterprise BYOC.

Self-host posture
9
Job dispatch latency
9
Setup complexity
9
Value
8
Support
9
#5

Hatchet

5.8/10$240/yr more

Best open-source PostgreSQL-based background jobs with TypeScript and Python

OSS PostgreSQL-based jobs with MIT license, Go core, plus TypeScript and Python SDKs.

PlanMonthlyAnnualWhat you get
OSS (free)FreeMIT-licensed self-hosted PostgreSQL plus Go core.
Cloud FreeFreeTen-K events with 5 concurrent workers hosted.
Cloud Pro$50.00/mo$600.00/yr250K events with higher concurrency and SLA.
EnterpriseCustomCustomBYOC plus dedicated infrastructure with SAML and audit.

Hatchet is the OSS-PostgreSQL pick for engineering teams who want a self-hostable background-jobs platform without Redis dependency. Founded in 2023, Hatchet built the platform around PostgreSQL as the queue backend rather than Redis, which eliminates the operational complexity of running a separate Redis cluster and lets teams reuse their existing PostgreSQL infrastructure.

Four tiers serve four buyers. OSS ships MIT-licensed self-hosted with PostgreSQL plus Go-based core and TypeScript plus Python SDKs. Cloud Free ships up to 10K events monthly with 5 concurrent workers hosted. Cloud Pro ships $50/mo with 250K events plus higher concurrency and SLA. Enterprise ships custom with BYOC plus dedicated infrastructure, SAML SSO, audit, and premium support.

The load-bearing wedge is the PostgreSQL-as-queue model plus permissive MIT license. Where BullMQ requires Redis and SaaS alternatives lock data in vendor cloud, Hatchet runs entirely on customer PostgreSQL with the same Postgres engineers already operate; for teams with PostgreSQL expertise but no Redis ops, Hatchet OSS removes a vendor dependency. The catch is the relative newness of the platform versus Inngest or Temporal. For OSS-purist engineering teams already on PostgreSQL, Hatchet is the proven path; for established platforms with longer track records, alternatives cover better.

Pros

  • PostgreSQL-as-queue eliminates Redis dependency
  • MIT-licensed OSS self-hosted with no licensing fee
  • TypeScript plus Python SDKs with Go core
  • BYOC plus dedicated infrastructure on Enterprise
  • Cloud Free 10K events covers small-team evaluation

Cons

  • Newer platform versus Inngest or Temporal track record
  • Smaller community than Inngest or BullMQ
OSS MITCloud Free 10KCloud Pro $50/moOSS MIT free forever; Cloud Free 10K events

Best for: OSS-purist engineering teams already on PostgreSQL without Redis ops capacity. OSS MIT free; Cloud Free 10K events; Cloud Pro $50/mo; Enterprise BYOC.

Self-host posture
10
Job dispatch latency
9
Setup complexity
8
Value
10
Support
7
#6

Trigger.dev

5.3/10$240/yr more

Best TypeScript indie-friendly background jobs with cheap Hobby tier

TypeScript-first indie platform with Free 10K runs and $10/mo Hobby tier for cheap indie evaluation.

PlanMonthlyAnnualWhat you get
FreeFreeTen-K runs with 25 concurrent and TypeScript-first SDK.
Hobby$10.00/mo$120.00/yrFifty-K runs at the indie-friendly entry tier.
Pro$50.00/mo$600.00/yrFive-hundred-K runs with 250 concurrent and priority support.
EnterpriseCustomCustomSelf-hosted option with SAML SSO and dedicated CSM.

Trigger.dev is the TypeScript-first indie-friendly pick for solo developers and small teams who want background jobs without enterprise pricing. Founded in 2022 in the UK, Trigger.dev built around a TypeScript-first SDK with the cheapest paid entry tier in lineup at $10/mo Hobby that targets indie hackers and solo builders.

Four tiers serve four buyers. Free ships 10K runs per month with 1 dev environment and up to 25 concurrent runs. Hobby ships $10/mo with 50K runs and 50 concurrent runs plus standard support. Pro ships $50/mo with 500K runs and 250 concurrent runs plus priority support. Enterprise ships custom with self-hosted option, SAML SSO, and dedicated CSM.

The load-bearing wedge is the indie-friendly $10/mo Hobby tier. Where Inngest Basic starts at $30/mo and other picks jump to enterprise pricing quickly, Trigger.dev Hobby covers indie projects at a third the price; for solo developers running side projects with bounded run counts, the math works without burning the project budget on infrastructure. The catch is the TypeScript-only SDK; Python or Go services cannot use Trigger.dev directly. For solo TypeScript developers running indie projects, Trigger.dev is the proven path; for polyglot teams, alternatives cover better.

Pros

  • Cheapest paid Hobby tier at $10/mo with 50K runs
  • TypeScript-first SDK matches modern Next.js stacks
  • Free 10K runs covers small-team evaluation
  • 250 concurrent runs on Pro $50/mo
  • Self-hosted option on Enterprise

Cons

  • TypeScript-only SDK excludes Python and Go services
  • Smaller community than Inngest for support
Free 10K runsHobby $10/moPro $50/moFree 10K runs; cancel-anytime

Best for: Solo TypeScript developers running indie projects with bounded run counts. Free 10K runs; Hobby $10/mo; Pro $50/mo; Enterprise self-hosted.

Self-host posture
9
Job dispatch latency
9
Setup complexity
10
Value
10
Support
8
#7

BullMQ Pro

4.5/10$2,628/yr more

Best Redis-based background jobs with BullMQ Pro observability

Redis-based BullMQ Pro with job grouping, observability, and per-instance pricing.

PlanMonthlyAnnualWhat you get
OSS BullMQFreeMIT-licensed Redis-based queue Node.js library.
Pro$249.00/mo$2,988.00/yrPer-instance Pro with job grouping and observability.
EnterpriseCustomCustomMultiple instances with custom support and dedicated CSM.

BullMQ Pro is the Redis-based pick for teams already running Redis who want job grouping plus observability on top of the BullMQ open-source library. Built by Taskforce.sh founded 2018, BullMQ ships as the canonical Node.js queue library that works on existing Redis infrastructure; BullMQ Pro adds job grouping, observability, and a dashboard at $249/mo per instance.

Three tiers serve three buyers. OSS BullMQ ships MIT-licensed free with Redis-based queue and Node.js library plus community support. Pro ships $249/mo per instance with job grouping, observability, premium support, and dashboard included. Enterprise ships custom pricing with multiple instances, custom support, and dedicated CSM.

The load-bearing wedge is the Redis-already-installed compatibility. Where Hatchet requires PostgreSQL and Inngest is SaaS-only, BullMQ runs on the Redis cluster teams have already deployed for caching or session storage; for teams who already operate Redis, BullMQ adds nothing new to the operational footprint. The catch is the per-instance pricing; $249/mo per Redis instance compounds for teams running multiple Redis clusters. For Node.js teams already on Redis with bounded instance counts, BullMQ Pro is the proven path; for greenfield deployments, alternatives without Redis dependency cover better.

Pros

  • Runs on existing Redis infrastructure with no new ops
  • OSS BullMQ MIT-licensed free for unlimited usage
  • Job grouping plus observability plus dashboard on Pro
  • Multiple instances plus custom support on Enterprise
  • Canonical Node.js queue library since 2018

Cons

  • Per-instance pricing compounds across Redis clusters
  • Node.js-only library excludes polyglot teams
OSS BullMQ MITPro $249/mo/instanceEnterprise customOSS BullMQ MIT free; cancel-anytime

Best for: Node.js teams already on Redis with bounded instance counts. OSS BullMQ MIT free; Pro $249/mo per instance with observability; Enterprise custom contract.

Self-host posture
10
Job dispatch latency
9
Setup complexity
8
Value
7
Support
8

How we picked

Each pick gets a transparent composite score from price, features, free-tier availability, and editor fit. Pricing flows from our live database, so when a vendor changes prices the score updates here too.

We weight price 40 percent, features 30, free tier 15, and fit 15. Editorial pinning places Inngest #1 over composite-leading Temporal Cloud on brand recognition. Temporal uses per-action pay-as-you-go; QStash uses per-message; Inngest uses per-event quota. typical-tier matches mid-paid tier where applicable; lowMonthly reflects the SMB entry tier per pick.

We don't claim "30,000 hours of testing." Our methodology is the formula above plus the editor's published verdict for each pick. Verifiable, auditable, and updated when the underlying data changes.

Why trust Subrupt

We're a subscription tracker first, a buying guide second. Every claim on this page is something you can check.

By use case

Best event-driven background jobs platform

Inngest

Read the full review →

Best TypeScript indie-friendly background jobs

Trigger.dev

Read the full review →

Best open-source PostgreSQL-based background jobs

Hatchet

Read the full review →

Best durable-execution platform for long-running workflows

Temporal Cloud

Read the full review →

Best HTTP-based serverless queue

Upstash QStash

Read the full review →

Didn't make the list

Already in picks (third) but worth flagging the 5 SDK polyglot coverage. Go, Java, Python, TypeScript, .NET match enterprise polyglot footprints other picks cannot serve.

Already in picks (fourth) but worth flagging PostgreSQL-as-queue. MIT-licensed OSS eliminates Redis dependency for teams already on PostgreSQL.

Already in picks (fifth) but worth flagging HTTP-as-job-protocol. Serverless-native delivery fits Vercel, Cloudflare Workers, AWS Lambda without worker processes.

Already in picks (second) but worth flagging the Hobby tier. $10/mo with 50K runs is the cheapest paid entry in lineup for indie TypeScript developers.

How to choose your Background Jobs

Seven product shapes compete for one head term

The 'best background jobs' search covers seven distinct shapes. Event-driven leader (Inngest) targets modern SaaS teams running multi-step async workflows. TypeScript indie-friendly (Trigger.dev) targets solo TypeScript developers running indie projects. Simple TypeScript SDK (Defer) targets Next.js developers with simple async needs. Open-source PostgreSQL (Hatchet) targets OSS-purist teams already on PostgreSQL. Durable-execution (Temporal Cloud) targets teams running long-running polyglot workflows. HTTP-based serverless (Upstash QStash) targets serverless teams on Vercel, Cloudflare Workers, AWS Lambda. Redis-based BullMQ (BullMQ Pro) targets Node.js teams already on Redis. The honest framework: identify whether your bottleneck is workflow complexity, language ecosystem, or compliance posture.

Per-event vs per-action vs per-instance pricing math

The pricing model decision drives unit economics more than vendor selection. Per-event (Inngest, Hatchet) bills on workflow trigger count. Per-action (Temporal Cloud) bills on individual workflow steps. Per-message (QStash) bills on dispatched messages. Per-run (Trigger.dev) bills on background-job invocations. Per-instance (BullMQ Pro) bills flat per Redis cluster. The honest framework: per-event wins for teams with high-throughput simple jobs where step count is bounded. Per-action wins for long-running multi-step workflows where steps count differently from events. Per-instance wins for Redis-already teams with one or two instances; multiple instances compound the math.

Step Functions (Inngest) vs durable execution (Temporal) vs simple jobs (Defer)

The workflow-abstraction decision drives team mental model. Step Functions (Inngest, Hatchet) treat workflows as multi-step async functions where each step retries independently with idempotency. Durable execution (Temporal Cloud) stores complete workflow history and replays from any point on failure. Simple jobs (Defer, Trigger.dev, QStash) treat each background task as a single function invocation. The honest framework: simple jobs win for solo developers and small teams whose async work is bounded to single-step tasks. Step Functions wins for SaaS apps with multi-step user flows where partial failure is the load-bearing concern. Durable execution wins for long-running workflows (multi-day approvals, distributed sagas) where history replay matters.

TypeScript-only vs polyglot SDKs: pick by team language

The SDK ecosystem decision drives team adoption. TypeScript-only platforms (Trigger.dev, Defer) ship a single TypeScript SDK that fits modern Next.js and Node.js stacks. Polyglot platforms (Inngest with TypeScript plus Python plus Go, Hatchet with TypeScript plus Python plus Go core, Temporal Cloud with 5 SDKs) cover multiple languages. The honest framework: TypeScript-only wins for teams whose entire backend runs Node.js where polyglot coverage is overkill. Polyglot wins for teams running multiple language services where one background-jobs platform across all services beats running per-language tools. Temporal Cloud's 5 SDKs cover the broadest polyglot footprint.

OSS self-hosted (Hatchet, BullMQ) vs SaaS (Inngest, Trigger.dev, Temporal)

The OSS self-hosted versus SaaS decision drives compliance posture and operational lift. OSS self-hosted (Hatchet OSS, BullMQ OSS, Inngest OSS) keeps job data on customer infrastructure with no vendor cloud dependency. SaaS (Inngest Cloud, Trigger.dev, Temporal Cloud, Defer, QStash) sends job data to vendor cloud which compliance-heavy teams cannot accept. The honest framework: OSS wins for FedRAMP, HIPAA, or air-gapped requirements where job data cannot leave customer infrastructure. SaaS wins for teams without those constraints where the operational lift of running BullMQ on Redis or Hatchet on PostgreSQL exceeds the SaaS fee saved.

When Inngest wins versus Hatchet at scale

Inngest versus Hatchet is the load-bearing decision for SaaS teams choosing modern background jobs. Inngest wins when (1) Step Functions abstraction is load-bearing for multi-step user-flow workflows, (2) brand-recognition matters for procurement at series A or beyond where modern async-jobs reference base is required, (3) per-event pricing aligns with the team's workflow shape. Hatchet wins when (1) the team is already on PostgreSQL and Redis ops capacity is constrained, (2) MIT OSS license is required for compliance posture or vendor-neutral deployment, (3) polyglot Go plus TypeScript plus Python services need a unified queue platform. The honest framework: SaaS-acceptable teams pick Inngest. OSS-purist teams pick Hatchet.

Frequently asked questions

Are these prices guaranteed not to change?

Vendor pricing changes regularly. Rates here are what each vendor advertises as of May 2026. Inngest Basic $30/mo stable. Trigger.dev Hobby $10/mo stable. Defer Pro $15/mo stable. Hatchet Cloud Pro $50/mo stable. Temporal Cloud Pay-as-you-go $0.42/1M actions stable. Upstash QStash Pay-as-you-go $1/100K stable. BullMQ Pro $249/mo per instance stable. Verify with vendor before institutional contracts.

Does Subrupt earn a commission from any of these picks?

We track which picks have approved affiliate programs in our database, and the FTC disclosure block at the top of every guide names which ones currently have a click-tracking partnership. Affiliate revenue does not change ranking. The composite math runs against the same weights for every pick regardless of partnership.

Why is Inngest ranked first instead of composite-leading Temporal Cloud?

Inngest leads brand recognition for modern event-driven background jobs since 2021 with the deepest Step Functions reference base, and is uniquely-true on the event-driven-leader flag. Temporal Cloud wins composite math at $1K free trial credits but covers the durable-execution audience with 5 SDKs. The picks-array order leads with the head-term-search brand. Temporal is in picks (third) for polyglot durable-execution readers.

Should I pick Step Functions (Inngest) or simple jobs (Defer, Trigger.dev)?

Pick by workflow complexity. Simple jobs win for solo developers and small teams whose async work is bounded to single-step tasks (send email, generate PDF, refresh cache). Step Functions wins for SaaS apps with multi-step user flows (signup with email plus billing plus provisioning plus welcome) where partial failure is the load-bearing concern. Most teams start with simple jobs and add Step Functions only when retry-step idempotency becomes load-bearing.

When does Temporal beat Inngest for long-running workflows?

When workflows run multi-day or multi-week. Temporal stores complete workflow history and replays from any point on failure; multi-day approvals, multi-week ETL pipelines, and distributed sagas survive process restarts and deployments naturally. Inngest Step Functions retry steps independently but do not store full history for replay-from-arbitrary-point. For workflow durations exceeding a few hours, Temporal is the proven path; below that, Inngest is simpler.

When does Hatchet OSS beat SaaS alternatives?

When PostgreSQL-already and Redis-not. Hatchet uses PostgreSQL as the queue backend rather than Redis; teams already operating PostgreSQL avoid running a separate Redis cluster purely for job queues. SaaS alternatives (Inngest, Trigger.dev, Temporal Cloud) send job data to vendor cloud. For OSS-purist teams already on PostgreSQL, Hatchet is the proven path; for SaaS-acceptable teams, alternatives are easier to operate.

When does QStash beat worker-based background jobs?

When the application stack is fully serverless. QStash treats every job as an HTTP webhook that fires at scheduled times; for serverless apps on Vercel, Cloudflare Workers, or AWS Lambda where every endpoint is already an HTTP function, QStash adds nothing new beyond a webhook trigger plus retry. Worker-based platforms (Inngest, Trigger.dev, Hatchet, BullMQ) require running long-lived worker processes that serverless deployments cannot host natively.

Should I run Trigger.dev or Defer for solo TypeScript projects?

Pick by feature surface. Trigger.dev ships Step Functions plus 250 concurrent runs on Pro $50/mo for indie projects with multi-step async needs. Defer ships simpler API at Pro $15/mo for projects with single-step async needs. The decision tree: multi-step workflows pick Trigger.dev. Single-step tasks pick Defer at lower price floor. Most indie projects start with Defer and migrate to Trigger.dev when Step Functions becomes load-bearing.

Should I run multiple background-jobs platforms?

Most teams pick one. Multi-platform stacks add cognitive load on backend developers without proportional benefit; the same async tasks run identically across Inngest, Hatchet, or Trigger.dev. Exception: serverless apps may run QStash for HTTP-triggered jobs plus worker-based jobs (Inngest or Trigger.dev) for long-running tasks. Avoid running Inngest plus Trigger.dev plus Hatchet simultaneously; pick one platform plus optionally one HTTP-based serverless layer.

When does this guide get updated?

We aim to refresh /best/ guides quarterly when there are no major shifts, and immediately when there are. Major triggers: vendor pricing changes (rates stable through May 2026), new entrants (Inngest Step Functions evolution, Temporal Cloud regional expansion, Hatchet community growth), Inngest per-event rate changes, Temporal per-action rate changes, Upstash QStash policy changes. The lastReviewed date at the top reflects the most recent editorial sweep.

Subrupt Editorial

The team behind subrupt.com. We track subscriptions, surface cheaper alternatives, and publish buying guides where the score formula is on the page so you can recompute it yourself. We do not claim 30,000 hours of testing. What we claim is live pricing from our database, a transparent composite score, and honest savings math against a category baseline.

Last reviewed

Citations

Affiliate disclosure: Subrupt earns a commission when you switch to a service through our recommendation links. This never changes the price you pay. We only recommend services where there's a real cost or feature advantage for you, and our picks are based on the data on this page, not on which programs pay the most.

Related buying guides

Track your subscriptions on Subrupt

Add the Background Jobs you pay for and see how much you'd save by switching.

Open dashboard

More buying guides

Independent rankings for the subscriptions worth paying for.

See all guides