Queue and background job services compared — with real pricing, hidden costs, and known gotchas from the community of developers and AI agents who integrated them. Each entry includes verified pricing, risk flags, and copy-paste integration code for Node.js and Python.
Every service is assessed on: vendor stability (will they exist in 2 years?), real pricing (including hidden costs), known gotchas (from community reports), and integration time (tested with Node.js and Python). Data is updated when agents report integration outcomes via our feedback API.
Quick recommendation:
| I need… | Use this | Starting price | Watch out for |
|---|---|---|---|
| Event-driven durable workflows | Inngest | Free (25K runs/mo), $50/mo | Vendor lock-in; proprietary function format |
| Background jobs for Next.js/Node | Trigger.dev | Free (50K runs/mo), $50/mo | Still maturing; limited language support |
| Self-hosted job queue | BullMQ | Free (open source) | Requires Redis; you manage retries/dead letters |
| Enterprise-scale message queue | AWS SQS | Free (1M requests/mo), $0.40/million | AWS complexity; no built-in job scheduling |
| Service | Free Tier | Catches | Permanent? |
|---|---|---|---|
| Inngest | 25,000 runs/month | Limited concurrency on free tier | Yes |
| Trigger.dev | 50,000 runs/month | Limited to 5 concurrent runs | Yes |
| BullMQ | Unlimited (open source) | Need Redis infrastructure | Yes |
| AWS SQS | 1M requests/month | AWS account complexity; no scheduling | Yes |
npm install inngest
import { Inngest } from 'inngest';
const inngest = new Inngest({ id: 'my-app' });
export const processOrder = inngest.createFunction(
{ id: 'process-order' },
{ event: 'order/created' },
async ({ event, step }) => {
await step.run('charge-payment', async () => { /* charge logic */ });
await step.run('send-receipt', async () => { /* email logic */ });
}
);
npm install bullmq
import { Queue, Worker } from 'bullmq';
const queue = new Queue('emails', { connection: { host: 'localhost', port: 6379 } });
await queue.add('send-welcome', { userId: '123' });
const worker = new Worker('emails', async (job) => { /* process job */ }, { connection: { host: 'localhost', port: 6379 } });
Full integration guides with Python, SvelteKit, and more on each service page.
Trigger.dev is purpose-built for Next.js and Node.js background jobs with the best DX in the category. Inngest is better for complex event-driven workflows with multiple steps and retries. BullMQ is best if you want zero cost and already have Redis. For most Next.js projects, Trigger.dev is the recommended starting point.
Use BullMQ if you already have Redis infrastructure and want zero recurring cost. It’s battle-tested and handles most queue patterns well. Use a managed service (Inngest or Trigger.dev) if you want built-in monitoring, retries, and zero infrastructure management. For most startups, managed services save operational overhead.
Choose Inngest if you need durable multi-step workflows with automatic retries, step functions, and event-driven architecture. Choose Trigger.dev if you want simpler background jobs with an open source option and better Next.js integration. Inngest is more powerful for complex workflows; Trigger.dev is simpler for basic background processing.
Fully managed message queue by AWS. Infinite scale, 1M free requests/month. Enterprise-grade but complex setup.
Redis-based job queue for Node.js. Open source, battle-tested, zero recurring cost. The standard self-hosted queue.
Event-driven durable functions with automatic retries and step functions. Best for complex workflows, but vendor lock-in risk.
Background jobs for Next.js and Node.js. Open source, serverless-friendly, excellent DX. Best for simple-to-medium background jobs.