Graph-Native Data Foundation
Labbit connects every sample, material, instrument, result, and workflow step in one data model, so you can follow the relationships behind your work and see exactly how each record was produced.
THE PROBLEM
A single sample touches reagent lots, instruments, locations, analysts, and SOP steps. In most labs that story is split across the LIMS, instrument software, spreadsheets, and paper. Each holds part of it, but the context of how the work was done, which step produced a result and under which version of the process, is often captured somewhere else or not at all.
That gap shows up when the questions get harder: an out-of-spec investigation that keeps widening, an auditor asking for a sample's complete history, a new assay that needs a new kind of entity. Teams end up chasing context instead of following it.
CAPABILITIES
Samples, materials, instruments, results, and workflows share one connected model. Start from any record and follow its connections, including in directions the original question didn’t anticipate, as an investigation expands.
Labbit captures relationships as workflows execute. Each record links to the workflow step, user, and signature that produced it, and every change creates a new revision linked to the one before. Your data stays connected to how it was produced and how it changed.
The graph foundation lets you extend entity types and relationships as assays and processes change. New structure is configured, reviewed, and deployed through change control, so the model grows with your lab and your validated state stays documented.
Labbit represents data and relationships in RDF and records provenance following the W3C PROV standard. These are established, open models for describing relationships and provenance, which supports interpretation, exchange, and reuse beyond Labbit.
HOW IT WORKS
01
When a workbook is committed, the entities involved and their relationships are recorded as new revisions, linked to the workflow task that produced them.
02
Relationships accumulate across samples, lots, instruments, and sites, building a genealogy that grows with every run.
03
Search any record to see what it's connected to, then open its revision history to see who changed what, when, and why.
IN PRACTICE
DIAGNOSTIC TESTING
Emerging assays with complex genealogy
DIAGNOSTIC TESTING
Block, slide and stain tracking end to end
GMP BIOMANUFACTURING
Vein-to-vein COI and batch execution
GMP BIOMANUFACTURING
Check-weigh dispensing with genealogy
What is a graph-native LIMS?
A graph-native LIMS uses a connected data model in which samples, materials, instruments, results, and workflow steps are entities linked by relationships. In Labbit, those relationships are captured as work executes, so investigations, genealogy, and audit reviews can follow connections from record to record.
What kind of database does Labbit use?
Labbit runs on an RDF graph database. Provenance follows the W3C PROV standard, so lineage is described with open, established models rather than a proprietary format.
Is a graph database better than a relational database for a LIMS?
Both can model relationships, and both can support regulated work when they're designed well. Labbit's advantage comes from how its graph works together with its workflow engine and revision model: relationships and provenance are captured as part of executing the work, so the context is already there when you need it.
How does Labbit protect record history?
Labbit is designed so records are never overwritten. Each change creates a new, complete revision linked to the one before it, attributed to the user who made it and time-stamped by the system.
Can the data model change as our assays change?
Yes. Entity types and relationships are part of your Labbit configuration. Changes are reviewed and deployed as versioned changesets, and each deployment is recorded with who deployed it and what changed. Configuration and validation activities still apply, scoped to what changed.
Can we use our Labbit data in our own analytics tools?
Yes. Data Export delivers files to cloud storage your organization manages, and Labbit's APIs provide programmatic access. See Analytics for details.
SEE IT ON YOUR DATA
Follow a sample end to end
Bring a sample history your team has had to piece together. We'll show you its
connections, revisions, and workflow context in Labbit.