# Your customers’ runs, from raw curve to normalized result

> If Clarida reads your cycler’s run files, it calls Cq from the curves and takes the run to normalized, QC-checked results. A pilot starts with one model.

Source: https://clarida.bio/partners/instrument-makers
Updated: 2026-11-09

[For instrument makers](https://clarida.bio/partners)

If Clarida reads your cycler’s run files, it calls Cq from the curves and takes the run to normalized, QC-checked results.

A partnership, set up with you

[Plan a pilot](https://clarida.bio/talk-to-us?topic=pilot)

## Where your software stops, and Clarida starts

Your software calls Cq when the run ends, and much of it goes further. Clarida takes your customers' analysis deeper: reference-gene validation, efficiency-corrected normalization, QC and statistics.

If Clarida reads your cycler’s run files, it calls the Cq from the curves itself, so every step after the run rests on one method. Today that analysis runs in Clarida, under its own name.

## The analysis your customers would run

It rests on published work: geNorm, Jo Vandesompele's method for choosing reference genes, and qBase, Jan Hellemans' framework for relative quantification. Both co-authored the MIQE guidelines, and both work on Clarida: Jan as a co-founder, Jo as its scientific advisor.

- **Cq calling a customer can check.** Baseline and threshold applied the same way to every well of a run imported with its curves.
- **QC and outlier handling.** Replicate agreement, positive- and negative-control checks, and outlier flagging.
- **Reference genes and normalization.** geNorm reference-gene selection, efficiency-corrected relative quantification and inter-run calibration.
- **Statistics, reports and exports.** Group statistics, reports as PDF and HTML, and export to an Excel workbook and to RDML, the open format for qPCR data.
- **The full workflow, not only analysis.** Your customers design the run, capture the bench work, analyze and report in one place, so a result arrives with its plate, protocol and QC attached.

## What you cannot see once it ships

Your validation ran on instruments in your own lab, on protocols you chose. After the model ships, you see it through service calls, returns and qualification visits. Each says whether an instrument meets its specification; none says how its results hold up in the labs that run it.

- **No common yardstick.** Two of your units can give one sample a different Cq, and so can two ways of analyzing the same curve. From the results labs report, you cannot tell which it was, because no single method runs across your fleet.
- **Lab and bench conditions.** Each lab brings operators, plastics, protocols and a room your validation never met. Replicate spread on a lab's unit can widen without any of it reaching you.
- **Drift you cannot see yet.** A qualification visit checks the block against its specification on one day, often once a year. A slow change in the months between shows in no single run, and remote monitoring, where a unit has it, reads the instrument's diagnostics rather than its results.
- **Your box, or their bench?** A late result can come from the hardware, or from a lab's handling, and each needs a different fix. A complaint brings you the symptom, often without the run behind it, and only when a lab chooses to file one.

Every instrument raises its own questions, so a view of your fleet across labs is built with you, in a pilot. What it would look at is on [the field view page](https://clarida.bio/partners/field-view).

## How a pilot with one model runs

1. **Send a run file from the model.** Clarida reads run files from CFX, LightCycler 480, QuantStudio, Rotor-Gene or RDML today. If your model writes another format, reading it is the first thing the pilot looks at.
2. **Your customers import their runs.** They bring their run files into Clarida, with nothing to install. On a LightCycler 480, [Porta](https://clarida.bio/security/porta), Clarida's lab connector, reads finished runs straight from the instrument's database.
3. **Your own software is a separate conversation.** Clarida inside your own software, under your name, or running in your own cloud isn't built yet. We build it with a partner who needs it; a pilot scopes it.

## Frequently asked questions

### Does Clarida read your run files today?

Clarida reads run files from CFX, LightCycler 480, QuantStudio, Rotor-Gene or RDML today, with their amplification curves, and a Cq table from any instrument. For a run imported with its curves, Clarida calls Cq itself, so the result does not depend on any one instrument's Cq algorithm. Clarida does not analyze dPCR. If your platform writes a raw format Clarida does not read yet, bring a file to the call.

### What would you see from your customers' runs?

Nothing, today: no maker receives statistics from labs' runs. What a field view would show, and on what terms, is set down in a pilot before the first statistic.

### What can field data tell you, and what can't it?

It would tell you how closely replicates agree within each experiment: precision inside one run, in many labs. It would not tell you how runs, labs or months compare, because each lab runs its own samples and assays. That needs one control, from you, run the same way everywhere, and a pilot can set one up.

It would not tell you about accuracy, how close a result sits to the true quantity, because the samples labs run are uncontrolled and unknown. Any "how much" question needs a known standard or control, which field data on its own does not carry.

### Is this a validated IVD analysis pipeline?

No. Clarida turns qPCR data into results for research use. It is not a validated IVD analysis pipeline, is not part of any instrument's regulatory clearance, and is not for the in vitro diagnostic interpretation of a sample. It serves research use of your platform: gene expression, genotyping, pathogen surveillance and similar.

### Where does the analysis run?

In the cloud, with no install and no version on premises. A lab that has to keep its runs on site is not a fit, and that is worth raising early.

### Can you see how your instruments compare to a competitor's?

No. A pilot looks at your own product only.

### What can you publish from a pilot?

Nothing yet: there is no field data on your fleet. What a pilot produces, and what you may publish, is agreed before it starts.

Updated November 9, 2026

## Start with one instrument model and its run files.

We look with you at what Clarida reads from that model, and what a pilot would cover. A founder answers within a working day, and the scope and terms are agreed before a pilot starts.

[Plan a pilot](https://clarida.bio/talk-to-us?topic=pilot) · [Talk to a founder](https://clarida.bio/talk-to-us?topic=pilot&channel=write)
