Devia

• Capturing a deviation on the shop floor, such as a fill-weight variance or a cold room excursion, with photos and PDFs, and having Devia ask for every detail the SOP requires
• Triaging incoming deviations by severity, risk and due date, and seeing which past deviations each one resembles
• Starting an investigation from a drafted Ishikawa and 5-Why analysis that cites the relevant SOPs and earlier cases, then confirming or editing the root cause
• Checking whether a new deviation repeats a cause whose CAPA was verified effective, and escalating it for a systemic action
• Assigning corrective and preventive actions to owners with due dates and producing a closure report in the QMS's format
• Working through an overdue deviation backlog by risk and due date, and asking Ask Devia which open deviations have had no recent activity

Devia is a narrow tool aimed at a well-defined, expensive problem: deviation investigations that are slow, inconsistent from site to site and that keep finding the same causes. Its design choices fit GxP: intake driven by the site's own SOPs, drafts that a reviewer must adopt, a recurrence rule that needs both a shared cause and a failed verified CAPA, an attributed audit trail, a validation package, and deployment into the customer's own cloud account. Two caveats matter for evaluation. First, the launch release says Devia works with TrackWise, Veeva Vault QMS and MasterControl, but Devia's own pages describe import from a QMS export and report output, with two-way sync still on the roadmap, so ask how records will flow in and out of your QMS and who keeps them in step. Second, several capabilities the release mentions, such as cross-site trend monitoring, appear as roadmap items on the platform page. A pilot on a single site's deviation history is the sensible way to judge whether the drafted root causes and recurrence matches hold up.

About Devia

Devia is a Zurich-based spin-out of Visium that emerged from stealth on November 11, 2026, after what its launch release describes as a year of pilots with quality teams in live GxP environments. It covers one workflow in depth: the deviation, the record a pharma plant opens when something departs from an approved procedure. The person who found the event describes it in plain words and attaches photos or PDFs, and Devia asks for whatever the site's SOPs require. It proposes severity, risk rating, quality impact and a due date from the company's own rules and similar past events, drafts Ishikawa and 5-Why analyses from the report, the SOPs and the closest past cases, and checks whether the cause has come back despite an earlier CAPA. It then recommends corrective and preventive actions and produces a closure report in the customer's QMS format. Devia proposes and people decide: the team confirms the root cause, a reviewer accepts or rejects each recurrence match, and QA closes the deviation, with every change recorded in an audit trail that Devia says supports 21 CFR Part 11 and EU GMP Annex 11. The main tradeoffs are scope and integration. Deviation management is the live product; trend monitoring, CAPA effectiveness and inspection readiness are on the roadmap. Devia works alongside an existing QMS rather than replacing it, and today it imports deviation and CAPA history from a QMS export and sends closure reports back as documents; two-way QMS sync and MES, LIMS and ERP connectors are listed as next. It deploys into the customer's own Azure or AWS account on Azure OpenAI or Amazon Bedrock and comes with a validation package. There is no public pricing, trial or documentation. It fits multi-site manufacturers and CDMOs whose investigations keep finding the same causes, and fits poorly for teams that need a full QMS or live plant-system integration now.