RMM integration
Kaseya-stack MSPs get parity with the NinjaOne experience — organizations, agents, and alarms on the customer hub.
What Vectis syncs
The read side of the adapter. Pulled on a schedule and available everywhere the customer account surface lives.
Actions Vectis can take
Write-back methods this adapter exposes. Rules can call them; so can inline actions on the customer hub. Every action is logged to the audit trail.
How it correlates
Vectis is about Kaseya VSA joining your other systems around the customer account — not a standalone dashboard. Two concrete examples:
Kaseya alarms for a customer join their ConnectWise or Autotask tickets and their Pax8 license inventory on one page. The account hub is one consistent shape regardless of which RMM you run.
A single rule template — 'RMM alert older than 30 minutes with no PSA ticket → open one' — works whether the alert came from Kaseya or NinjaOne. Same cross-tool automation, different underlying stack.
Setup snapshot
Mint a dedicated API token in Kaseya VSA → Settings → API Access → Tokens. Use a service role with read on organizations + agents + alarms and write on alarms (acknowledge + close). Paste the token and your VSA tenant URL into Vectis and pick your VSA major version (VSA 10 SaaS today; on-prem VSA 9 + VSA X are planned for follow-up phases). Vectis tests with a paginated org query before saving.
Full setup guideavailable after signup
14-day free trial. Connect Kaseya VSA at signup. See every customer with their full context on day one. Cancel anytime during the trial at no charge.