Tenant isolation
Users, licenses, devices, credentials, support, and marketplace state stay tenant-scoped so client workspaces do not expose provider or cross-tenant context.
Security
MSPGate keeps tenant boundaries, approval gates, audit trails, device trust, and package entitlements visible before work moves from planning to execution.
Users, licenses, devices, credentials, support, and marketplace state stay tenant-scoped so client workspaces do not expose provider or cross-tenant context.
AI can plan and explain actions, but execution stays bound to entitlement, tenant policy, device trust, risk class, and approval state.
Launch MSP remains shadow-only, giving early customers visibility and guided workflows without real execution privilege.
Operational actions and governance events are visible through audit logs and export surfaces for review, reporting, and client proof.
Device posture, telemetry summary, rollout state, shadow policy, and patch posture help operators avoid blind execution decisions.
Marketplace services expose credential needs and connection posture so sales and operators do not imply unsupported one-click automation.