wharf
Sign in

Integrations

Fits the stack you already run.

Wharf connects to your existing brokers. It doesn't ask you to route traffic through anything new, and it doesn't run a server of its own.

One client, two brokers, no relay in between.

Wharf connects directly to whichever broker your topic lives on. Kafka is the primary integration; Pulsar runs through the same interface.

Apache Kafka

Primary integration
connected · 2m ago
Topicorders.created
Partition3
○ord_92831#184291
○ord_92834#184294
"order_id": "ord_92831",
"amount": 149.99

Connect to any Kafka cluster you can already reach — self-hosted, Confluent Cloud, or a managed equivalent, over your existing network path.

SASL/PLAINSASL/SCRAM-256SASL/SCRAM-512mTLS

Apache Pulsar

Supported integration
connected · 4m ago
Topicorders-created
Partition0
○ord_55210#8842
○ord_55213#8845
"order_id": "ord_55210",
"amount": 62.00

Connect to a Pulsar cluster with the same interface used for Kafka — topics, partitions, and messages behave the same way regardless of broker.

OAuth2Token auth

What's not supported yetnot shipped

Wharf doesn't support other message brokers, queues, or streaming platforms today. Additional broker support is a direction we're considering, not a scheduled release — nothing to see here yet beyond Kafka and Pulsar.

Connect your first cluster.

Get early access