The management UI that ships with RabbitMQ can peek at a few messages and move a whole queue, and that is where most teams stop. When a dead-letter queue holds 3,000 messages from four different bugs, you want to see why each one died, send back only the ones you fixed, and know afterwards who did what. A handful of tools exist for that. They split into two camps: desktop apps for one developer, and self-hosted servers for a team. Here is how they compare. I build one of them, Warren, so read the table with that in mind; everything about the others is taken from their own pages, checked on 12 October 2026.
| Runs as | Price | Dead letters | Roles, audit log | Alerts | |
|---|---|---|---|---|---|
| RabbitGUI | desktop app | €45 once | browse, republish to the original queue, throttle | no | no |
| QueueExplorer | desktop app | Standard and Professional editions | browse, move or copy, edit | no | no |
| HZN Queue Console | desktop app, web on a custom licence | paid, 14-day trial | browse, one click back to the source queue, edit | no | no |
| QueueLens | self-hosted web, MIT | free | browse, copy or move, park, dry run | yes | in-app; email, Slack, PagerDuty experimental |
| Qarote | cloud or self-hosted, MIT core | core free, Cloud $99 a month billed yearly | no message browsing | on paid plans | yes |
| Warren | self-hosted web, closed source | Community free for one broker | browse grouped by failure, replay to the original route, canary, undo | audit log in every edition, roles from Team | Team and Pro |
RabbitGUI calls itself the RabbitMQ IDE for developers. It is the cheapest paid option, a one-time €45, and covers the dead-letter basics well: search and filter messages, select some or all, and republish them to their original queue or anywhere else, with throttling. Credentials stay encrypted on your machine. If you are the one developer who handles dead letters, it is hard to beat on price.
QueueExplorer has been on the market the longest and treats messages "like files": copy, move, back up to disk, edit, and see why a message was dead-lettered. The Professional edition adds XPath, JSON and regex extraction. It suits someone who works with many message formats and wants a mature desktop tool.
HZN Queue Console also speaks ActiveMQ Classic and Artemis, and validates messages against AsyncAPI schemas. For dead letters it has a one-click move back to the source queue and lets you change payload or headers on the way. A custom licence allows a web deployment.
What all three share: they run on one person's machine with that person's broker credentials. There is no record of who replayed what, no roles, and nothing that wakes someone when a dead-letter queue starts filling.
QueueLens is the closest to Warren in approach: a self-hosted web app, MIT-licensed, with Viewer, Operator and Admin roles, an audit log, a mandatory dry run before bulk actions, a parking queue, field masking, and it refuses to browse quorum queues with a delivery limit, where every requeue would count. It started in July 2026 and is young; alert delivery outside the app is marked experimental. If open source is a requirement, look here first.
Qarote is a monitoring tool rather than a dead-letter tool. It reads the management API's metrics, detects incidents such as lost consumers or stalled acks, scans the configuration for anti-patterns like queues without a dead-letter exchange, and exposes all of it to AI agents through an MCP server. Its page says it never stores message payloads, and it does not offer browsing or replay. It pairs with a dead-letter tool rather than replacing one.
Warren is a self-hosted console for the dead-letter side: it reads every dead-letter queue of a broker, groups the messages by exception and death reason across queues, tells each message's story from x-death and from Spring and MassTransit error headers, and replays a selection to its original exchange and routing key with publisher confirms. Bulk actions take a dry run first, a canary can go before the rest, a replayed message that dies again is found and counted against its replay, and discards and purges can be undone from the audit log. Team and Pro add roles, alert rules and Prometheus metrics. It is closed source; the Community edition is free for one broker.
For moving messages between queues once, a shovel or a short script with publisher confirms is enough, and the management UI covers a peek at a few messages. Two earlier articles go through those options: moving messages with shovel, rabbitmqadmin and friends and what the management UI can do with dead letters. To understand one message, paste it into the free x-death decoder.