INKY vs Respond.io

INKY ships a dashboard release every one to two weeks, moving from 1.8.5 to 1.9.6 since May. The functional center is the Triage workspace, which pulled detection review, message actions, and account-takeover enforcement into one place and made ATO configurable without a SIEM. July added Smart Insights, an LLM second opinion on any inbound message with a plain-language explanation, gated to INKY Pro with a per-team opt-out. The releases since have returned to widening the rule engine and the integration surface around it.

Two threads run in parallel. One is analyst experience: consolidate review into Triage, then explain verdicts rather than just issue them. The other is distribution — Autotask ticketing, Gradient billing reconciliation, KaseyaOne role alignment, CyberHoot training recognition — all of which make INKY easier to run inside a Kaseya-provisioned MSP stack and harder to swap out of one. The newest release refines both rather than extending either: a bracketed-subject rule condition, and Autotask ticketing split per report type so a phishing-only configuration is finally saveable.

Expect Smart Insights to expand from an on-demand second opinion into something that annotates the Triage queue by default, since that is where its explanations would actually save review time. On the integration side the pattern is one new partner platform per release, so the next addition is more likely another MSP tool than a change to detection itself.