Understand the product model
MSPlex is the managed exchange layer between AI clients and real MSP systems. It is not a wrapper generator or an automation marketplace.
Getting Started
Start with the product model, not the hype.
MSPlex should make sense as infrastructure before it ever shows up as a workflow. This page explains what the exchange is, what is in the current build, and how an MSP should evaluate fit before the Q3 2026 early-access wave.
Orientation
Three things to understand before you evaluate.
Start with the stack fit
The current build is focused on operator workflows across PSA, documentation, and procurement surfaces that MSPs use every day.
Evaluate with the right expectations
This stage is about validating operational fit before launch, not forcing a buyer through a generic self-serve motion too early.
Launch posture
What is in the current build and what is next.
The current build centers on HaloPSA, Hudu, IT Glue, ConnectWise, and PAX8. SentinelOne, Datto BCDR, and Entra ID remain in the planned Q3 wave, with Microsoft 365 in the planned Q4 wave.
Current build
Current build
HaloPSAPSA
HuduDocumentation
IT GlueDocumentation
ConnectWisePSA
PAX8Procurement
Planned Q3
Planned Q3
SentinelOneSecurity
Datto BCDRBCDR
Entra IDIdentity
Planned Q4
Planned Q4
Microsoft 365Productivity
Evaluation flow
The right sequence for an MSP evaluation.
01
Map your stack
Confirm which systems matter most in your environment and whether the current build already covers them.
02
Pick the first workflows
Identify the workflows you want AI to touch first, especially ticketing, documentation retrieval, procurement, or identity tasks.
03
Review the security fit
Review trust boundaries, auth posture, and tenant isolation so the evaluation stays grounded in operational reality.
04
Request the next step
Use the contact flow to align on rollout timing, current build depth, and what an early-access path would look like.
Operator fit
Best fit for teams that already know where the pain is.
You should engage now if
- You already run one or more systems in the current build.
- You have clear AI workflows in mind for PSA, docs, or procurement.
- You want the gateway layer managed instead of building MCP plumbing internally.
Review next
The strongest next pages after this one are the security posture and the connector catalog. They answer the trust and coverage questions that usually determine whether a buyer is ready to keep moving.
Ready to map your stack?
Bring the systems you care about most, the workflows you want AI to touch first, and the security questions that need answers. We will use that to shape the right early-access conversation.