INKY vs LiveAgent
Side-by-side trajectory, velocity, and editorial themes.
Email security platform deepens its absorption into the Kaseya MSP ecosystem with each release.
INKY is an email security platform deeply integrated into the Kaseya MSP ecosystem. The visible release window is dominated by integration plumbing — KaseyaOne role mappings, Autotask Integrated Customer Billing, Graphus and SaaS Defense imports, and partner-facing usage/billing dashboards — alongside steady UX modernization of admin tables and team selectors.
The product is consolidating its place inside Kaseya's MSP stack rather than expanding outward to new buyers. Each release wires further into Kaseya billing, identity, and partner surfaces, and provides one-click pathways from competitor or sibling Kaseya products (Graphus, SaaS Defense). The standalone INKY surface area is being modernized at the same time, but new directional moves are scarce — execution is the focus.
Expect continued Kaseya integration density (BMS, Datto RMM, or Quote Manager are likely next), more bulk-action and partner-tier features, and gradual deprecation of legacy Graphus surfaces as imports complete. Net-new threat-detection or AI capabilities are not visible in this window and unlikely to land before the integration push settles.
LiveAgent wires its ticketing engine into the Claude ecosystem via MCP.
LiveAgent is in dense maintenance mode — multiple version trains and a backport branch all shipping fixes and security patches almost daily — but the AI integration thread has sharpened. The 5.64 release adds an AI Agent Work Distributor for tickets, a new add_note MCP tool, and OAuth 2.1 on the MCP server with the explicit goal of letting claude.ai connect as a custom connector. Earlier May releases switched the MCP protocol to Streamable HTTP and renamed MCP tokens for clarity.
The product is positioning MCP as its core integration substrate. Each release adds another MCP refinement — protocol upgrade, naming cleanup, ticket-level AI work distribution — pointing toward a model where Claude or any MCP-aware agent triages and acts on tickets natively. The parallel backport lines (5.62.x, 5.63.x) suggest the AI work is being layered on without forcing customers off the legacy install base.
Expect the AI Agent Work Distributor to grow into more autonomous resolution flows, with new MCP tools added incrementally (search, reply, escalate), and a more explicit Claude-Connector-ready posture in product marketing.
See more alternatives to INKY →
See more alternatives to LiveAgent →