bussinEnterprise-Grade Messaging Tooling
Direct, Browser-Native Azure Service Bus Explorer
Manage, debug, and inspect Azure Service Bus queues, topics, subscriptions, and dead-letter queues (DLQ) with protocol fidelity. bussin runs entirely in your browser using MSAL-delegated Entra ID authentication and direct AMQP-over-WebSockets connections—ensuring strict security with zero intermediary servers or backend proxies.
Instant, zero-install diagnostic console. Save namespace bookmarks and UI preferences in isolated local storage.
Zero-Proxy Web-Native Architecture
Bussin is a specialized client-side Azure Service Bus Explorer built as a Progressive Web App (PWA). It compiles a high-performance .NET WebAssembly runtime paired with a custom TypeScript AMQP 1.0 engine (powered by Rhea). By connecting directly to the Azure Service Bus WebSockets endpoint (`wss://`), it guarantees absolute security boundary integrity.
Decoupled Client Engine
Traditional Service Bus clients rely on heavy desktop runtimes (like .NET WinForms or Electron wrappers) or compromise security with backend HTTP-to-AMQP proxy servers. Bussin resolves this by executing all AMQP connections directly in your browser's sandboxed network layer.
Built for Developers & SREs
Whether debugging live message flows, analyzing message properties, or performing dead-letter triage across multiple environments, Bussin provides a zero-onboarding console for modern DevOps teams.
Zero-Trust Data Boundaries
Because your credentials, Entra ID OAuth tokens, and messaging payloads are processed purely in client-side memory, your telemetry and business data never transit a third-party relay—satisfying compliance and enterprise security policies.
Professional Service Bus Administration Features
Entity Metadata & State Browsing
Inspect comprehensive queue, topic, and subscription metadata, current active/dead-letter message counters, active locks, and partition configurations at a glance.
Deep Message Pattern Search
Scan up to 1,000,000 messages by executing fast, client-side pattern matching across message bodies, sequence numbers, session IDs, custom headers, and dead-letter reasons.
Multi-Tenant & Cross-Tenant Favorites
Pin favorite namespaces across multiple Entra ID tenants, organize them into custom nested folders, and customize UI themes—all stored locally and securely in isolated browser storage.
Non-Blocking Background Workers
Execute massive batch actions, including background purges or deep index scans, utilizing non-blocking worker services that keep the main UI fluid and highly responsive.
Interactive Message Workflows
Peek, publish, receive-and-lock, complete, abandon, defer, and resubmit messages. Manipulate system and user-defined custom properties during manual dead-letter replays.
Direct AMQP 1.0 WebSockets
Bypasses REST API bottlenecks. Establishes native AMQP 1.0 links directly to the Azure Service Bus endpoint over secure WebSockets, supporting transactional locks and credit allocations.
Why Browser-Native Matters
Shifting Azure Service Bus management to a client-side web sandbox provides significant advantages for secure and cross-platform enterprise environments.
- No Installation Friction: Avoid local dependency cycles, native package installations, or administrative approvals. Just navigate to the URL and connect.
- True Cross-Platform Equality: Achieve uniform performance and UI rendering across Windows, macOS, and Linux without native emulation layers or heavy wrappers.
- Entra ID and RBAC Compliance: Respect existing Azure roles (e.g., Azure Service Bus Data Owner, Receiver, Sender) via secure delegated access tokens.
- Enhanced Remote Security: Eliminate connection string dispersion. The app functions entirely as a secure client, storing nothing on external systems.
Azure Service Bus Tooling Comparison
An objective comparison of core developer-facing features across common Service Bus administrative clients.
| Feature Capability | bussin | Azure Portal | Service Bus Explorer (Paolo Salvatori) | VS Code Extension | messentra | purpleexplorer | turbo360 |
|---|---|---|---|---|---|---|---|
| Entra ID Support | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Zero Backend Architecture | ✓ | ✓ | ✓ | ✓ | ✓ | ||
| Cross-Platform | ✓ (Browser/PWA) | ✓ (Browser) | ✓ | ✓ | ✓ | ✓ (Browser) | |
| Mobile Responsive UI | ✓ (Fully responsive) | (Clunky blades) | (Desktop portal) | ||||
| No Install Required | ✓ | ✓ | ✓ | ||||
| Discovery of Namespaces | ✓ | ✓ | ✓ | ||||
| Favorites with Custom Folders | ✓ | ✓ | ✓ | ||||
| Statistics View | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
| Deep Search | ✓ | ✓ (Downloaded only) | ✓ (Downloaded only) | ✓ | |||
| Reverse Peek | ✓ | ||||||
| Batch Send | ✓ | ✓ | ✓ | ||||
| Background Tasks | ✓ | ✓ (Server-side) | |||||
| Easy DLQ Move / Resubmit | ✓ | ✓ (Requires setup) | ✓ | ✓ | ✓ | ||
| Free to Use | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Comparison is based on typical developer usage profiles and public specifications. Standard features are continually updated; evaluate tools according to your enterprise security boundaries.
Product Walkthrough
Primary Use Cases
- Secure Hot-Fix Triage: Safely inspect and edit problematic messages in production queues using client-side Entra ID permissions.
- Dead-Letter Analysis & Replay: Browse failed messages in the DLQ, isolate failure reasons, edit headers, and resubmit them safely with background concurrency limits.
- Cross-Platform Infrastructure Diagnostics: Ensure Linux, Mac, and Windows engineering environments share identical access to diagnostic tooling.
- Namespace Subscription Audit: Validate active topic filters, verify SQL/correlation routing behaviors, and confirm message arrival on topic subscriptions.
Frequently Asked Questions
Does bussin transit or persist my message data?
Absolutely not. Bussin operates strictly on a zero-proxy, zero-trust architecture. There are no intermediate servers or backend relays. MSAL.js secures delegated tokens inside your browser sandbox, and the TypeScript AMQP client opens WebSocket tunnels directly to standard Azure endpoints. Your messages, SAS keys, and credentials never leave your browser context.
Do I need to deploy server components or agents?
No. Bussin is compiled to run as a static Single Page Application (SPA). The app can be accessed directly online or cached as a local Progressive Web App (PWA) for completely offline load capabilities.
How does authentication integrate with Entra ID?
Bussin integrates directly with standard Microsoft identity providers via PKCE-flow OAuth 2.0. It acquires delegated scopes (specifically `https://servicebus.azure.net/user_impersonation` and ARM directory management), respecting your native Azure RBAC roles. If you do not have permission in Azure Active Directory, the browser connection is rejected at the broker plane.
Does this support macOS and Linux environments?
Yes. By utilizing standard HTML5 WebSockets and WebAssembly, Bussin runs perfectly on standard browser engines across macOS, Linux, and Windows, offering an instant cross-platform solution to traditional desktop tool fragmentation.
Open Bussin App
Inspect and manage your Azure Service Bus namespaces immediately, secure in your browser environment.