Inspect, manage, and move messages across Azure Service Bus and AWS SQS — from a single native window. Edit entity properties, resubmit dead-letters in bulk, round-trip messages through JSON or CSV.
Connect to as many Azure Service Bus namespaces and AWS SQS accounts as you like. Each shows up as a branch in a single tree, so switching between brokers takes zero context-switching.
Peek non-destructively, then create or edit queues, topics, and subscriptions — TTL, lock duration, max delivery count, forwarding, redrive policy. Destructive actions always confirm.
Built on .NET MAUI with native UI on Windows and macOS. No Electron, no browser-in-a-window. Starts in under a second on a four-year-old laptop.
Bulk-resubmit dead-letters at 2 a.m. without writing a script or paging an Azure admin. Connection profiles live in your OS keychain, not a shared password manager.
Export a message to JSON, edit it, re-import into your dev queue. Schedule sends. Test subscription rules without redeploying.
Inspect SQL and correlation filters on Service Bus subscriptions. See exactly which subscription a sample message lands on. Catch broken topology before it ships.
Full support for queues, topics, subscriptions, sessions, and dead-letter sub-queues. Connect via connection string or Microsoft Entra ID.
Standard and FIFO queues, dead-letter inspection, batch operations. Authenticate via access keys.
More brokers planned. Tell us which one.
Browse messages with their full payload, headers, and custom properties — without consuming them from the queue.
Create queues, topics, and subscriptions; edit TTL, lock duration, max delivery count, auto-forwarding, dead-lettering on expiration, and SQS redrive policy — without opening the portal.
Resend a message to its origin queue, a different queue, or another namespace entirely. Bulk-select or single-shot.
Every queue and subscription exposes its dead-letter sub-queue inline. Bulk-resubmit to origin, or purge. Dead-letter reason and description are columns, not buried.
Save selected messages as JSON or CSV, edit locally, import back into any queue — same broker, another broker, or across clouds.
Send new messages with full headers, custom properties, session IDs, and content type. Schedule for a future enqueue time on Service Bus.
Browse sessioned queues with full session iteration. Group messages by session ID; resubmit in order. FIFO message-group IDs handled the same way.
Real-time grid filter on sequence number, label, content type, session/correlation ID, dead-letter reason, custom properties, or substring across the payload.
Create and edit SQL filters and correlation filters on Azure Service Bus subscriptions. Catch routing mistakes before deploy.
Remove individual messages or whole batches. Explicit confirmation for destructive actions — nothing dangerous happens silently.
Server-side batched fetching and virtualized grid keep the UI responsive on queues with thousands of messages and many namespaces in the tree.
Zero analytics or phone-home. Connection strings live in the OS keychain (Credential Manager / Keychain). Your queues are nobody else's business.
Honest side-by-side against the tools developers usually reach for. Spot a mistake? Tell us — we update this table monthly.
| QueuePeek | Service Bus Explorer |
Azure Portal | Cerebrata | Turbo360 | QueueExplorer | |
|---|---|---|---|---|---|---|
| Azure Service Bus | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| AWS SQS (Standard + FIFO) | ✓ | — | — | — | — | — |
| Native Windows app | ✓ | ✓ | Web only | ✓ | Web only | ✓ |
| Native macOS app | ✓ | — | Web only | ✓ | Web only | Beta |
| Create / edit queues, topics, subscriptions | ✓ | ✓ | ✓ | ✓ | ✓ | Partial |
| Edit entity properties (TTL, lock, redrive…) | ✓ | ✓ | ✓ | ✓ | ✓ | Partial |
| Peek without consuming | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Bulk resubmit from DLQ | ✓ | Partial | — | ✓ | ✓ | ✓ |
| Copy / move messages between queues | ✓ | Partial | — | ✓ | ✓ | ✓ |
| Schedule send (Service Bus) | ✓ | ✓ | — | ✓ | ✓ | ✓ |
| Bulk export / import (JSON + CSV) | ✓ | Partial | — | Partial | Partial | ✓ |
| Subscription rule editing (SQL + Correlation) | ✓ | ✓ | ✓ | ✓ | ✓ | Partial |
| Session-aware browsing | ✓ | ✓ | Limited | ✓ | ✓ | ✓ |
| Microsoft Entra ID auth | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Credentials in OS keychain | ✓ | Plain text | n/a | ✓ | n/a | Plain text |
| Zero telemetry | ✓ | ✓ | — | — | — | ✓ |
| Cost | Paid 30-day trial | Free | Free (Azure cost) | Paid | Paid SaaS | Paid |
Last verified June 2026. Comparison points reflect each product's then-published feature set; not affiliated with any of the tools listed.
Each platform follows its own store conventions — a one-time purchase on Windows, a subscription on Mac. Whichever you pick, connection strings stay in your OS keychain and the app makes no outbound traffic except to the brokers you connect to. See the privacy policy.
Want something prioritised? Drop a note — feature requests with a real use case attached jump the queue.
QueuePeek is a native desktop application for inspecting and managing messages on message brokers — think of it as the equivalent of a database admin tool, but for message queues. It currently supports Azure Service Bus and AWS SQS.
Pricing follows each store's own conventions:
Both come with a 30-day free trial — the full app, no feature gates. No account, no email signup, no card details required to start the trial.
Install from your store of choice — Microsoft Store on Windows, Mac App Store on Mac — and you get 30 days of the full app, every feature, no banners, no upsell prompts. After 30 days the app shows a quiet status in the About dialog and the trial ends. No account, no email signup, no card details required to start.
Honest answer: it pays for full-time maintenance, native builds on Windows and macOS, App Store and Microsoft Store fees, and an explicit no-telemetry commitment. We'd rather charge a fair price once than monetise your data.
The free trial gives you a month to decide whether it's worth it before paying.
Azure Service Bus and AWS SQS as of v1.3. RabbitMQ, Apache Kafka, and GCP Pub/Sub are on the roadmap — let us know which one you'd want first.
Yes. Create, edit, and delete queues, topics, and subscriptions. Edit max delivery count, lock duration, message TTL, auto-forwarding, dead-lettering on expiration, duplicate detection windows, and SQS redrive policy. You can also create and edit SQL and correlation filter rules on subscriptions.
The Azure Portal is a web UI for managing Service Bus resources. It can do most things, but slowly — you click through three or four panes to inspect one message, and there's no way to peek across multiple namespaces or across SQS.
QueuePeek is a desktop app optimised for the read/inspect/act loop: a single tree across all your namespaces and accounts (Azure and AWS, side by side), bulk operations, JSON/CSV round-trip, entity-property editing, and dead-letter as a first-class concept. It's the tool you reach for when you actually need to fix something.
Not yet — it's the top item in the v1.4 roadmap. Today, Azure Service Bus authenticates via connection string or Microsoft Entra ID interactive sign-in. AWS SQS uses IAM access keys.
No. No analytics, no error reporting, no phone-home of any kind. The only network traffic the app makes is to the brokers you've explicitly connected to. See the privacy policy for specifics.
In the operating system's secure credential store — Windows Credential Manager on Windows, macOS Keychain on Mac. They never leave your machine and are never written to plaintext config files.
Native build for Windows 10/11 (x64 and arm64) on the Microsoft Store, and macOS 13+ (universal Apple Silicon & Intel) on the Mac App Store.
Not currently. If you'd use one, let us know — Flatpak and AppImage are on the "considering" list and demand signal is what will tip the decision.
Yes. Select any number of messages and export to JSON or CSV with their full payload, headers, and custom properties. Re-import into the same queue, a different queue, or even a different broker. Useful for backups, reproducers, and migrations.