kumry
An AU financial ERP’s Kafka backbone, one HMAC hop from a conversation.
How kumry fits into aanty
kumry runs 37 microservices on Kafka with 18+ topics and its own notifications service (Socket.io, email, HMAC webhooks, 40+ event→notification mappings). aanty consumes kumry’s Kafka topics directly and turns invoice, bill and compliance events into discussion threads and practice-wide firm channels, plus client portal chat.
Kafka topic bridge
aanty consumes kumry’s 18+ kumry.*.events Kafka topics, turning system events into threads on the record they describe.
Practice-wide firm channels
Compliance and period-close events route to firm-wide channels alongside per-client discussion threads.
Client portal chat
Replaces kumry’s portal queries with a purpose-built, magic-link client portal for invoice and compliance conversations.
Bi-directional integration
Events flow both ways: kumry activity lands in aanty as a typed message in the right thread, and actions taken in aanty — approvals, replies, assignments — flow back out to kumry, 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 kumry inside a real aanty workspace
Bring the kumry events your team already generates. In fifteen minutes we'll show you what they look like as a conversation, not a notification.