Free · Version 1.1 · Windows 10 and 11

The explorer for your queues and storage

Sign in with Microsoft Entra ID and open the namespaces and storage accounts you can see in Azure, with your roles and no key to copy. Browse queues, topics, blobs and tables, peek, search and replay messages, clean up dead letters, and run local Service Bus brokers on your PC. Free, with no account.

  • Azure Service Bus
  • Azure Queue Storage
  • Azure Storage
  • RabbitMQ 4
  • ActiveMQ Classic
  • Apache Artemis
The start page of Busrider 1.1: what your Azure account sees and you haven’t saved yet, local Service Bus brokers, and every broker in one list. Sample data.

Azure, signed in with Microsoft Entra ID

Sign in with your work or school account: Busrider finds the Service Bus namespaces and storage accounts you can see in Azure, with what your roles allow on each. Open one, or save several at once. No key to copy from the portal, none stored.

  • Microsoft’s own sign-in page, in your browser: multi-factor authentication and Conditional Access work, and Busrider never sees your password.
  • Every directory you belong to, by subscription, guest ones included. One that asks for MFA waits, locked, until you sign in to it.
  • Your Azure roles respected: what they don’t allow is greyed, with the role to ask for, such as Azure Service Bus Data Sender.
  • Your sign-in stays on this PC, encrypted with your Windows account. Busrider talks to Azure directly, as you, and only reads Azure Resource Manager, to find what you can see.

The first time, Microsoft asks you, or your organisation’s administrator, to allow Busrider. Connection strings and SAS URLs still work, side by side.

Every broker in the same window

The same screens for each broker, one tab per connection. What a broker can’t do is left out, not faked.

Azure Service Bus

Queues, topics, subscriptions and their rules.

Connect with
Microsoft Entra ID, or a connection string encrypted on your PC
Dead letters
The dead-letter sub-queue
Purge
Everything, or a period

Azure Queue Storage

Beta

The queues of a storage account, with Base64 bodies decoded.

Connect with
Microsoft Entra ID, a connection string or a SAS URL, or Azurite
Dead letters
Azure Functions’ failure queue, shown as the queue’s Dead-letter tab
Purge
Everything

Azure shows the first 32 visible messages without taking them. To read further, Busrider asks first, then receives them and gives them back: each counts one more read.

RabbitMQ 4

Beta

Queues, exchanges and bindings.

Connect with
Management URL, AMQP URL, user and password
Dead letters
The queue bound to the dead-letter exchange
Purge
All ready messages

Reading a classic or quorum queue takes its messages for a moment, so Busrider asks before the first read. Streams are read in place.

ActiveMQ Classic

Beta

Queues and topics, read over AMQP 1.0.

Connect with
AMQP 1.0 URL, user and password; Jolokia URL optional
Dead letters
This queue’s share of ActiveMQ.DLQ
Purge
Everything, or a period of sender dates

Apache Artemis

Beta

Addresses and their queues, read over AMQP 1.0.

Connect with
AMQP 1.0 URL, user and password; Jolokia URL optional
Dead letters
This queue’s share of the dead-letter address
Purge
Everything, or a period of sender dates

Beta, as in the app: support for these brokers is new. Azure Service Bus is the one Busrider started with.

Azure Storage: search every blob, read its JSON

Find a blob anywhere in a storage account, by its name or by what it holds, and read it formatted right away. Blobs, tables and queues in one tab, with your environment’s rules.

  • Search the whole account at once: by name and path (*.json, order-), by text inside the blobs ("REFUNDED") or with a /regex/, narrowed by container, type, date, size or metadata. Each match shows its line.
  • Open a result and its JSON is there, formatted as a tree you can fold; PDFs page by page. Edit opens it at the matching line.
  • Edit a text blob in place: saved only if nobody changed it meanwhile, the version replaced kept as a snapshot if you ask. Diff, versions and metadata.
  • Containers read folder by folder, files dropped to upload them; tables with their types and a query written as a sentence or in OData; the account’s queues in the same tree.

Connect with Microsoft Entra ID, a connection string, a SAS URL or Azurite. Edits and deletes act on your real data: an environment set to Read only locks them.

Local brokers, one click away

Run an Azure Service Bus namespace on your PC, created from the start page: empty, copied from a saved connection, or from a definition file. Your app connects with a local connection string. No Docker, no Azure bill.

  • Started and stopped by Busrider, or kept running when it closes. Messages and entities stay on disk between runs.
  • Copies the queues, topics, subscriptions and rules of a saved Service Bus connection, and up to 100 messages per queue if you ask, never from a PROD connection.
  • Listens on this computer only (127.0.0.1), unless you open it to Docker containers and other computers.
  • Extra keys with Send, Listen or Manage rights, to test your app’s rights before deploying.

Free, with no account. Local brokers run on Busrider’s own emulator, made for development and tests: it is not Microsoft’s emulator, nor Azure.

Everything for a day spent with queues

All of it is free, on every broker, with no account.

Saved connections

Sign in with Microsoft Entra ID, or paste a connection string or a broker’s address, pin the connections you use most and connect in one click. Several at once, one tab each, even to different brokers. Keys and passwords are encrypted with your Windows account.

Browse, peek, search and live

Queues and topics stream in with their counts. Read messages page by page, all at once or live; search ids, labels, bodies and properties, and filter by date.

Send and act in bulk

Write a message with what its destination asks for, send it again or several times. Edit and resend one, or check several to resubmit, move to dead-letter, delete or export them.

Purge, all or a period

Empty a queue or its dead letters, entirely or only the messages of a period where the broker dates them (on RabbitMQ, all ready messages; on Azure Queue Storage, the whole queue). Progress and Cancel in the status bar.

Entities, rules and configuration

Create, edit, duplicate and delete queues, topics, subscriptions, exchanges and bindings, and subscription filters. Export a namespace’s configuration and import it into another.

A receipt for every action

A purge, a bulk action or a resend ends with a receipt: what was done, where, and the counts before and after, read again from the broker.

Activity

Waiting messages by the hour or by the day, with the oldest message and the busiest hour.

Environments that protect

Tag connections PROD, DEV or an environment of your own, such as REC, with its colour on the tab. Each one sets what Busrider may change there: read only, messages, or messages and entities. On PROD, a purge, a delete, a resubmit or a move to dead-letter asks you to type the entity’s name first.

AI assistants, on your terms

Turn on Settings › AI assistants, and Claude, Codex, Antigravity or another MCP client works with your brokers through Busrider. Off until you turn it on, and free.

They read what you allow

Queues, topics and subscriptions with their counts, settings and rules, messages peeked or searched, dead letters grouped by reason. Each environment, and each connection, says whether assistants may read, ask for changes, or nothing.

PROD stays locked

Production connections stay locked until you unlock one, read-only, for 15 minutes, an hour or until Busrider closes, with or without message content.

You approve every change

A send, a resubmit, a delete or a purge an assistant asks for waits for your approval in Busrider, described from what Busrider read, not from the assistant’s words.

Local brokers on demand

An assistant can create, start, stop and restart your local brokers and read their log. Emptying one waits for your approval; deleting one is left to you.

Never your keys

Assistants get connection names, never connection strings, keys or passwords. They reach Busrider on your PC only, with a key other Windows accounts can’t read.

Every request logged

Settings › AI assistants › Activity keeps each request for 30 days on your PC, without message content. Pause, or stop all AI access, in one click.

What an assistant reads goes to its provider’s AI service, under that provider’s terms: see the privacy policy.

What stays on your machine

Busrider talks straight to your brokers and to Azure. Nothing about them goes through us.

Read the privacy policy
  • Connection strings and passwords

    Encrypted with your Windows account. They never leave the app.

  • Your Azure sign-in

    Done with Microsoft, in your browser. Busrider keeps its tokens on your PC, encrypted with your Windows account, and talks to Azure directly.

  • Messages, blobs and names

    Only exchanged between the app and your brokers or storage accounts. An error report you send hides the names of your connections, queues and hosts, and your user names, unless you choose to show them.

  • Feedback, votes and ratings

    Sent only from Feedback & roadmap, with a random number for this installation, and read only by us.

  • Update check

    At start and every 6 hours, Busrider asks our server which versions are current. It sends only where it was installed from, with no identifier.

  • Usage and error statistics

    Feature counts and error codes, sent only if you agree: Busrider asks at first start. No cookie, no lasting identifier. Settings › Privacy has a switch for each.

Security and the GDPR

Facts rather than labels: what is in place in version 1.1.

A locked-down app

Busrider opens production namespaces and storage accounts, so its own security comes first.

  • The window runs in a sandbox, with no direct access to your system, under a strict content security policy.
  • Camera, microphone and location are refused, and the released app has no developer tools.
  • A message or a blob is shown, never run, whatever it contains.
  • What an environment locks, the app’s core refuses too, not just its buttons.
  • Signing in with Microsoft happens in your browser: Busrider never sees your password.
  • Busrider stays on a supported version of Electron, and its libraries are watched for known flaws.

The GDPR, by keeping little

Busrider is built to need almost nothing about you.

  • No Busrider account, and nothing from your brokers or Azure: no message, no blob, no queue name, no connection string, no sign-in.
  • Statistics are sent only if you agree, to Aptabase in the EU, with no lasting identifier.
  • Feedback, votes and ratings are hosted in the EU, in Ireland, and kept for a limited time: 24 months for feedback and ratings.
  • Your brokers’ and storage accounts’ data stays yours: we never receive it, so we never process it for you.
  • To see or delete what we hold about you, write to [email protected].

Flaws found, flaws fixed

How a vulnerability is handled, and how its fix reaches you.

  • A security contact, and a reply within 3 working days.
  • A bill of materials (SBOM) with every version, listing what Busrider is built from.
  • Automatic alerts on the libraries Busrider is built from.
  • Security updates through the Microsoft Store, and a version with a security issue asks to be updated.

Found a vulnerability? Write to [email protected], and please keep it private until a fix is out. How we handle it.

Install it your way

From the Microsoft Store, or from a terminal with winget. Either way you get the Store version, and the Store keeps it up to date.

Get it from Microsoft Store

winget install --id 9NP026NQZQ2M

winget comes with Windows 11 and recent versions of Windows 10. It shows the Store’s terms once: type Y to accept them.

Frequently asked questions

Is Busrider free?

Yes. Busrider is free to download from the Microsoft Store and free to use, on every broker, with no account: signing in with Microsoft Entra ID, local brokers and AI assistants included.

Which brokers does it work with?

Azure Service Bus (plus local Service Bus brokers on your PC), Azure Queue Storage, the blobs and tables of Azure Storage, RabbitMQ 4, ActiveMQ Classic and Apache Artemis, each connection in its own tab of the same window. The same screens work with every broker; what a broker can’t do is left out. Support for all but Service Bus is new: the app marks it Beta.

Can I sign in with Microsoft Entra ID?

Yes, with a work or school account, for Azure Service Bus, Azure Queue Storage and Azure Storage. Microsoft’s sign-in opens in your browser; the first time, Microsoft asks you, or your organisation’s administrator, to allow Busrider. Busrider then lists the namespaces and storage accounts you can see, guest directories included, and greys what your roles don’t allow, with the role to ask for.

Is it an alternative to Service Bus Explorer?

Yes. For Azure Service Bus, Busrider covers the everyday tasks of the classic Service Bus Explorer for Windows in a modern desktop app. Browsing sessions comes in a later version. It is an independent project, not affiliated with Microsoft.

What can it do with a storage account?

Open its blob containers, tables and queues in one tab: search the blobs by name, path, text or regular expression, preview them, edit text blobs (saved only if nobody changed them meanwhile, with a snapshot of the version replaced if you ask), and query tables with their types.

Why does Busrider ask before reading a storage queue further?

Azure shows only the first 32 visible messages of a queue without taking them. To read further, Busrider receives them and gives them back: meanwhile they are hidden from their consumers, and each counts one more read (Azure Functions gives up on a message after 5, by default). So it asks first, and always on PROD.

Does reading a RabbitMQ queue take its messages?

RabbitMQ can’t show a classic or quorum queue without taking its messages for a moment: consumers don’t get them meanwhile, and they come back marked redelivered. Busrider asks before the first read. Streams are read in place.

What is a local broker?

An Azure Service Bus namespace that runs on your PC, created and started by Busrider for development and tests, empty or copied from your namespaces’ configuration. No Docker and no Azure bill. It runs on Busrider’s own emulator, not Microsoft’s: check your app against Azure before it goes live.

How do I clean up dead letters?

Open the Dead-letter tab of a queue or subscription to read the messages and why they were dead-lettered, resubmit the ones to retry, then purge the rest. On Azure Queue Storage, the queue Azure Functions moves a queue’s failed messages to is that queue’s Dead-letter tab.

Are my connection strings and passwords safe?

They are encrypted with your Windows account and never leave your computer. With Microsoft Entra ID there is no key at all, and your sign-in is kept the same way. Busrider talks directly to your brokers and to Azure; nothing goes through our servers.

Can an AI assistant change my queues?

Only where you allow it, and each change waits for your approval in Busrider. AI assistants are off until you turn them on, PROD connections stay locked, and assistants never get your keys.

What about the GDPR?

Busrider is built to need almost no personal data: no account, nothing from your brokers or Azure, and statistics only if you agree, with no lasting identifier. What the app sends is hosted in the EU. The privacy policy says what is kept, why and for how long; write to [email protected] to use your rights. Your brokers’ data stays yours: we never receive it, so we never process it on your behalf.

Does Busrider run on macOS and Linux?

Windows 10 and 11 today. macOS and Linux versions are coming, with the same features.

Choose what you accept. Your choice is kept for 6 months, then we ask again.