Every integration, one detail page each
Event-bus transports, the developer platform, identity, storage, external delivery channels, migration bridges, and the five active sibling platforms — the full picture behind aanty’s ecosystem moat.
31 integrations
Every entry links to a detail page covering how it connects, what flows each way, and what it pairs with.
Kafka
Kafka topics become conversations, not just logs.
Event bus · InboundRedis Streams
80+ event types, one ingestion path.
Event bus · Bi-directionalHMAC webhooks
Signed, retried, and boring in the way infrastructure should be.
Platform · Bi-directionalMCP
Your org graph, available to any MCP client — under your ACLs.
Platform · InboundSlack import
Bring your Slack history — all of it, not 90 days.
Platform · InboundTeams import
Leave the M365 chat tab, keep the conversation history.
Platform · Bi-directionalJira
Every ticket gets a thread. Every thread can move the ticket.
Platform · Bi-directionalGitHub
Pull requests and issues, discussed where the team already is.
Platform · Bi-directionalGitLab
Merge requests and pipelines, in the same graph as the discussion.
Platform · Bi-directionalSalesforce
Deals and cases get a thread, not just an activity-log entry.
Platform · Bi-directionalHubSpot
Pipeline conversations that stay next to the deal.
Platform · Bi-directionalGoogle Workspace
Docs, Drive and Calendar, connected to the conversation about them.
Platform · Bi-directionalMicrosoft 365
Files, calendar and identity from the M365 estate, without living inside a chat tab.
Platform · InboundZoom
What got decided in the meeting, captured where the async work lives.
Platform · Bi-directionalGoogle Calendar
Scheduling changes as messages, not a separate app to check.
Identity · InboundOkta
OIDC/SAML SSO — sign in with the identity your org already governs.
Identity · InboundAzure AD
Entra ID as the source of truth for who’s in your aanty org.
Identity · InboundSCIM
Provisioning that follows your directory, not a spreadsheet.
Storage · OutboundS3 object storage
Files and attachments in storage you control.
Event bus · InboundInbound email
A channel email address turns a reply into a typed message.
Event bus · OutboundSMS
The delivery channel for the alert that can’t wait for an app to open.
Event bus · OutboundMobile push
The needs-you queue, on the lock screen — never the whole firehose.
Platform · Bi-directionalZapier
Trigger a workflow from a message. Post a message from a workflow.
Platform · Bi-directionalMatrix
A federation-friendly bridge for teams who live on Matrix.
Platform · Bi-directionalA business bridge for the channel your customers already use.
Platform · Bi-directionalTelegram
Fast reach for broadcast and community, governed once it lands.
Sibling · Bi-directionalkumty
Execution Intelligence’s 80+ event types, native in aanty.
Sibling · Bi-directionalkumry
An AU financial ERP’s Kafka backbone, one HMAC hop from a conversation.
Sibling · Bi-directionalnainty
The AI chief-of-staff’s client portal chat, upgraded from 30-second polling.
Sibling · Bi-directionaltrainty
Sovereign AI education, with cohort channels and guardian alerts included.
Sibling · Bi-directionalinkury
A local-first document platform’s editor becomes aanty’s canvas.
Don’t see the integration you need?
The event ingestion bus, HMAC webhooks and MCP cover most sources out of the box. Tell us what you’re running and we’ll show you the fastest path in.