Front end
React, TypeScript, Microsoft Fluent UI design system.
CIO & IT leadership
Not another platform. The platform you already run
IT says no to structured-content programs for reasonable reasons: another vendor, another identity provider, another audit perimeter. Dx5 asks for none of them. It is a SharePoint application running inside your Microsoft 365 tenant, on the security posture IT already operates.
Entra IDThe identity model you already run
One list No second user list to maintain
The deployment shape
Inside the perimeter you already audit
Dx5 is one more application inside the customer's existing Microsoft 365 tenant. The dashed line below is the perimeter the IT team already owns: identity, audit, data-residency. Nothing about Dx5 crosses it.
The structural problem
Every CCMS deal stalls in IT for the same reasons
The content team picks a vendor, procurement starts the contract, IT starts the architecture review, and the deal stalls. The stall is rarely about the product. It is about adding a platform: another vendor, another identity to maintain, another perimeter to audit.
Dx5 removes the architecture review by being a SharePoint application. Your existing tenant is the deployment target, so the identity provider, access controls and audit posture are the ones you already run.
What changes for IT
| What changes | How |
|---|---|
| Not another platform to approve | Dx5 is a SharePoint application. It runs inside the Microsoft 365 tenant you already operate. No separate vendor platform to provision, monitor or audit. |
| Not another identity provider | Microsoft Entra ID single sign-on. No separate credentials, no second password rotation, no parallel access regime. Conditional access rules apply unchanged. |
| Not another data-residency conversation | Content lives in the customer’s SharePoint. The data-residency posture of the tenant. Microsoft 365 region, sovereign cloud, on-premise, applies unchanged to Dx5 content. |
| On-premise deployment for environments that require it | SharePoint Server 2019 and SharePoint Server Subscription Edition supported. Air-gapped and sovereign deployments work. |
| Vendor risk that does not lock the content in | Content is stored as DITA XML, the open international standard. Any DITA-compliant tool can read it. SharePoint exports cleanly. The exit path does not require our cooperation. |
Tech stack
Built on what your IT team already operates
SharePoint integration
SharePoint Framework (SPFx), Microsoft’s official extension model.
Back end
ASP.NET.
Authentication
Microsoft Entra ID single sign-on. No separate credentials.
Deployment
SharePoint Online (Microsoft 365), SharePoint Server 2019, SharePoint Server Subscription Edition. National-cloud Microsoft 365 (US Government, Germany, China 21Vianet) and hybrid topologies supported.
Content storage
DITA XML (ISO-recognized) inside SharePoint document libraries.
Frequently asked questions
How does it get installed, and who does the installing?
The Dx5 package goes into your SharePoint app catalog and provisions its own SharePoint libraries on first run, so there is no build-out phase before the content team can start. Integration uses the SharePoint Framework, Microsoft's own extension model. DxAuthor+ is either customer-managed or hosted by us for SharePoint Online, which is a procurement preference rather than a product difference.
What has to reach the author's desktop?
A Word add-in, into the Word your tenant already licenses. DxAuthor+ runs in Word for Microsoft 365 on the desktop and on the web, and DxChecker for Word is the same shape. There is no forked build of Word to distribute and no second set of credentials to issue, because sign-in is Microsoft Entra ID.
Do Purview, eDiscovery and our data-loss-prevention rules cover this content?
They cover it because there is nothing separate to configure. Components are items in SharePoint document libraries, so classification, audit, eDiscovery and data loss prevention apply as they do to the rest of the estate, and SharePoint audit logs feed Microsoft Sentinel or another SIEM through standard connectors. Dx5 adds no separate plan for audit, logging, prevention or backup.
What is on the roadmap that we should not plan around?
Two things, named so nobody budgets against them. DxChecker rules running inside the DxAuthor+ authoring experience at write time is under development and is not shipping; today DxChecker runs as its own Word add-in, as a server-side job, or through its API. Rule authoring in natural language rather than XML is also a development item. Plan on what is in the platform now.
Our documentation is tightly coupled to PLM and CAD data. Does that change the answer?
It might, and it is worth naming rather than working around. Bluestream's center of gravity is manufacturing and product documentation, with integrations into PLM, ERP and CAD, and for an organization whose documentation is an extension of its product data that focus is a genuine advantage. Ours is regulated content governed inside the Microsoft estate. If the industrial coupling is your priority, start there.
Start the technical conversation early. The architecture review goes faster
Rollouts that involve IT from the start close faster than the ones that arrive at architecture review unannounced. There is less to negotiate when the answer to every objection is the tenant you already run.
