The lab itself, on the record.
Freezer and incubator conditions, animal welfare, equipment health and the live device streams behind them — held on the same record as the samples they surround. An excursion stops being an alert about a freezer and becomes a finding about material.

The lab is a physical place, and it is already telling you things.
Sensor connectivity is where lab operations stops being a records problem and starts being a real-time one. The same connection and streaming model that carries instrument output carries environmental and welfare readings — which means an excursion is an event in the sample's own history, not an entry in a separate log that someone reconciles later.
Cold chain & storage conditions
Continuous freezer, fridge, and shipper temperature against the samples actually inside them, so an excursion resolves to an affected sample list rather than a unit ID.
Welfare & activity monitoring
Cage- and rack-level sensing in animal facilities — movement, drinking, and activity change — so a deviation surfaces as an alert during the night rather than an observation at the morning round.
Room & facility conditions
Ambient temperature, humidity, differential pressure, and door events across rooms and suites, held to the same audit standard as any other record.
Hardware-agnostic by design
Sensors and cage hardware come from whoever makes the best of them. The platform is the data and governance layer over that hardware — which is precisely the gap the sensor vendors themselves do not want to fill.
Conditions across the lab and the facility, read continuously and joined to the material and studies they affect.
From a record you query to an operation you watch.
Records tell you what happened. Lab operations needs to know what is happening — and the platform's hot tier is the difference between the two.
- Live streams from device and system activity with no polling on your side
- A change feed that fires whenever the workspace configuration itself changes
- Warm queries over data still in motion, so a threshold is checked as it is crossed
- Every alert and acknowledgement recorded as an attributable, timestamped event
What every platform capability does for the lab estate.
Here is the entire published platform capability set, with what each one is for when what is being watched is the lab itself.
Workspaces & provisioning
AvailableA governed workspace provisioned on sign-up — no installation, no server build — with your team invited into it under their own roles.
Read the docsOne workspace spans samples, instruments, freezers, robots, and rooms, instead of one system per island each with its own login and its own version of the truth. Provisioned at sign-up, with your team invited into it under their own roles.
Deployment options
AvailableEvaluation, Fully-Managed, or Bring-Your-Own-Cloud — three tiers with an identical compliance, audit, and access model.
Read the docsFacility and welfare data is some of the most sensitive data a lab holds. Run in your own cloud tenant and it never leaves infrastructure you control — with the same audit trail, access model, and compliance behaviour as the managed tier.
Granularity of control
AvailableDrafts, commits, undo/redo, proposals, and forks — configuration is versioned like a document, so nothing is permanent until someone says so.
Read the docsA new alert threshold, a rebalanced robot schedule, a changed escalation path — drafted, reviewed, committed, and reversible. Operational change stops being a deployment and becomes something a lab manager can make and a QA reviewer can read.
API & connection nodes
AvailableTwo integration patterns: an API node that polls a system on a schedule, or a Connection node that receives events as they happen.
Read the docsThe freezer, the incubator, the cage rack, the robotic arm, the LIMS, and the badge reader all attach through the same two node types — polled or pushed. OPC UA and SCADA, which most lab automation and building systems speak natively, are roadmap; today those systems connect through their REST, file, or broker interfaces.
Cold, warm & hot data
AvailableDownload the history, query what is flowing now, or subscribe to a live stream and a configuration change feed.
Read the docsCold gives you a year of temperature history for an excursion investigation. Warm answers which units are drifting right now. Hot pushes a live feed to the operations screen, and a change feed fires whenever the workspace configuration itself changes.
Custom nodes & extensibility
In progressA pluggable node model behind every connection, query, and dashboard. First-party node types today; customer self-service authoring is roadmap.
Read the docsRobotics and instrument vendors ship islands, and a new node type is how an unintegrated arm, reader, or cage sensor becomes a first-class participant in the same flow as everything else. Built by our team on the shipped node model today; self-service authoring is roadmap.
the assistant, the AI operator
AvailableA workspace-aware assistant with context on your real connections and flows. It drafts proposals for review and never mutates anything directly.
Read the docsAsk which freezers drifted last night, which robot runs stalled, or which racks stopped reporting — and get an answer grounded in your actual workspace. The assistant drafts new monitors, queries, and dashboards as proposals for a person to approve.
MCP server
AvailableAny MCP-native model can read, query, and propose. There is no accept tool — proposals only ever land through a person in the workspace UI.
Read the docsAny MCP-native model can read the lab's live state, run queries across it, and propose new monitoring, but cannot enact anything. The absence of an accept tool is the architecture, not a policy — which is what makes agents usable in a regulated facility at all.
Roles & access administration
AvailableNamed access rights, bundled into custom configurations, assigned to people — with Viewer/Editor/Admin as the starting default, not the ceiling.
Read the docsA vivarium technician, a facilities engineer, a study director, and an external auditor each need a different lab. Named access rights bundled into custom configurations give each of them exactly their own, and every assignment is itself audited.
Audit trail & data integrity
AvailableEvery governed mutation produces its own compliance evidence structurally — attributable, timestamped, append-only, and mapped to an ALCOA+ principle.
Read the docsThe audit machinery is already load-bearing for sample custody: attributable, timestamped, append-only, each event tagged with the ALCOA+ principle it satisfies. Monitoring runs on that same spine, so an excursion and its acknowledgement are evidence rather than a side channel.
System upgrades
RoadmapThe planned linked-environment model — promote a change from testing through staging into production on your own change-control steps.
Read the docsPlanned: promote a monitoring configuration or workflow change from a testing environment through staging into production on your own change-control steps — so a change to a facility's alerting is as controlled as a change to a study.
Validation data & custom reporting
RoadmapAudit-trail export today, with broader validation-data downloads and custom compliance reporting planned.
Read the docsAudit-trail export is live today. Broader validation-data downloads and custom compliance reports and dashboards over operational and environmental data are planned.
Put the lab on the same record as its samples.
The conditions, the equipment and the material they hold, in one place — so a question that crosses them has an answer rather than an investigation.