Making organisational decisions explainable, accountable and auditable.
DEXYS covers quality, information security and AI standards (ISO 9001, 27001 and 42001), alongside risk, controls, decision authority, accountability, nonconformities and evidence. What sets it apart is that it connects a decision to the authority that allowed it, the risk and controls it answers, the actions that followed and the evidence behind it.
Describe your organisation once and keep it current: the Registers of issues, interested parties, risks, impact assessments, the roles people hold and the authorities you will not let a machine decide, alongside your processes, policies, systems and people.
Assess the documents you already hold against ISO 9001, ISO 27001 and ISO 42001, and Cyber Essentials. Each requirement gets one audit-readiness verdict, golden threads show what has to join up, and the gaps are named rather than averaged away.
Record a decision once and connect it to the authority who may take it, the accountable person, the risk and controls it answers, the actions that follow and the evidence that supports it. A named person confirms it, the confirmation carries a review date, and DEXYS can say in writing which rule produced each answer.
The Assurance checker ships inside your DEXYS deployment and checks your Microsoft 365 and Azure configuration on a schedule. It reports what it finds, including when a run fails, because silence reads as health. A failing check alerts the accountable person, and what follows is worked through as events, incidents, nonconformities and corrective actions.
AI assistants are useful when they answer from what your organisation has confirmed, and dangerous when they answer from nothing. DEXYS lets them work inside the record, as the person who connected them.
On a plan that includes it, an assistant that speaks the Model Context Protocol can answer from your confirmed record. It acts with the connecting person's own permissions, every change it makes is recorded in that person's name, and each area is exposed only when you tick it: the default is nothing. A decision it adds from an assessment is a draft with nothing accepted. An AI assistant has worked a test organisation over MCP (November 2026): Claude, signed in as a member of that organisation, ran assessments, set up decisions and checks, and closed failing-check alerts. It has run on a test organisation so far.
DEXYS can package your confirmed working practices as a Microsoft 365 Copilot agent, “How we work”, for your administrator to upload to your own tenant. It was uploaded to a test tenant and tested in Microsoft 365 Copilot in November 2026.
The AI agents your organisation runs are recorded in an agents register beside the people and roles. An agent may hold a role and perform it, and that is recorded; competence is a claim about a person, so an agent is never graded on it.
If you run Azure API Management in front of your AI tools, you can connect your gateway to DEXYS. The gateway asks DEXYS whether your own record shows a recorded stop for the system behind a tool, and the human sovereignty boundary lists the authorities you will not delegate to a machine. It needs your own API Management and is off until you connect it, and DEXYS enforces nothing by itself.
A governance record is only worth trusting if you can see what holds it and what can reach into your systems. These are the guarantees, stated with the conditions they depend on.
In a deployment in your own Azure subscription, DEXYS holds no standing credential into the systems your organisation declares. DEXYS Assurance is a read-only registration with no secret, used for the checks you switch on, consented to by your administrator and revocable by them at any time. Where DEXYS hosts your deployment, DEXYS holds the same registrations and no secret for them.
The Assurance checker runs compiled read-only commands. Some checks need a permission that could also change things, such as SharePoint full control. None is given by default: your administrator opts in one at a time, with an acknowledgement, and can opt out at any time.
You can keep your compliance documents in your own SharePoint. Where you host your own deployment, your record stays in your Azure subscription, on your own spend, in the region you choose.
DEXYS can carry out a short list of named changes in your systems, but only when a named, accountable person presses for them, on that person's own permission. Closing a corrective action can need a second person: until an Organisation Admin narrows it, every severity needs a peer review.
Changes to the record are kept in a change log and a case history with who made them and when.