MSP Manager is cloud-hosted SaaS — there is no on-premises deployment option. The management console is browser-based, and the customer portal is web-accessible. Setup involves configuring client records, service tiers, billing templates, and contract structures before connecting the RMM integration.
For N-able RMM customers, the RMM integration configuration is handled through N-able's shared ecosystem settings rather than through a separate API setup — which means the time-to-operational alert routing is significantly shorter than configuring a third-party PSA integration with N-central or N-sight.
The RMM alert-to-ticket integration supports both N-central and N-sight. Alert thresholds, device groups, and alert categories in the RMM can be mapped to specific ticket templates, priorities, and assignment rules in MSP Manager. This means that when a monitoring alert fires, the resulting ticket is not a generic 'alert from RMM' entry — it can be pre-populated with the correct client, device context, service category, and priority based on rules configured in the integration.
The depth of this configuration depends on how the MSP has structured their N-central or N-sight monitoring policies, so teams with well-configured RMM alert structures get more value from the integration than teams with generic alert policies.