The AI agent for Heroku Kafka | Menza
Menza Heroku Kafka logo

KNOW WHAT YOUR HEROKU KAFKA CLUSTER IS DOING.

Connect Heroku Kafka to Menza and ask about your clusters, topics, consumer groups and configuration without opening the CLI — what's provisioned, how retention is set, which topics have no consumers. Menza reads it live through the official Heroku APIs, and the connector is read-only, so your cluster is never touched.

  • Reads databases data
  • Generates answers and insights
  • Connects via the official API

What can Menza do with Heroku Kafka?

Audit topic config in one question

Ask how retention, partitions and replication are set across every topic and Menza reads live cluster configuration, so misconfigured topics surface before they lose data.

Find the topics nobody consumes

Ask which topics have no consumer group attached and Menza cross-reads topics against consumer groups, so abandoned streams and forgotten experiments stop cluttering the cluster unnoticed.

See every Kafka add-on across your apps

Ask which apps run Kafka add-ons and on what plans, and Menza reads live Heroku data — one inventory of clusters, versions and attachments without touching a dashboard.

See these answers on your own Heroku Kafka data.

Menza working with Heroku Kafka.

Menza watches your Heroku Kafka data and surfaces what's worth knowing the moment it spots it — the margins, stockouts, and trends you'd otherwise dig for. Read-only: it answers and flags, never changes your data.

MenzaMenzajust now

Topic 'user-events' is set to 24-hour retention while every other production topic keeps 7 days. The setting dates from its creation in a staging test — downstream replays past yesterday will come up empty.

MenzaMenza6m ago

Your cluster runs 14 topics but only 9 have a consumer group attached. The five without consumers are all prefixed 'exp-' and were created in March — likely finished experiments.

Connect Heroku Kafka in a couple of clicks.

Is my Heroku Kafka data secure?

Your credentials are encrypted at rest and never exposed to the AI. Menza reads your data through the provider's official API using the access you grant, and you stay in control of what it can do — read-only by default, with any actions gated behind your approval.

Read our privacy policy
  • Encrypted in transit and at rest
  • Scoped access — you choose what Menza can see
  • Read-only by default; any action needs your approval
  • Credentials are encrypted and never shown to the AI
  • Revoke access at any time

Heroku Kafka questions, answered.

How does Menza connect to Heroku Kafka?

You connect with your Heroku API key — paste it once and you're done. The key is encrypted at rest and never shown to the AI; Menza uses it server-side to read your apps, add-ons and cluster data through Heroku's official APIs.

What can Menza answer about my Heroku Kafka data?

Anything the APIs expose: apps, add-ons, cluster info, topics, consumer groups and configuration. Ask which topics exist and how they're configured, which consumer groups are attached where, or which apps share a cluster.

Is my Heroku Kafka data safe with Menza?

Yes. Your API key is encrypted and never exposed to the AI, and Menza can only reach what the key grants. This connector is read-only — Menza never changes topics, consumer groups or configuration; it reads cluster state to answer questions.

Can Menza read the messages inside my topics?

No. Menza works with the management APIs — cluster info, topics, consumer groups and configuration — not the message stream itself. It tells you how the cluster is set up and used, without ever consuming your event data.

Put Menza to work on your Heroku Kafka data.