Skip to content

For kit makers

Labs that pick your kit start from your settings

Your customers pick your kit and import their run. The analysis starts from your targets, controls, call cutoffs and settings.

On this page

What a lab sees when it picks your kit

Researchers find your kit under your name among their presets and pin it to their qPCR start page. Every sample, assay, mix and marker it brings keeps your name while it is unchanged; a lab that edits one sees it lose your name, so a modified kit is never shown as yours. The catalog number and links to your protocol and product page travel with it.

Detection and genotyping kits (pathogen panels, STI, food and veterinary testing, SNP assays). Your customers want to know what is in the sample, not a list of Cq values. Clarida starts each run from your targets, their call cutoffs and your controls, and returns one call for each. A genotyping kit also brings its markers and what its controls should read. A lab can still change a cutoff for its own run.

Quantification kits (expression panels, miRNA). Your kit's assays and analysis settings come with the preset, so each run starts from them. What your customers get back is a number they can act on, with the full analysis behind it when a reviewer or QA asks.

The bench work, in the same record. Your customers can lay out the plate, prepare the mixes and note a pipetting slip in the same experiment as the analysis, so each choice lands in one traceable record.

How your kit gets into your customers' runs

  1. You hand over your kit once. Targets and call cutoffs for a detection kit, the assays and settings for a quantification kit, with the mix and cycling protocol. We build them into your kit's preset, with its catalog number and links to your protocol and product page.
  2. We publish it to the labs you choose, or to everyone. There is nothing for your customers to install and no code to redeem. They can inspect every part of the preset, but not edit it.
  3. Your support team sees a run when a customer sends it. Clarida can't share a customer's run with your team. A customer can export it as RDML or an Excel workbook and send it.

Can you see how your kit runs in labs?

Your validation lab is controlled. The labs that run your kit add instruments, operators and conditions you can't see from the bench, and today you hear about them as a complaint or a return, if at all.

Every kit raises its own questions, so a view of yours across labs is built with you, in a pilot. What it would look at is on the field view page, and what you would see today is in the questions below.

A pilot works out what a view of your kit could follow over time: a new lot reading unlike the one you validated, or no-template controls amplifying more often than they used to. Following a lot needs its number, which Clarida does not record today.

Frequently asked questions

Does Clarida read your customers' run files?

Clarida reads run files from CFX, LightCycler 480, QuantStudio, Rotor-Gene or RDML, with their amplification curves, and a Cq table from any instrument. SYBR Green and probe chemistries come in, singleplex and multiplex: gene expression, genotyping, pathogen detection, miRNA quantification. For a run imported with its curves, Clarida calls Cq itself, so your kit is analyzed the same way on every cycler; a Cq table keeps the instrument's own Cq. How each file comes in is on importing instrument data. Clarida does not analyze dPCR.

Which kits get the most out of Clarida?

Compatibility is rarely the question. Every kit gains the same thing, whatever your volume: your customers start from your analysis instead of building their own. Not sure where your kit lands? Bring it to the call.

Does Clarida work with IVD-labeled kits?

For research use, yes, with one boundary. Clarida is not a validated IVD analysis pipeline and is not part of any kit's regulatory clearance. It is not for the in-vitro-diagnostic interpretation of a sample.

Research use of your kits is what it serves: gene expression, genotyping, pathogen surveillance and similar. Many IVD-labeled kits are also run for research, and for that work Clarida handles the analysis exactly as it does for an RUO kit. If a customer needs a validated diagnostic pipeline, that is outside what Clarida provides today.

How does the branding work?

Researchers pick your kit by name, and your name stays on every sample, assay, mix and marker it brings into the experiment while it is unchanged. The kit's catalog number and links to your protocol and product page travel with it.

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.

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 you publish from a pilot?

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

You sell master mixes, not kits?

Then the shape is a little different: a master mix starts your customers from your cycling protocol and settings, and it has its own page.

Updated

Your first kit, built as a preset with you.

We build its preset from your settings and publish it to the labs you pick. A founder answers within a working day, and the scope and terms are agreed before a pilot starts.

More for partners

All partner pages
  • Master mix makers

    Your mix becomes a preset with its cycling protocol and analysis settings, and each experiment on it starts from them, on the lab’s own instrument.

  • Instrument makers

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

  • Field view

    How your kit, master mix or instrument holds up across labs. Each product raises its own questions, so a pilot sets out with you what the view would show.