FOR CORE FACILITIES
One method every group runs. One record that protects your facility.
Every group works the same validated way and starts from your presets, then keeps its own data and its own conventions, from a first-year student to a visiting PI. One workflow your reviewers already trust, across every bench.
What your facility is judged on
Your reputation is the service. One bad result can undo it.
Twenty groups, twenty ways to normalize, and no authority to standardize any of them.
One group in Excel, one in R, one in the instrument software, so no two results match.
Defensibility lives in a folder of Excel files and your memory, until a PI's reviewer asks how a number was produced.
Your staff spends its week answering "how do I interpret this" instead of running the service.
Unify the workflow, defend every result, free your staff’s week.
Every group starts from a proven design, not a blank sheet.
Build a preset once, and every group starts from it, then adapts it to its own question.
Groups run their own instruments and note what they see, so context travels with the data.
Every group runs the same normalization, QC and inter-run calibration, on one platform, recorded.
A self-contained, MIQE-aligned record you hand the PI. When a reviewer asks, it reopens.
Your groups’ data
No group ever sees another’s data. Not even you.
Each group works in its own workspace, and workspace membership is the only way into a group’s experiments, samples, assays and results. That holds under one facility account, and it holds for you as the account owner: no membership, no read.
What the account shares is the billing and capacity pool and the system catalogs of instrument types and standard protocols every group can build on. Never a group’s data. So the rival groups down the hall run on one standardized platform without ever sharing their work with each other.
Data is encrypted in transit and at rest, and hosted in the EU, so a group’s unpublished results never leave its own workspace. Your facility gets one consistent method across every group, and the governance arrangement for your institution is a conversation we are glad to have.
The D-DEAR method
Set the method once. Every group runs it their own way.
One continuous workflow every group runs the same way, so what you hand back stays comparable across users, projects and years.
That’s D-DEAR: Define, Design, Execute, Analyze, Report. Everything except the cycler.
This is where an experiment gets its context before any plate: a clear goal, the background behind it, and the papers that justify the choices. Each experiment frames its own question, since a liver expression study and a pathogen panel are not the same experiment.
Because the context lives with the experiment rather than in a separate document, it travels downstream to the record a PI can defend. So months later, when a reviewer asks why a run was set up a certain way, the answer is on the record, not reconstructed from memory or lost when a student leaves.
Curate what a good run starts from: validated assays with their acceptance criteria, a reference-gene panel scored with geNorm where your facility chooses which genes to keep, and the mix and protocol, saved as a preset. A group building a run in that area pulls your preset instead of assembling it from scratch.
From there each group designs the rest of its own experiment and keeps its own data separate, so you share a validated starting point without imposing one rigid design on twenty different research questions. And a reference-gene panel validated in one tissue is not assumed to transfer to another, so groups re-validate where the biology demands it.
Because the design is recorded, well positions, controls and reference-gene choices stay visible and traceable into every group’s analysis, instead of becoming an undocumented source of variation you get blamed for later.
A materials checklist, mixes at the calculated volumes, and a guided plate fill to follow at the bench, then the run starts on your own instrument. Clarida guides and records here, it does not pipette or drive the cycler.
As a plate is loaded, anything visible on a specific well, a bubble, a short pipette, a cloudy reagent, can be noted, and that note stays attached to the well.
So later, in analysis, that note sits next to the measurement. Whoever analyses it can tell a bench artifact from real biology without a back-and-forth thread, and an exclusion is one they can explain rather than reconstruct.
Groups bring raw amplification curves and Clarida can call Cq itself, with more than one established method to choose from, or they start from the Cq values their instrument produced. The imported Cq is never overwritten.
From there every group works with the same methods: Cq processing, reference-gene normalization scored on geNorm or a global mean, efficiency-corrected quantification, per-metric QC that surfaces outliers without dropping them for you, and inter-run calibration across the thousands of plates a core runs over operators and years. A group that starts from your preset starts from your settings, and every step is recorded, so what changed is always visible.
That consistency is the load-bearing part for a facility running many operators: the result no longer depends on which spreadsheet a user built or which step they remembered.
When a PI's reviewer asks how a number was produced, the exact analysis reopens: the method, the settings and the data behind every value, already on the record instead of reconstructed from a student's laptop.
The methods and settings are captured the way MIQE asks you to report them, so the PI's methods section is complete and every result traces back to how it was produced.
The record carries its own data inside it, which is why it still works months later: it opens and re-analyses without Clarida, a database, or the software that made it. That self-contained, versioned record is what your facility hands to each PI, and it is what makes your service defensible.
Why switch
One shared workflow, and results that finally line up.
Right now your service is twenty relays. Each group frames its run in a notebook, plans the plate in Excel, calls Cq in whatever instrument software it already trusts, normalizes in its own way, and builds the figure in GraphPad Prism. Every handoff is a chance to drop the baton, and every group drops it differently, so nothing your facility hands out is done the same way twice.
Clarida does not ask your groups to abandon the instrument software they trust. It is the workflow around the run instead: the design before the plate, and the analysis after it, efficiency correction, normalization, QC and inter-run calibration, done the same way every run and recorded. One shared, defensible workflow in place of twenty inconsistent relays.
Today, times every group
Exported, reformatted, and pasted between apps that never talk.
With Clarida
- Definegoal & context
- Designyour facility’s standard
- Executeguided benchwork & notes
- Analyzesame method, every group
- Reporta record each PI can defend
One record, from the question you framed to the figure you publish.
Methods that hold up
geNorm, efficiency correction and MIQE-aligned reporting, from the team that wrote them, so what your facility hands out holds up.
The path of least resistance
Groups get a faster, cleaner analysis than the tools they cobble together, so they choose it. You make the good path the easy one.
Free your staff's time
The repetitive setup, analysis and interpretation emails shrink, so a fixed team serves more groups without more headcount.
From the source
Trust the analysis, because they wrote it.
Clarida comes from the team behind geNorm, qbase+ and the MIQE guidelines the field reports to. The methods you rely on stay in the hands that defined them, now maintained and moved to the cloud.
28,000+
citations of the geNorm and qBase methods
Since 2007
building qPCR analysis software
MIQE
the reporting standard, co-authored by the team
For the facility
Be the one they can't afford to cut.
The rigor your facility hands out
When a reviewer asks how a number was produced, the exact analysis reopens with its methods on the record. Your facility handed the group a report that holds up.
Serve more groups on the same budget
The repetitive setup, analysis and interpretation load drops, so a fixed team covers more of the institute. You scale without the headcount you will not be given.
Comparable across every group and year
Every group works on one platform with the same validated methods, recorded, so results line up across users, projects and years. The method is the constant, not the answer.
Step in when a group needs you
A group can invite your staff into its workspace to run or check the analysis together, on one shared record, not an email thread. No standing access to any group that did not invite you.
The method outlives the people
When a student rotates out, the analysis and the reasoning stay in the workspace, so the facility’s work does not walk out the door at the end of a thesis.
Ready to set your facility up?
One facility account, every group in its own workspace, your presets ready to share. We will shape the deployment and the pricing around the groups you serve.
Set up your facilityQuestions, answered
No. Each group works in its own workspace, and access is gated by workspace membership, nothing else. One group never sees another's experiments or results, even under the same facility account, and even you as the account owner have no read into a group's data.
The only things shared across the account are the billing pool and the system catalogs of instrument types and standard protocols. Never a group’s work.
No, and you should not have to. You build validated presets once, your assays, a geNorm-scored reference-gene panel, the mix and protocol, and each group starts from the preset for its area, then designs the rest around its own question.
So you share a validated starting point without policing twenty different research questions, and each group keeps its own conventions and its own data separate. A panel validated in one tissue is not assumed to carry to another.
Clarida is instrument-agnostic and reads qPCR and RT-qPCR data from the major platforms, whichever cyclers your facility runs. Start from the Cq values an instrument called, or bring the raw amplification curves and let Clarida call Cq itself, using single-threshold, SDM or LinRegPCR. Your imported Cq is never overwritten.
It also reads qbase+ files, so a group with legacy analyses can bring them across rather than start from zero.
Reference-gene stability is scored with geNorm so a group can drop an unstable gene, or use global-mean normalization. Quantification is efficiency-corrected, group results come back as a geometric-mean fold-change with confidence intervals and Benjamini-Hochberg across genes, and the tests are the ones qPCR papers use: t-tests, Wilcoxon, Mann-Whitney, one-way ANOVA and Pearson or Spearman.
Every step is recorded and the report carries its own data and methods inside it, so a PI or a reviewer can reopen the exact analysis months later and re-analyse without Clarida. Nothing is a black box.
The analysis lives in the group's workspace, not on a departing student's laptop, so when they move on the record stays and reopens exactly as they left it.
The next student picks up the same analysis instead of rebuilding it, so the facility’s method and the group’s work outlive every rotation.
A facility runs as one account and one budget, with capacity that scales across all your groups and per-group workspaces kept isolated. You bring groups in as they are ready.
Pricing is a short conversation shaped around how many groups you serve and how you want to roll it out, not a fixed list you have to fit into.
Analysis today is qPCR and RT-qPCR, read from the major platforms. dPCR support is on the roadmap.
If your facility runs dPCR alongside qPCR, raise it in a walkthrough and we will be straight with you on timing.
Become the core they can’t do without.
Tailored to your groups, running in days, not a procurement saga.