Background Jobs & Cron for Next.js: what 39 makers' products chose
Among 39 makers' products built with Next.js that we know the background jobs & cron of, Trigger.dev leads: 16 of them (41%). Next come Inngest (11) and Temporal (10).
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. A data pipeline orchestrator answers a different need: it runs scheduled data, ETL and ML pipelines as graphs of dependent steps with a run history, rather than jobs your app enqueues when a user does something.
What makers on Next.js chose
| Option | Next.js products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 16 (41%) | 28% | ~20,000 users | $0/moFree | |
| 11 (28%) | 20% | ~5,000 users | $99/moPro | |
| 10 (26%) | 43% | ~1,800 users | $5.50/moDeveloper (pay as you go) | |
| 2 (5%) | 2% | ~10,000 users | $1.00/moPay as you go | |
| 1 (3%) | 1% | — | — | |
| 1 (3%) | 4% | — | — | |
| 1 (3%) | 4% | — | — |
Live makers' products with a source for both: that they're built with Next.js, and what they use for background jobs & cron. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You deploy to serverless hosting and have tasks that run for minutes
Trigger.dev 16 here - One user action kicks off several steps with waits between them
Inngest 11 here - A process runs for days or months and must pick up where it left off after a crash
Temporal 10 here - You only need a scheduled call or a delayed HTTP request on serverless
Upstash 2 here - You already run a Node server and want a free queue next to it, on Redis or Postgres
BullMQ 1 here
Trigger.dev
Hosted job platform16 Next.js products here (41%). Free up to about 20,000 users. About $0 a month at 10,000 users (Free).
llms.txtBest 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.
“Probably one of the best background task experiences I've ever had, it's so nice working with tools like this. Everything just works and it's super complete”
- Tasks run without timeouts and retry automatically, which suits long-running, multi-step AI workflows and agents. 4 sources
- It takes queues and job infrastructure off the team's plate while staying in a TypeScript stack. 3 sources
“Orchestrates our long-running background agents 24/7”
Background Jobs & CronMaker says so +1 · source ↗“Trigger.dev powers our AI workflow execution engine. Running complex multi-step AI workflows reliably in the background — with support for long-running tasks and automatic retries — would have been incredibly complex to build ourselves. Thank you for making background job processing so developer-friendly!”
Background Jobs & CronMaker says so +1 · source ↗“We have a lot of background jobs in Midday, and thanks to Trigger.dev we can focus on building our product instead of handling queues and infrastructure.”
Background Jobs & CronMaker says so · source ↗“Probably one of the best background task experiences I've ever had, it's so nice working with tools like this. Everything just works and it's super complete”
Background Jobs & CronMaker says so · source ↗“With Trigger.dev we make sure every background job is resilient and durable!”
Background Jobs & CronMaker says so · source ↗“The processing of indexing data from various work applications is performed through time-consuming processes, retries, and tracking of their status. We were provided with a powerful way of running and monitoring these workflows using Trigger.dev.”
Background Jobs & CronMaker says so · source ↗“CopyCopter uses Trigger.dev as a background job manager, making the code cleaner, more scalable and more fun to play with! Trigger.dev is a must-have for NextJS Serverless App.s”
Background Jobs & CronMaker says so · source ↗
Inngest
Hosted job platform11 Next.js products here (28%). Free up to about 5,000 users. About $99 a month at 10,000 users (Pro).
llms.txtCLIIn LovableBest forEvent-driven, multi-step workflows where each step retries on its own and your code stays in your existing app.
Trade-offPricing scales with executions and steps, so chatty workflows cost more.
“Inngest's queuing system is a fantastic improvement over managing queues ourselves - it frees up time so we can spend talking to more customers instead.”
- It replaces a self-hosted Redis queue and workers, so teams stop running event infrastructure themselves. 2 sources
- Workflows can be tested locally, and production runs come with tracing and monitoring built in. 3 sources
Status page: 14 incidents in the last 90 days, 4 major (its own page, 2026-10-19).
“Great integration with the modern Vercel stack!”
Background Jobs & CronMaker says so +1 · source ↗“Inngest is powering our background jobs and workflows with ease! Its powerful automation and seamless integration into our development process allow us to focus on building without worrying about infrastructure.”
Background Jobs & CronMaker says so +1 · source ↗“All of our async operations run on Inngest. They have the best DX. Super simple to do debouncing, throttling, fanning out, and more. Easy to test in local, and easy to monitor in production.”
Background Jobs & CronMaker says so · source ↗“We also hosted our own Redis-based queue before managing events infra became a job in itself. Inngest has top tier local dev DX and helps our background jobs scale infinitely.”
Background Jobs & CronMaker says so · source ↗“Inngest's queuing system is a fantastic improvement over managing queues ourselves - it frees up time so we can spend talking to more customers instead.”
Background Jobs & CronMaker says so · source ↗“Inngest is doing all the magic for us!”
Background Jobs & CronMaker says so · source ↗“It helped me to create very complex workflows very fast.”
Background Jobs & CronMaker says so · source ↗“Fantastic for background job handling, with first-class observability built in.”
Background Jobs & CronMaker says so · source ↗
Temporal
Durable workflow engine10 Next.js products here (26%). Free up to about 1,800 users. About $5.50 a month at 10,000 users (Developer (pay as you go)).
llms.txtBest 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.
“Reliable execution of tasks is the backbone of many of the solutions we offer and Temporal is a great enabler for this.”
- Durable workflows survive retries, timeouts, crashes and deploys, replacing fragile stacks of queues, timers and cron jobs. 4 sources
- Retries and compensating actions are handled by the platform, so application code describes business logic rather than failure handling. 4 sources
- It adds a real step up in app complexity and cognitive overhead, and some teams migrated off happier. 3 sources
- Running it highly available in-house takes dedicated on-call engineers, which pushes teams to the paid cloud. 1 source
Status page: 23 incidents in the last 90 days, 3 major (its own page, 2026-10-19).
“We chose Temporal because it provides a reliable foundation for long-running tasks.”
Background Jobs & CronMaker says so · source ↗“Reliable execution of tasks is the backbone of many of the solutions we offer and Temporal is a great enabler for this.”
Background Jobs & CronMaker says so · source ↗“We could not make this without Temporal super system for workflows”
Background Jobs & CronMaker says so +1 · source ↗“As a team building complex workflows in voice AI, Roark wouldn’t exist without Temporal. It gave us the reliability of a distributed system without drowning in glue code. Temporal turned what used to be a mess of retries, timers, and state machines into something we can trust to run at scale.”
Background Jobs & CronMaker says so · source ↗
Upstash
Serverless queue2 Next.js products here (5%). Free up to about 10,000 users. About $1.00 a month at 10,000 users (Pay as you go).
llms.txtIn v0Best 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.
“We use Upstash for caching and queues – it's been incredibly reliable for us since day one!”
- Its serverless Redis is the default cache and shared-state store in Next.js and Vercel side projects, with nothing to operate. 4 sources
- It speaks the Redis protocol, so it is easy to swap for another Redis-compatible store later. 2 sources
- Databases get temporarily rate-limited under traffic spikes, taking apps down during a front-page surge. 3 sources
- Paying per transaction costs more than running a Redis-compatible store on one VM. 1 source
Status page: 5 incidents in the last 90 days, 1 major (its own page, 2026-10-19).
“Simple to use serverless Redis”
Background Jobs & CronMaker says so +2 · source ↗“We use Upstash for caching and queues – it's been incredibly reliable for us since day one!”
Background Jobs & CronMaker says so +1 · source ↗Also chosen, and not seen yet
Fewer Next.js products here: BullMQ (1), RabbitMQ (1), Dagster (1).
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Next.js.
- BullMQ → Temporal 3 pull requests
- Trigger.dev → BullMQ 3 pull requests
Getting background jobs & cron right
Anything that takes more than a few seconds or calls a flaky third-party API belongs in a job, not in the request handler. Make every job safe to run twice, because retries will run it twice. If you deploy to serverless functions, pick a hosted option; if you already run a server and Redis, a library queue is enough.
- Firing off a promise without awaiting it in a serverless function; the function is frozen after the response and the work silently never finishes.
- Putting whole objects in the job payload instead of IDs, so the job acts on stale data by the time it runs.
- Running scheduled jobs with no alert on failure, so a nightly cleanup can be broken for weeks before anyone notices.
The rest of the Next.js stack
What makers' Next.js products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 1,078 of 1,312
- Transactional Email: Resend 493 of 830
- Database: Supabase 171 of 382
- Payments: Stripe 288 of 359
- LLM API: OpenAI API 222 of 301
- Authentication: Clerk 176 of 211
- Web Analytics: Google Analytics 105 of 197
- Product Analytics: PostHog 123 of 168
Questions
What do most Next.js apps use for background jobs & cron?
Among 39 makers' products built with Next.js that we know the background jobs & cron of, Trigger.dev leads: 16 of them (41%). Next come Inngest (11) and Temporal (10).
What does background jobs & cron cost for a Next.js app with 10,000 users?
On our usage model at 10,000 users, Trigger.dev comes to about $0 a month (Free); Inngest comes to about $99 a month (Pro); Temporal comes to about $5.50 a month (Developer (pay as you go)); Upstash comes to about $1.00 a month (Pay as you go). Prices are from each vendor's pricing page.
Which background jobs & cron option stays free longest for a Next.js app?
Trigger.dev: on our usage model its cheapest plan stays free up to about 20,000 users.
How this is counted: a product is on Next.js when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its background jobs & cron. How evidence is collected.