What the service evidence establishes
Kaseya offers outsourced endpoint monitoring, management, patch and backup operations. Its NOC terms, updated October 7, 2025, define service through scoping and enrollment documents. Certain endpoints require supported RMM access; confirm the exact platform rather than assuming every Kaseya product is interchangeable. See the official service source.
Commercial boundary to resolve
The NOC terms say service is for customer personnel rather than customer end users, with English as the default unless scoped otherwise. Licenses can remain billable through the committed term when endpoint counts fall. Published SLOs are objectives rather than hard commitments. Ticket information is retained for six months and may then be deleted; it is stated as unavailable for export to the customer. Check the current order and negotiated amendments.
Qualification by scenario
| Your scenario | First question | Evidence to retain |
|---|---|---|
| Shrinking estate | Can licenses be reassigned, reduced or terminated during the term? | Committed-license schedule and removal/reassignment rules |
| End-user requests | Which separate desk service handles client contact? | NOC versus help desk intake and scope |
| Exit records | How will your own operational history be retained? | Buyer-owned ticket evidence and an agreed handover path |
Bring a defined inventory and anonymized workload to the first discussion. Device counts, user counts and ticket volumes describe different obligations. Record a missing answer as unresolved; do not substitute a zero cost, an assumed capability or a negative quality judgment. Ask the supplier to identify the applicable plan and legal entity in its reply.
Public customer evidence and its limits
The product page includes provider-hosted comments attributed to named customers, including Chris Morton, CIO at Logically. We have not independently interviewed the speaker, and this is not a substitute for a scoped reference. Ask a current user how license changes and operational records worked under their actual order.
For a reference conversation, ask when the service was used, which plan and shifts were involved, what the customer retained internally and whether a material incident or exit was experienced. A named comment can help identify a question to investigate, but it does not establish the full SLA, staffing model or suitability for your clients.
A bounded pilot before enrollment
Before enrollment, run a supported-endpoint test and an unsupported or inaccessible-endpoint test. Confirm who detects missing RMM access, what remediation is possible and how billing continues. Record incident evidence in your own permitted system from the start; do not assume an exit export will be available. Have your contract reviewer evaluate proposed amendments where continuity requirements exceed the public terms.
Define pass and fail criteria before testing: correct tenant, permitted action, an intelligible audit trail, accepted escalation and a reversible access path. Preserve both successful and unsuccessful cases. Use these criteria when agreeing your own pilot.
Compare the same obligation
Use the provider directory to select candidates, then send one RFP with identical scope. Normalize the quote in the cost calculator and record the five SLA clocks separately. Confirm staff and data locations, notice and exit work in writing before granting production access. Read our methodology or send a sourced correction.