Self-Driving Lab OS

Autonomous Execution,Human Approval.

Indus executes protocols and instruments through open laboratory standards. Every run is recorded and re-verifiable by replay. Every physical action stays inside a declared safety envelope, approved by a named human.

Open protocolsBack to overview
Execution Layer

Protocols, Instruments, and Runs You Can Replay.

Every run records its protocol, environment, and safety envelope, so results re-execute to equivalence under recorded conditions.

Versioned protocols

Numbered protocols with safety summary, stopping rules, instrument requirements, reagents, and per-step approval gating.

Backend adapters

Live Bluesky dispatch and deterministic mock replay ship today. SiLA 2, AiiDA, and custom backends stay planned registrations until external endpoints are connected.

Safety envelopes

Per-instrument min, max, and allowed-value rules halt out-of-range requests and lock the instrument under critical safety events.

Replay-to-equivalence

Deterministic steps require bit-equivalence, LLM steps require a tool-call trace and semantic overlap, and retrieval steps require ranked-source overlap above a published threshold.

Drift envelope

Per-run drift envelope (max, mean, std) is computed and ledger-anchored. Replay equivalence is committed under recorded conditions, not bit-identical determinism.

OCI + SBOM pinning

Each instrument and each run records the OCI image digest plus a CycloneDX or SPDX SBOM hash, so the environment is part of the bundle, not a side note.
Open Standards

Live Adapters and Planned Registrations, Labeled Apart.

Live adapters and planned registrations are labeled separately, so procurement evidence never implies that an unconnected integration is live.

BlueskyMock replayRO-CrateBagItOCICycloneDXSPDXSiLA 2 (planned)AiiDA (planned)Stencila (planned)Quarto (planned)JATS (planned)MCP (planned)ORCID (planned)ROR (planned)RAiD (planned)DataCite (planned)IGSN (planned)Handle/ARK (planned)
Planned Surface

Self-Driving Lab Connectivity.

Self-driving lab orchestration is a planned layer, not a current commitment. Today the mock adapter records deterministic-simulation observations, so the run-bundle contract holds even when the lab is not yet connected. As anchor institutions deploy Bluesky, SiLA, or AiiDA endpoints, those backends light up without changing the protocol contract.

Indus Execution

Make Every Run Replayable.

Open the protocol library in the workspace, or join the institutional beta to bring replayable execution to your lab.

Open protocolsJoin institutional beta