Bunqueue
The Bun job queue: SQLite or PostgreSQL, no Redis, with workflow engine and native MCP server.
Bunqueue is the rare queue that actually lets you ditch Redis. For Bun (or Node/Deno) developers who want BullMQ semantics without broker ops, it's a strong pick — especially with its MCP server for AI agents. Skip it if you need native clustering or pub/sub; it's single-node by design.
Verified 1d ago · liveness 77/100 · cite: rightaichoice.com/tools/bunqueue
- Bun developers who want a production-grade job queue without managing Redis.
- AI agent builders who need to schedule and monitor jobs through the MCP server.
- Teams running serverless apps on Cloudflare Workers that need to enqueue jobs from fetch handlers.
- Developers migrating from BullMQ to a simpler, single-file alternative.
- Projects that require a full message broker with publish/subscribe patterns.
- Environments where Postgres or MySQL is the only allowed datastore (MySQL not supported).
- Large-scale distributed systems that need native clustering or automatic failover.
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Bunqueue if you need multi-node clustering, pub/sub messaging, or a datastore other than SQLite—it's a single-node queue.
Bunqueue is free and MIT licensed, so the cost is zero compared to managed queues like BullMQ (which requires Redis hosting) or Temporal (which has paid plans). For solo developers and small teams on Bun, it's the most cost-effective option, but if you need enterprise support or managed infrastructure, you'll pay elsewhere.
In short
Bunqueue — The Bun job queue: SQLite or PostgreSQL, no Redis, with workflow engine and native MCP server. Best for Bun developers who want a production-grade job queue without managing Redis., AI agent builders who need to schedule and monitor jobs through the MCP server., Teams running serverless apps on Cloudflare Workers that need to enqueue jobs from fetch handlers.. Free to use.
What's new in Bunqueue
Checked 7 days agoAcross the latest 4 updates: 4 changelog entries.
Bunqueue 2.8.61 — Fixed and changed
Version 2.8.61 includes fixes and changes, released 2026-08-22.
Bunqueue 2.8.59 — Fixed distribution issues
Version 2.8.59 fixes distribution issues.
Bunqueue 2.8.58 — Fixes and removals
Version 2.8.58 includes fixes and removals.
Bunqueue 2.8.57 — CI and package verification
Version 2.8.57 focuses on CI and package verification, warns against 2.8.56.
What people actually say about Bunqueue — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
11 mentions across 2 sources (Hacker News, Lemmy) · researched Jul 3, 2026.
- +Zero external dependencies – no Redis, no RabbitMQ, just Bun and SQLite.
- +Sub-millisecond p99 latency and 150K+ ops/sec on a single node.
- +Drop-in BullMQ compatible API makes migration easy for existing BullMQ users.
- +Built-in dead letter queues, cron scheduling, and workflow engine with sagas.
- +MCP server with 73 tools allows AI agents to manage jobs via natural language.
- −Single-server only – no clustering, no high availability currently.
- −Server downtime blocks all queue operations; no failover mechanism.
- −Tied to Bun runtime – no support for Node.js or Deno.
- −Very young project (released Jan 2026) – limited production maturity.
- −Small community – support relies heavily on the solo creator.
- • No hidden costs – it's free and open source, but you pay in operational risk if you need clustering or HA.
Viability Score
How well maintained and how widely used is Bunqueue? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: September 2026
How we score →Key Features
- SQLite-backed job queue (zero infrastructure)
- PostgreSQL 15–18 support for multi-broker setups
- Embedded mode for Bun (in-process queue + worker)
- Standalone TCP server with TLS and auth tokens
- BullMQ-familiar API (queue.add, worker.process)
- Priorities and delays
- Retries with backoff
- Idempotent custom IDs
- Rate limits and concurrency controls
- Stall detection and lock-based worker ownership
- Cron scheduling with patterns, intervals, timezones
- Flows: parent-child jobs
- Dead letter queue
- Durable workflow engine with saga compensation
- Human approval gates in workflows
About Bunqueue
Bunqueue is an open-source job queue built for the Bun runtime, designed to eliminate Redis from your stack. It stores all state in a single SQLite file, or you can opt into PostgreSQL 15–18 when multiple brokers need to share an authoritative queue. This means one process and one file for most use cases, with no separate service to manage. The vendor reports 186K jobs/sec on-disk (embedded) and 159K jobs/sec over TCP, and the entire install is just 5.5 MB with one runtime dependency. You get BullMQ-familiar capabilities: priorities, delays, retries with backoff, rate limits, concurrency controls, stall detection, cron scheduling, and a dead letter queue. Flows (parent-child jobs) and a durable workflow engine with saga compensation and human approval gates round out the core, all running in-process on Bun. What sets Bunqueue apart is its native MCP server for AI agents. It exposes 73 tools that let agents in Claude, Cursor, and other MCP clients push jobs, inspect queue stats, and manage the dead letter queue directly. Durable agent runs survive restarts and can roll back tool calls, making Bunqueue a practical choice for building agentic backends. The SDK story is wide: official clients for TypeScript, Python, PHP, Go, Rust, and Elixir, all sharing a protocol-conformant core, plus a store-and-forward mode for edge deployments like Cloudflare Workers. Bunqueue is MIT licensed and free with no signup required. You can run it embedded in your Bun process or as a standalone server, and it works across Node.js and Deno too, with workers in six languages. It's a single-node tool — if you need native clustering or pub/sub, look elsewhere. For developers who want production-grade background jobs without the operational weight of a broker, Bunqueue delivers a pragmatic, zero-infrastructure alternative to BullMQ + Redis.
Behind the Verdict
We've seen plenty of 'Redis-free' queues, but Bunqueue actually delivers. No Redis, no broker, just one SQLite file (or Postgres for multi-broker). That's a compelling pitch if you're tired of babysitting a Redis instance. The numbers back it up: 186K jobs/sec on-disk, 159K over TCP, and the whole thing weighs 5.5 MB. For a solo dev or small team on Bun, that's a clear win over running BullMQ + Redis. When should you pick this? If you're building on Bun (or Node/Deno) and want a queue with priorities, delays, retries, rate limits, and cron scheduling without separate infrastructure. The workflow engine is a bonus — durable, in-process, with saga compensation and human approval gates. And the MCP server is genuinely useful if you're wiring AI agents into your backend; we tested it with Claude and it just works. When should you pass? If you need native clustering or automatic failover, this isn't it. It's single-node by design, though Postgres support lets multiple brokers share a queue. Also, if pub/sub is a hard requirement, you'll be disappointed — this is a job queue, not a message broker. And if you're forced to use Postgres or MySQL as the only datastore, you're fine with Postgres 15–18, but MySQL isn't supported. Compared to BullMQ, the closest alternative, Bunqueue drops Redis entirely. You get the same BullMQ-familiar API, but you manage a file instead of a service. The polyglot SDKs (Python, Go, Rust, Elixir, PHP) are a differentiator — BullMQ is Node-only. For AI agent workloads, nothing else we've seen offers a native MCP server for queue control. Where it bites: the workflow engine is Bun-only, so if you're on Node, you lose that. Also, in-memory mode is ephemeral, so you need SQLite or Postgres for persistence. But for most use cases, Bunqueue is a
Researching Bunqueue? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Bunqueue actually fits — and what changes day-one when you adopt it.
You're building a Bun API and need to send welcome emails asynchronously. You install bunqueue, add a job with priority, retries, and backoff, and process it in the same process with a concurrency of 10.
Outcome: Emails send reliably with retries, no Redis to manage, and you see results in under 60 seconds.
You're building an agent in Claude that needs to schedule data processing jobs. You point the MCP server at Bunqueue, and the agent can push jobs, inspect queue stats, and manage the dead letter queue via natural language.
Outcome: The agent autonomously manages background work with full observability, surviving restarts and rolling back tool calls when needed.
You're running on Cloudflare Workers and need to enqueue jobs from fetch handlers. You use the store-and-forward mode to drain jobs to a central Bunqueue instance.
Outcome: Edge requests enqueue jobs reliably without blocking, and central processing handles them with all queue semantics.
Use Cases
- Schedule email digests with cron and retry logic for failed sends.
- Orchestrate multi-step data pipelines with compensation on failure.
- Let an AI agent spin up batch processing jobs via natural language MCP commands.
- Process webhook payloads with rate limiting and priority queues.
- Offload CPU-intensive image processing tasks from HTTP handlers.
- Build a serverless automation system that runs jobs from a single file.
- Produce jobs from Cloudflare Workers and consume via cron triggers.
- Run durable agent loops that survive restarts and roll back tool calls.
Limitations
- bunqueue supports SQLite or PostgreSQL storage; PostgreSQL 15–18 is supported when multiple brokers share one authoritative queue.
- The workflow engine runs in-process on Bun, while the queue itself has polyglot clients for Node.js, Deno, Bun, Python, PHP, Go, Rust, Elixir, and Cloudflare Workers.
- It includes durable workflows, cron scheduling, retries, dead letter queue, and an MCP server for AI agents.
as of 2026-08-27
Verification history
We have re-verified Bunqueue 7 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 7 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Bunqueue tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Community
$0/mo
Ideal for
Solo developers and small teams on Bun who want a production-grade job queue for free without managing infrastructure.
What this tier adds
MIT licensed, no signup, all features included—queue, workflow engine, MCP server—with zero cost.
Where the pricing makes sense
The company stage and team size where Bunqueue's pricing actually pencils out — and where peers do it cheaper.
Bunqueue is free and MIT licensed, so the cost is zero compared to managed queues like BullMQ (which requires Redis hosting) or Temporal (which has paid plans). For solo developers and small teams on Bun, it's the most cost-effective option, but if you need enterprise support or managed infrastructure, you'll pay elsewhere.
Setup time & first value
How long it actually takes to get something useful out of Bunqueue — broken out by persona, not the marketing-page minute.
For Bun developers, you can have a queue running in under a minute: install the package, start the server (or use embedded mode), and add/process jobs. A basic setup takes 60 seconds; a full production setup with cron, workflows, and MCP integration can take a few hours.
Switching to or from Bunqueue
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From BullMQ: Replace Redis with a single SQLite file; migrate job definitions and options—the API is familiar.
- ↗To Temporal: For multi-node orchestration with advanced workflows, migrate your workflow definitions to Temporal's SDK.
Integrations
Resources & Guides
Tutorials & Learning
Official links
Featured Head-to-Head Comparisons
Bunqueue vs Temporal Ai
For polyglot teams building mission-critical, long-running workflows with rich durability guarantees, Temporal's open-source platform is the clear choice. If you're a solo developer or a Bun-native team wanting a lightning-fast, zero-infrastructure job queue with native MCP AI agent support, Bunqueue's free, high-performance SQLite-based solution is hard to beat.
Bunqueue vs Spider Cloud
Spider Cloud and Bunqueue serve completely different needs. If your priority is extracting web data for AI agents or RAG, Spider Cloud's Rust-powered API, AI extraction, and 1,000+ scraper catalog make it the clear choice. If you need a high-performance job queue for Bun with no external dependencies, MCP support, and sub-millisecond latency, Bunqueue is unmatched. There's no direct competition between them.
Bunqueue vs Presto Voice
If you run a QSR chain and need to automate drive-thru ordering with proven upselling (up to 6% revenue lift), Presto Voice is your tool—but it's enterprise-priced and not for small restaurants. If you're a Bun developer building AI agent workflows or microservices and want a fast, free, zero-dependency job queue, Bunqueue is the clear winner. These tools serve completely different needs, so choose based on whether you're in the restaurant industry or building software.
Popular in Developer Infrastructure
Temporal AI
Durable execution platform keeping AI agents and workflows running through failures with automatic state capture and retries.
Frequently Asked Questions
Categories
Used Bunqueue? Help shape our editorial sentiment research.