Devia Emerges From Stealth With AI Agents for Pharmaceutical Quality Investigations

A pharmaceutical quality investigation has to do more than close a ticket. It must explain what went wrong, establish the cause, document the response, and show whether the same problem has happened before. Devia, a Zurich-based Visium spin-out emerging from stealth, is applying AI agents to that chain of work while keeping quality professionals responsible for the decisions.

The company says it spent a year piloting the system with quality teams in live GxP environments, including work with a major contract development and manufacturing organization. GxP is the umbrella term for regulated good-practice requirements across areas such as manufacturing, laboratories, and clinical research.

Devia’s launch targets biopharma manufacturers, contract development and manufacturing organizations (CDMOs), and contract research organizations (CROs). Its premise is that an agent can assemble evidence and draft investigative work without replacing the people accountable for approving an investigation.

From an Initial Report to a Supported Root Cause

In pharmaceutical operations, a deviation is a departure from an expected procedure, process, or requirement. Investigating it can require staff to reconstruct an event from production records, standard operating procedures, attachments, and earlier cases scattered across systems.

Devia describes an agent that structures the initial report, brings relevant evidence together, suggests possible root causes, and drafts corrective and preventive actions, or CAPA. Operators, investigators, and quality assurance staff review and approve the work as it progresses.

The company’s platform documentation adds detail about that process. Intake questions follow the organization’s own procedures, and the system can read attached photographs and PDFs. For root-cause analysis, it drafts Ishikawa diagrams and 5-Why investigations using the event report, procedures, and relevant historical deviations.

These methods provide structure, rather than proof by themselves. An Ishikawa analysis organizes potential contributing factors; a 5-Why investigation follows a chain of explanations toward an underlying cause. The important question is whether each proposed explanation is supported by evidence that a qualified investigator can examine.

“Quality teams don’t need another system of record. They need an agent that does the groundwork, so their experts can focus on the root causes that matter,” said Pascal Rodriguez, Devia’s CTO.

Learning From Past Cases Without Automating the Verdict

Historical investigations become useful when they help staff recognize a shared cause, rather than simply find a report with similar wording. Devia says it compares new root-cause proposals with previous cases and keeps its own experts’ reviewed decisions available for future investigations.

The website distinguishes a cause that keeps appearing without an effective intervention from one that returns after a corrective action was verified as effective. That distinction can change the investigation: an organization may need to address a previously untreated systemic issue, or explain why a supposedly effective fix failed.

Devia presents these comparisons for human review. Staff accept or reject the suggested relationships, and the resulting decisions form part of the record. This makes the review process central to the product’s usefulness: an unsupported AI suggestion should not silently become the precedent for the next case.

According to the launch release, users in customer pilots spent half as much time investigating deviations. Devia has not disclosed the pilot sample size or evaluation methodology, so the figure represents a company-reported result rather than an independently established performance benchmark.

Working Alongside Existing Quality Systems

The launch names established quality platforms such as TrackWise, Veeva Vault QMS, and MasterControl as systems customers already use. Devia’s integration documentation makes the current implementation more specific: historical deviations and CAPAs are imported from QMS exports, procedures are brought in as documents, and completed investigations produce closure reports matching the customer’s QMS format.

That is different from a fully synchronized connection to every operational system. Direct connectors for quality management, manufacturing execution, laboratory information management, and enterprise resource planning are listed as upcoming capabilities. Broader trend monitoring and CAPA-effectiveness features also appear on the platform roadmap, alongside inspection-support tools.

For deployment, Devia says the platform can run in the customer’s Azure or AWS account, in a chosen region, using Azure OpenAI or Amazon Bedrock. Its documentation states that customer records are not used to train models for other organizations. It does not identify a proprietary foundation model; the product’s described value lies in applying AI to company procedures, historical cases, and controlled review workflows.

Traceability Is Part of the Product, Not an Afterthought

The need for rigorous investigations is well established. The FDA’s review of drug inspection observations identifies failures to investigate discrepancies and product failures among recurrent manufacturing-quality problems. Faster drafting alone does not resolve that issue if the evidence and conclusions remain weak.

Devia’s security documentation describes individually identified users, role-based access, single sign-on, encryption, and time-stamped records of changes and approvals. It also says the company supplies validation documentation to support customers’ computerized-system validation or assurance work. These are capabilities intended to support regulated use, rather than a substitute for the customer’s own validation and quality responsibilities.

The launch also references EN 18286:2026. The European Commission confirms that the harmonized standard addresses quality-management requirements for providers of high-risk AI under Article 17 of the AI Act. Devia says its approach follows those principles; the announcement does not establish that the product has been independently certified to that standard.

Devia’s opportunity is to reduce the time investigators spend collecting and organizing information while making the reasoning easier to inspect. Its more consequential test will be whether quality teams can consistently turn that assistance into stronger investigations—and corrective actions that prevent the same manufacturing problem from returning.