In the product
What it looks like
Screens from the live platform, demo tenant. Click any screen to open it full size.
Approved calibrations issue a numbered certificate rendered from your template — HTML, PDF and Digital Calibration Certificate XML from the same data — with the decision rule, the standards, the environment and the provenance printed on it.
Corrections are never silent. Amendments supersede and revocations recall; every revision is preserved with the signature that bound it, and anyone can verify a certificate number publicly. Inbound DCCs from other laboratories are parsed and imported straight into the asset's history. Outbound DCC XML is validated against the PTB DCC 3.2.0 and D-SI 2.1.0 schemas, signed with XMLDSig and independently verifiable, and certificate PDFs carry a detached CMS/PKCS#7 signature.
Screens from the live platform, demo tenant. Click any screen to open it full size.
A certificate can only be issued from an approved calibration. One certificate per event; a second attempt returns the existing number.
The number comes from the tenant's prefix scheme, sequentially, audited.
Lab identity, accreditation number, signer name and title, per-customer template pinned by the service agreement.
Standards with their own certificates and due dates, environment in words, decision rule statement, TUR, tolerance limits and verdict per point, received date, procedure, scope and traceability statements.
The same data as DCC XML with D-SI units, coverage factor and probability, influence conditions and conformity per result.
An amendment creates revision n+1 with the reason; the old revision stays. A revocation recalls. The verify page shows both.
A quality system is defined as much by what it will not accept. These are enforced in the platform, not in a procedure.
Refused (409).
The second attempt returns the existing certificate number rather than creating a duplicate.
Hard-blocked unless an override reason is supplied; the override is audited and visible.
There is no edit. Amend or revoke, with a reason, and every revision is kept.
Approved calibrations issue a numbered certificate rendered from your template — HTML, PDF and Digital Calibration Certificate XML from the same data — with the decision rule, the standards, the environment and the provenance printed on it.
Toggle between the printed certificate and its DCC XML. Both are generated from the same record — which is why they can't disagree.
An annotated certificate as the platform prints it, mapped to ISO/IEC 17025 §7.8 and 21 CFR Part 11.
Here the certificate is a view of the data. Change the data and you get a new revision with a reason; you cannot get a certificate that says one thing while the record says another.
The DCC lets the customer's asset system import the result, the uncertainty and the conformity without anyone retyping it — and Metroliq imports theirs the same way.
CONDITIONAL, FAIL, superseded and revoked are shown on the public verify page. A certificate that looks cleaner than the data is not a certificate.
Calibration & uncertaintyCalibration & uncertaintyThe verdict is computed, not typed.Every calibration is a numbered event that carries its own points, readings, reference standards, environment and decision rule — and evalua…
Customer portalCustomer portalTheir assets. Their certificates. Their requests.Each customer gets a branded portal scoped hard to their own customer id: instruments with status and due dates, certificate history, quote …
Integrations · API · automationIntegrations, API & automationConfigured, never hard-coded.A visual integration builder with a ten-system catalog plus generic REST and CSV, AI-proposed field mapping with a dry run, signed webhooks …
Compliance · validation · securityCompliance, validation & securityReady for the assessor, the auditor and the inspector.ISO/IEC 17025:2017 and 21 CFR Part 11 are not features bolted on; they are how the record works: a SHA-256 hash-chained audit trail, two-com…The tour runs the working platform, not a mockup. Pilot on your own instruments with your own imported history — we set it up with you, and fixes ship in hours and days, not release cycles.