What people ask before a pilot. If yours is not here, ask it from inside the demo — the intake form on the last screen goes straight to us.
The product is in use and moving fast: features and fixes ship in hours and days. The record is not moving — the audit trail, signatures and certificate revisions are immutable by construction. Expect rough edges, fast fixes and a direct line to the people building it.
Nothing during the beta. Every tenant is on one plan with every module on. Pricing will be introduced with notice; beta customers will not be surprised.
No hard limits are enforced in the beta plan. Tell us your volume in the pilot request so we size the workspace.
It is yours. An audited full-tenant export is a built-in function, and certificates leave as PDF and DCC.
Bring one lab and your real history. Three onboarding questions configure the workspace; the import engine maps your export and shows you the mapping before anything loads. We set it up with you.
Yes: spreadsheets and full exports from legacy calibration systems, including history, with original certificate numbers preserved. The run is idempotent and audited; phantom records are rejected.
A configured workspace exists before your first login ends. A realistic pilot on real history is a matter of days, most of it your review of the mapping and the templates.
No software does. Accreditation is granted to your laboratory by your accreditation body. Metroliq is built so the records, certificates, uncertainty, decision rules and quality system meet the standard's requirements, and the readiness self-check tells you what an assessor will ask for. See the compliance page.
The platform implements the Part 11 controls — validated system, two-component signatures bound to meaning, secure time-stamped hash-chained audit trails, authority checks, retention. Compliance is a property of your validated use; the validation kit gives you the evidence.
You get our supplier evidence — functional specification, test specification, IQ and a verification suite that executes in your own instance and signs what it found — plus the workspace where you author your URS, your risk assessment, your verification strategy and your validation summary report. The supplier half is ours. The validation of your intended use is yours, and the workspace is built to make it take days rather than months.
Nothing. It drafts specifications, forms, budgets, investigations, CAPAs, mappings and reviews. A person approves and signs. The maths — uncertainty, TUR, guard bands, verdicts, intervals — is deterministic code.
No. Prompts contain only the record in context and are sent to the model provider through our gateway; the ledger records what was sent (by hash) and what came back.
The builders are optional per workspace. The deterministic engine, the signatures and the audit trail do not depend on them.
As a cloud service behind Cloudflare with TLS 1.3 and strict certificates. On-premise deployment is available on request for contracted customers. Details on the security page.
Not yet. The controls are documented on the security page and can be reviewed in a pilot; certifications are on the roadmap and will be announced when they are real, not before.
Field capture works offline through a device outbox and syncs when a connection returns. Signatures are never applied offline; they are applied at sync by the user present.
Inside the product: the built-in assistant answers questions about your data and where things are, and escalates to a human with the context attached. Beta customers talk to the people building it.
Hours and days, not release cycles. Every change ships with the test gates green and the OQ re-runnable.
Yes, and in the beta it is the normal way the product grows. Tell us the pain, not the button.
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.