Kafka
Kafka topics become conversations, not just logs.
How Kafka fits into aanty
aanty is a first-class consumer of Kafka topics — the exact shape kumry already runs (37 microservices, 18+ kumry.*.events topics). Every event on a subscribed topic renders as a system message in the right channel or thread, and aanty publishes its own registry-named events back so producers can react to what happens in the conversation.
Native topic consumer
Subscribe a channel to one or more Kafka topics; each message on the topic becomes a typed system message people can reply to.
Outbound event publish
Actions in aanty — a reply, an approval, a mention — publish back as registry-named aanty.<domain>.<action> events on your topics.
Entity-linked threads
Events that reference an entity (invoice, task, risk) attach to that entity’s thread via the generic linked_entity envelope, not a fresh unrelated message.
Bi-directional integration
Events flow both ways: Kafka activity lands in aanty as a typed message in the right thread, and actions taken in aanty — approvals, replies, assignments — flow back out to Kafka, kept in sync through the same tenant-scoped access controls as the rest of the product.
See it alongside
Other integrations and pages that pair naturally with this one.
See Kafka inside a real aanty workspace
Bring the Kafka events your team already generates. In fifteen minutes we'll show you what they look like as a conversation, not a notification.