Current build
5 connectors in the current build
HaloPSAPSA
HuduDocumentation
IT GlueDocumentation
ConnectWisePSA
PAX8Procurement
Connector Guidance
Judge connector fit by workflow, not by logo count.
The public catalog shows what exists. This page explains how an MSP should evaluate connector relevance, how to separate the current build from the roadmap, and what the common next requests tell you about where the system may expand.
Current fit
Start where the current build already aligns with your stack.
Planned next
4 connectors in planned waves
SentinelOnePlanned Q3
Datto BCDRPlanned Q3
Entra IDPlanned Q3
Microsoft 365Planned Q4
Evaluation rules
Three rules for judging connector relevance.
01
Choose high-frequency systems first
Start with the systems your operators already use most often. Connector fit matters more than broad future roadmap breadth in the first evaluation.
02
Evaluate workflow depth
Judge the connector by the workflows you need, not just the logo. Ticketing, documentation, procurement, and identity surfaces all have different operational depth.
03
Separate current build from roadmap
Keep the current build and planned waves separate in your planning so the rollout conversation stays realistic.
Common next requests
Where buyers often want the exchange to expand next.
Frequent requests
- Kaseya
- Additional PSA
- NinjaOne
- Sophos
Use this with
Need connector guidance grounded in your stack?
The best rollout conversation starts with the systems you run today, the workflows you care about most, and the gaps you need the exchange to close first.