Production-ready today for real MSP evaluation.
Built for the tools MSPs actually run.
MSPlex connectors are built against real production environments. They are not wrappers generated from API docs. They are operational routes for the systems MSPs already depend on.
Queued for the next public waves based on MSP demand.
Across PSA, documentation, security, backup, and identity.
Production routes, not connector theater.
The first MSPlex connectors focus on the systems MSPs touch most often during daily operations. Each route is designed to survive the operational details that demos skip.
HaloPSA
Full ticket lifecycle, client management, contract billing, time entries, asset tracking, and SLA monitoring.
- Ticket lifecycle management
- Client and contract lookup
- Time entries and asset tracking
- SLA and workflow visibility
Hudu
Knowledge base search, password retrieval, asset documentation, company records, and procedure lookup.
- Knowledge base search
- Password and process lookup
- Asset documentation access
- Company and procedure records
Queued around real MSP demand.
The roadmap is intentionally vertical. MSPlex is prioritizing security, backup, and identity systems that extend real cross-tool workflows instead of chasing generic breadth.
SentinelOne
Threat detection status, endpoint health, quarantine actions, policy management, and incident investigation.
- Threat detection status
- Endpoint health checks
- Quarantine and policy actions
- Incident investigation support
Datto BCDR
Backup status, recovery point verification, screenshot checks, agent health, and restore operations.
- Backup status checks
- Recovery point verification
- Screenshot and agent health review
- Restore operation support
Entra ID
User management, group membership, license assignment, sign-in logs, and conditional access policy review.
- User and group management
- License assignment
- Sign-in log visibility
- Conditional access policy review
What makes an MSPlex connector production-ready.
A connector is only useful if the auth model, tenancy boundaries, and operational edge cases are already handled. That is the actual work.
Auth handled properly
OAuth2, API keys, token refresh, and tool registration are built into the connector layer instead of delegated to ad hoc scripts.
Tenant-safe by design
Every connector is designed for per-tenant credentials, usage metering, and the exchange model required by MSP environments.
Built for real workflows
The goal is not a generic tool list. It is reliable execution across tickets, docs, security posture, identity, and backup operations.
Tell us what your stack needs next.
If your team needs ConnectWise, IT Glue, NinjaOne, Sophos, or another platform, that demand should shape the roadmap.