TopicConsole

What is TopicConsole

TopicConsole is an open-source Apache Pulsar desktop client that puts cluster browsing, message inspection, and lightweight administration into a single app. It is designed for teams that want a local tool rather than a hosted control plane, so the connection runs from your computer straight to your Pulsar environment.

The app focuses on three core jobs:

• exploring tenants, namespaces, topics, and subscriptions;
• observing live message traffic with a low-impact reader-backed mode;
• searching message history and exporting results for follow-up work.

It is available for macOS, Windows, and Linux, and the site describes current builds for Apple Silicon and Intel macOS, Windows amd64, and Linux amd64. The project is publicly developed under AGPL-3.0, with source and issue tracking on GitHub.

Key features

TopicConsole centers on a small set of practical Pulsar workflows rather than a broad admin suite.

• Direct broker and admin connections: you enter the Pulsar service URL and admin URL you already use, then connect without a middleware service in between.
• Cluster navigation: the workspace shows tenants, namespaces, topics, and subscriptions, with partition counts visible while you browse.
• Observer mode: you can watch new traffic without creating a durable subscription, which makes it useful for incident checks and quick development validation.
• Search tools: search by message key, payload text, JSONPath, JMESPath, and publish time.
• Side-by-side inspection: message metadata and content can be viewed together, which helps when you need to match headers, keys, and payloads.
• Export options: search results can be exported as JSON or CSV.
• Explicit actions: the app also supports producing test messages and running admin actions, but those remain deliberate steps rather than automatic background behavior.
• Local-first setup: credentials stay on your machine, and the product does not rely on a hosted TopicConsole account.

How to use it

1. Download the build for your platform from the official site or GitHub Releases.
2. Open the desktop app and add your Pulsar service URL and admin URL.
3. Test the connection before saving so you can confirm the cluster is reachable.
4. Browse from tenants to namespaces, then drill into topics and subscriptions.
5. Use observer mode when you want to read live traffic without leaving a durable cursor behind.
6. Search historical messages with filters such as key, payload text, JSONPath, JMESPath, or publish time.
7. Open message metadata and payload together, then export the set as JSON or CSV if you need to share findings.
8. If needed, create test messages or run admin actions intentionally from within the same workspace.

The workflow is meant to support a common sequence: connect, inspect, observe, search, and then export or act.

Who it is for

TopicConsole is a good fit for people who work with Apache Pulsar clusters and want a focused desktop viewer instead of a larger platform.

It is especially relevant for:

• platform engineers who need a quick way to inspect namespaces and subscriptions;
• developers validating whether events are arriving as expected;
• operators checking live traffic during incidents;
• teams that prefer local credentials and direct broker connectivity;
• users who want a lightweight client without Docker or a JVM dependency.

The app is also useful when you need to move between multiple environments, since the site highlights keeping production and other clusters close at hand in one workspace.

What to know before you use it

TopicConsole is intentionally narrow in scope, so it is best understood as a desktop client for browsing and investigation rather than a replacement for official Pulsar administration tooling.

• It works with Apache Pulsar via your own service and admin endpoints; it is not a managed Pulsar service.
• Observer mode is designed for reading live traffic without creating a durable subscription, but it is still a read-path workflow rather than a full historical replay system.
• The site does not claim support for every architecture or operating system; the published builds mentioned are macOS on Apple Silicon and Intel, Windows amd64, and Linux amd64.
• Because credentials remain local and there is no companion server, you are responsible for how those endpoints and secrets are managed on your machine.
• Search and inspection depend on the live cluster data you can reach; if you need the authoritative source for production administration, use your official Pulsar tools, permissions, and cluster procedures alongside this app.

TopicConsole is most useful when you need a lightweight, local Apache Pulsar desktop client for fast inspection and safe observation. If you want to browse topics, inspect payloads, and verify message flow from your own machine, TopicConsole keeps that path direct and simple.