NextMQ

Introduction

NextMQ is a fully managed BullMQ for serverless Next.js. You write the same Queue and Worker code you already know — we host the queue server and Redis and run your jobs for you.

BullMQis the job queue most Node apps reach for. But it assumes something serverless can't give it: a process that stays alive with a live Redis connection. To use it on Vercel you'd have to stand up and babysit your own queue server, Redis, and webhook plumbing.

NextMQ runs all of that for you. You install @nextmq/sdk, paste in your project keys, and write normal BullMQ. Your jobs execute on our managed BullMQ server and call your code back over a signed webhook — with retries, scheduling, rate limits, and flows handled by default.

npm install @nextmq/sdk

What you get#

  • No infrastructure. We host and scale the queue server and Redis.
  • The BullMQ API. Same Queue, Worker, and FlowProducer — nothing new to learn.
  • One route to add. A single handler auto-registers your workers and verifies every call.
  • Defaults that just work. Retries, backoff, delays, priorities, rate limits, dedup, and flows.

What you write#

  • Your queues and the processor functions that run your jobs.
  • One webhook route, created with createNextMQHandler.
  • A little config — your project keys and your app's public URL.

That's the whole surface area. Everything else is managed.

Note
NextMQ is built on real BullMQ, so it's drop-in for the API you already use. A handful of methods that assume a worker running inside your own process behave differently over a managed connection — see Coming from BullMQ.

Good fits#

  • Background work in a Next.js app on Vercel or any serverless platform.
  • Media processing, AI/LLM calls, report generation, syncing to third-party APIs.
  • Anything you'd use BullMQ for — without running BullMQ's infrastructure.

Next steps#

Next →Quickstart