MSPlex/Status
Status

Read what is live now, and what is still on the launch track.

This page separates live public surfaces from launch-readiness signals. The website, CMS publishing, and contact routing are operational today. The managed gateway rollout should still be framed around the current build and the Q3 2026 target.

Operational signals that are already live.

Website surface live

The public marketing site, structured data, and public resources are live and actively maintained.

CMS publishing live

Directus is live behind the blog and launch-update publishing flow, so public articles and updates can be published without code deploys.

Contact routing live

Website forms route through the Google Workspace mail flow, with branded notifications to the team and branded confirmations to submitters.

Gateway on launch track

The managed exchange itself is still on the launch track. Public readiness should be discussed in terms of current build depth and Q3 2026 rollout timing, not as a general-availability claim.

Keep the current build separate from the next wave.

Current build

5 connectors in the current build

HaloPSAPSA
HuduDocumentation
IT GlueDocumentation
ConnectWisePSA
PAX8Procurement
Planned Q3

3 connectors planned for Q3

SentinelOneSecurity
Datto BCDRBCDR
Entra IDIdentity
Planned Q4

1 connector planned for Q4

Microsoft 365Productivity

Pair public status with the right trust and rollout surfaces.

Status rule

Public status should make it obvious which surfaces are operating today and which product capabilities are still being communicated as launch-track readiness. That distinction keeps buyer trust intact.

Need the status conversation grounded in your stack?

We can map your current tools, security posture, and launch expectations to the real build and the next planned wave.

MSPlexStatus