Current build
The current build centers on HaloPSA, Hudu, IT Glue, ConnectWise, and PAX8. That is the operator-first core of the current public connector story.
Roadmap
Public roadmap, grounded in real MSP workflows.
MSPlex roadmap language should make one thing clear: what is in the current build, what is planned for the next waves, and what is still just demand shaping. This page keeps those categories separate so rollout expectations stay credible.
Roadmap layers
Separate the current build from the next two waves.
Q3 2026 wave
Q3 planning is focused on security, backup, and identity surfaces: SentinelOne, Datto BCDR, and Entra ID.
Q4 2026 wave
Q4 planning extends into Microsoft 365 productivity workflows while additional connector demand continues to be shaped by operator requests.
Connector waves
The current build is real. The next waves are planned.
Current build
- HaloPSA
- Hudu
- IT Glue
- ConnectWise
- PAX8
Planned Q3
- SentinelOne
- Datto BCDR
- Entra ID
Planned Q4 and later demand
- Microsoft 365
- Kaseya
- Additional PSA
- NinjaOne
- Sophos
Roadmap rules
Expansion should follow workflow pressure, not logo chasing.
01
Prioritize operational fit
The roadmap should follow operator workflow demand, not generic marketplace breadth.
02
Keep readiness legible
Current build, Q3, and Q4 must stay visibly separate so the public site never blurs readiness with intention.
03
Weight requests by workflow depth
Connector requests matter when they connect to real workflow depth, not just brand recognition.
Review next
Pair the roadmap with live launch detail and fit guidance.
Use with
Practical note
A public roadmap should help buyers plan conversations, not assume production availability before the current build and rollout timing are actually ready.
Need to map the roadmap to your operating stack?
Bring the systems you rely on most and the workflows you want to accelerate first. We can tell you what is current, what is planned next, and where demand is still being shaped.