kumty
Execution Intelligence’s 80+ event types, native in aanty.
How kumty fits into aanty
kumty runs 88 tables, 437 routes and Redis Streams with 80+ event types across comments, @mentions and per-event-type channel preferences. aanty replaces kumty’s Slack/Teams bridge_configs with native entity-linked threads on tasks, risks and decisions, fed directly by kumty’s Redis Streams.
Entity-linked project threads
Tasks, risks and decisions in kumty each get an aanty thread with a live status card, not a comment box bolted on.
Redis Streams ingestion
kumty’s 80+ event types feed the event bus directly, replacing bespoke Slack/Teams bridge configs.
Per-event-type preferences
Notification routing follows kumty’s existing per-event-type, per-channel preference model — nothing to relearn.
Bi-directional integration
Events flow both ways: kumty activity lands in aanty as a typed message in the right thread, and actions taken in aanty — approvals, replies, assignments — flow back out to kumty, 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 kumty inside a real aanty workspace
Bring the kumty events your team already generates. In fifteen minutes we'll show you what they look like as a conversation, not a notification.