MSPlex/Resources/FAQ
FAQ

Common questions before rollout.

These are the recurring questions buyers ask as they move from product curiosity into practical evaluation. Use this page to clarify the model, connector posture, and trust expectations before you open a direct conversation.

Product model

Is MSPlex a marketplace or wrapper platform?

No. MSPlex is the managed exchange layer between AI clients and MSP systems. It focuses on routing, connector behavior, and operational trust boundaries rather than acting like a generic automation marketplace.

Who is the right fit for MSPlex today?

The current public posture is aimed at MSP operators who already know where the workflow pain is and want a cleaner way to connect AI to production systems.

What should an MSP bring into an evaluation?

Start with the current build, connector fit, and the workflows you want AI to touch first. That gives the evaluation a practical shape instead of a generic demo request.

Connectors and launch

Which connectors are in the 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.

What is still in the launch pipeline?

SentinelOne, Datto BCDR, and Entra ID remain in the planned Q3 wave, with Microsoft 365 in the planned Q4 wave.

When is MSPlex aiming to launch?

The public site is aligned to an early-access target in Q3 2026. Buyers should treat the current public surfaces as launch-readiness guidance, not a claim that every planned connector is already shipping.

Security and evaluation

How should I think about tenant isolation?

The public posture is that tenant isolation and managed auth handling belong in the gateway layer, not scattered across every AI client or workflow definition.

How much security detail should I expect publicly?

The public site should answer the first trust questions. Deeper implementation detail should move into a direct evaluation conversation once the stack and workflow fit are clear.

Can I evaluate MSPlex before talking to the team?

Yes. Use the connector catalog, the experience page, and this resources section together. They are designed to reduce uncertainty before you ask for a direct rollout conversation.

Use the FAQ with the operational pages around it.

Still have a gap?

If the public answers still leave a blocker, route the question directly to the MSPlex team so the response can be grounded in your stack and rollout timing.

Need an answer that depends on your stack?

Public FAQ content should eliminate the generic questions. The next layer is a direct conversation about connector fit, workflow shape, and rollout timing in your environment.

MSPlexFAQ