QueueForge
A self-hosted dashboard that watches your RabbitMQ or Kafka dead-letter queues, alerts you when messages start piling up there, and lets you replay or fix them without writing a one-off script.
🔗 Visit QueueForge
Description
When a message queue system like RabbitMQ or Kafka can't process a message — a malformed payload, a downstream service that's down, a bug in a consumer — it typically gets shoved into a dead-letter queue (DLQ) rather than lost outright. The problem is that DLQs are easy to forget about: nothing breaks loudly when messages pile up there, they just quietly accumulate until someone notices a customer's order never processed, or a webhook never fired, days later.
QueueForge is built to close that blind spot. It's a self-hosted platform that continuously monitors DLQs across RabbitMQ and Kafka, alerts the team the moment messages start landing there, and provides recovery workflows — including replaying failed messages back through the pipeline — instead of requiring an engineer to write a custom script under pressure at 2am. It supports unlimited clusters on every plan, with a 6-day free trial and paid tiers at $9/month or $90/year (a modest discount for annual billing), both of which unlock the full feature set with no per-message or per-queue metering.
💬 Our review
The short version: QueueForge solves a specific, well-understood operational pain — DLQs are a known weak point in message-queue-based systems, and most teams either build brittle internal tooling for this or simply don't monitor it at all until something breaks visibly.
At $9/month with unlimited clusters and no per-message charges, the pricing is aggressively simple and cheap relative to the cost of even one missed failed-message incident in production — this isn't the kind of tool where usage-based pricing punishes you for having a busy queue, which is a real advantage over more enterprise-y observability platforms that meter by event volume. The trade-off is that it's not open source, so you're trusting a small, single-purpose vendor with visibility into your messaging infrastructure, and being self-hosted still means you're the one running and securing the deployment (it isn't a fully managed SaaS). Worth adopting if your team runs RabbitMQ or Kafka in production and currently has no dedicated DLQ visibility — which, realistically, describes a lot of teams; overkill if you're running message queues at hobby scale where occasional manual inspection is fine.
💰 Pricing
📊 Global score
🤖 AI-enriched data
Essai gratuit 6 jours, puis 9$/mois ou 90$/an, fonctionnalités complètes et clusters illimités sur tous les plans
Pros
Prix simple et bas (9$/mois), pas de facturation au message
Clusters illimités sur tous les plans
Couvre à la fois RabbitMQ et Kafka
Workflows de recovery (replay) intégrés, pas de script à écrire en urgence
Cons
Pas open source
Self-hosted = c'est vous qui déployez et sécurisez, pas un SaaS pleinement managé
Outil de niche récent, jeune vis-à-vis des plateformes d'observabilité généralistes