METASPEQ Studio
Governed NIR quality control, from spectrum to signed result.
Studio runs your metaspeQ analysers, predicts with signed calibration models, refuses samples it doesn't know, and keeps a record of who did what. It runs on Microsoft Azure, and your team signs in with their work Microsoft account.
METASPEQ Studio for Windows
One installer for the PC beside your analyser. Studio opens in its own window with the same Microsoft sign-in, and the instrument agent runs in the background, so the analyser stays online even when the window is closed.
- Windows 10 or 11, 64-bit
- Administrator rights (installs for all users)
- Hamamatsu detector driver installed
- Outbound HTTPS to Studio and Microsoft sign-in
Available to metaspeQ customers. Our engineer installs and configures it on your instrument PC during onboarding, together with your detector files and sign-in settings.
Request the installerSHA-256 98809FA820D6360E63759AC84138433B69CA2BE158DF901341F014DB59AA5CC0
Already a customer? Email info@metaspeq.com to arrange an install or an upgrade.
The live overview from a demo run on a simulated instrument. Every result passed the input checks; anything outside the calibration range shows OUT OF DOMAIN and carries no value.
QC from anywhere
The scan happens at the plant. The decision can happen anywhere.
The operator scans at the bench. METASPEQ Studio checks the result, records it and sends it to QA. QA reviews and signs from any browser, at home, on the road or in the air.
1. Scan at the bench. Results in under a minute.
- Input checks passed
- Inside the calibration range
- Prediction recorded
- Audit entry chained
- Sent to QA for signature
2. Checked and recorded. Every step on the audit trail.
3. Signed from home. Close out the evening batch from the kitchen table.
Signing always asks for a fresh Microsoft sign-in, wherever you are, and follows your own release SOPs. The analyser, the sample and the operator stay at the plant.
What Studio does
Six jobs, one platform.
Guided acquisition
Dark, reference and sample steps with 1 to 64 replicate scans, age-checked references and an auto-loop.
Safe predictions
Each model applies its own preprocessing. Bad input is refused, and unknown samples get no number.
Automated model building
Record samples, add lab values, and let AI agents search 42 algorithm and preprocessing combinations. The result is a draft for QA.
Signed approvals
Model promotion, batch release and process interventions each need a second person's signature.
Drift alarms
EWMA, CUSUM and Page-Hinkley monitors watch every result and ask the lab for reference values when needed.
Reports and a cited copilotcopilot soon
Pilot results against the lab, result sheets, and a copilot that answers only from your records, with citations. It can't approve anything.
Instrument control
Four steps at the bench. The edge agent does the rest.
- Connect the detector
- Capture a dark frame with the lamp off
- Capture the white reference
- Acquire and predict with the model assigned to the line
Commands queue in Studio and run on the instrument PC. Preprocessing can't be changed at the bench: every model uses the pipeline it was approved with.
The Windows app
Built for a validated instrument PC.
The app shows the same Studio pages your team uses in the browser, so there's no second interface to validate.
Instrument online at a glance
The system tray shows online, offline or a problem, and lets you start or stop the instrument agent.
Preflight before every start
Settings, credentials, runtime, detector files, network and sign-in are checked in order. It stops at the first problem and says which one.
Changes only on purpose
A validated installation changes only when someone installs a new version deliberately.
Secrets stay encrypted
Credentials are encrypted with Windows DPAPI, and the window opens only Studio and Microsoft sign-in.
Sign-in and roles
Everyone signs in with Microsoft. Each role sees what it may do.
Roles are assigned in Microsoft Entra ID. Everyone sees the same menu; controls a role can't use are switched off.
| Role | Can do |
|---|---|
| Operator | Run the instrument, record campaign scans, request batch release |
| Analyst | Everything an operator can, plus campaigns, lab values, model builds, and requesting and executing promotion |
| QA Approver | Sign approvals, reject batches, verify the audit chain |
| Auditor | Read and verify the audit trail; otherwise read-only |
| Admin | Manage the model registry and read everything; can never sign |
The requester can never approve their own request, even with both roles. Signing asks for a fresh Microsoft sign-in.
Security and data integrity
Built so an auditor can check it.
Runs on Microsoft Azure.
Single sign-on with Microsoft Entra ID. No separate Studio passwords.
The edge agent only calls out over HTTPS. Nothing can connect in.
Append-only and hash-chained, anchored to immutable storage. An auditor can verify the whole chain.
Checksummed and signed (Ed25519), in a format that can't run hidden code.
Every spectrum is stored as submitted, including refused ones.
These are technical controls that support your validation (IQ/OQ/PQ). Validation, SOPs and training stay with your quality team.
Getting started
From demo to first scan.
Book a demo
We agree on one material to start with.
Set up access
We add your users and their roles in Microsoft Entra ID.
Install
Our engineer installs Studio for Windows on the instrument PC and connects the analyser.
First scan
Sign in with your work Microsoft account and run your first sample.
Do we need our own Azure subscription?
No. Studio runs in metaspeQ's Azure environment. Your team signs in with their existing work Microsoft accounts.
Can Studio be used on a Mac?
Yes, in the browser. The Windows app is needed only on the PC connected to the analyser.
What happens if the internet drops?
The edge agent needs an outbound connection to send spectra and receive results. Scans don't get a result until the connection is back.
Who can change a production model?
Nobody alone. An analyst requests the change, a different QA approver signs it after a fresh sign-in, and the change is checked again before it runs.