Synthetic workflow passed
The demonstrated core
A browser-created work order moved through procedure-defined measurements, draft, review, approval, signature and PDF output. The item and order completed after approval and certificate issuance.
- Manual readings and environment inputs—not automatic instrument capture.
- One demo administrator performed and reviewed the work; independent user roles remain to be tested.
- Public verification identifies the issued test record; it does not validate a physical calibration.
Different capabilities; different evidence
Product AI and the website assistant
The website assistant matches questions to curated documentation using server-side keyword retrieval. It is not a general-purpose model and cannot query your lab records. CalBrix Brain, predictive drift, OCR, interval optimization and other product intelligence are not validated for operational advice.
- Only the drift insufficient-history guard was tested.
- Do not infer that every product AI feature runs locally or that no deployment data can leave your network.
- Any AI data-flow and output-quality requirements must be assessed for the intended deployment.
Linked demo records; integrity work remains
Records and audit history
The demo linked the instrument, procedure, readings, environment, review and certificate. Ten historical audit entries have verification mismatches. A fully verified, immutable or audit-ready record system is not claimed.
- Data retention and complete export workflows need testing.
- Customer-owned instrument display is incomplete in some views.
- Qualified personnel must verify traceability and the content of operational records.
Validation pending
Security controls
Selected authentication and signature checks passed. MFA, SSO, tenant boundaries, independent reviewer permissions and recovery require dedicated security testing.
- No independent penetration-test or certification claim.
- No blanket claim of encryption at rest, verified backup recovery or complete security-monitoring coverage.
- See the Security status page for the observed scope.
Assess individually
Integration requirements
Core APIs were exercised during the demo. API-key access, webhooks, Beamex import, other hardware and external services were not validated. The integration-health view has a known error.
- Do not treat a module or API screen as proof of a working connector.
- CSV/Excel migration, DOCX and DCC export need separate testing.
- PDF certificate output is the demonstrated document path.
By assessment, not turnkey validation
Deployment and operations
The demo runs on hosted infrastructure. Private or on-premise requirements can be discussed, but air-gapped operation, automatic scaling, managed backups and identical behavior across deployments are not established.
- Validate security, capacity, recovery and data flows on the target infrastructure.
- Agree support coverage, maintenance and hosting costs in writing.
- Production use follows acceptance testing, not account registration.
Evaluate the fit before operational use.
Use synthetic data first. Production use depends on resolving relevant gaps, validating your procedures and controls, and agreeing acceptance and commercial terms. A demo does not establish metrological validity, compliance or security certification.