V5 Ultimate vs Matrix Requirements

Matrix Requirements is two modules: MatrixALM covers design controls, requirements, risk (ISO 14971), verification and validation matrices, and IEC 62304 software lifecycle. MatrixQMS covers document control, training, CAPA, complaint, audit and change control. It is not an MES — Device History Records live in a separate system. V5 Ultimate is one platform: DMR-locked routing, per-serial eDHR, calibrated tool integration, WMS, and QMS on the same stack.

This is Matrix's flagship strength. The RTM is deeply configurable — categories per project, custom item types, XML export, side-by-side design-input / design-output / verification / validation views. V5 covers the same regulatory surface area with less UI depth on the ALM side, but the RTM is native to the execution layer — the same requirement that proves a URS is tested drives the qualification of the manufacturing system that keeps it provable.

Matrix is one of the best tools on the market for IEC 62304 evidence — item types for software requirements, software architecture, unit + integration + system testing, SOUP, anomalies and problem reports all cross-linked. V5 covers IEC 62304 as part of its regulated-software framework but does not match Matrix's ALM depth. If the product is standalone SaMD, Matrix is often the right answer; if the product is a device with embedded software plus manufacturing, V5's unified stack usually wins.

Matrix does not run the shop floor. The DHR is assembled after the fact from MatrixQMS records + MES exports. V5 is the build environment: the routing references the locked DMR revision, only that revision is visible on the operator kiosk, torque and vision tools are calibration-gated, the UDI label prints at the workstation, and the eDHR locks the moment final inspection signs — no end-of-batch reconstruction.

Matrix is cloud-hosted on AWS with an on-premises option available for enterprise customers. V5 also ships as Lovable Cloud and V5 Ultimate On-Premises (containerised, air-gap capable, customer-owned keys and data). On-prem parity is real; the operational difference is that V5's on-prem includes the execution layer, so a fully air-gapped device manufacturer can run both design and production on the same on-prem stack.

Matrix has shipped AI-assisted requirement drafting and risk suggestion inside MatrixALM. V5's AI layer is regime-aware — for a device tenant it speaks DHR / DMR / UDI / DI+PI / GUDID / EUDAMED and uses ISO 13485 + 21 CFR 820 templates. Both vendors are explicit that AI does not e-sign; a qualified human always signs.

Matrix quotes per user per month with tiered bundles for ALM only, QMS only or both. V5 publishes per-user / month for Cloud and an annual term licence for On-Premises with a free trial. For a 10-person SaMD team Matrix is often cheaper; for sites with 50+ floor operators V5 is usually cheaper end-to-end because it replaces both Matrix and a separate MES.

Standalone SaMD and IVD companies whose product is primarily software, teams that want maximum ALM configurability (custom item types, custom categories, XML export), or organisations that outsource all manufacturing and only need the ALM + QMS layer.

Device manufacturers who own their production line and want eDHR self-building per serial, companies who would otherwise pay for Matrix + a separate MES, on-prem / air-gap requirements including the execution layer, or combination-product manufacturers who need pharma BMR + device DHR on one stack.