Benchling Instrument Integration

Splashlake connects thousands of lab instruments to Benchling, so results land in your notebook entries as structured data, linked to the right Registry entities and Inventory containers. The same platform brings in your LIMS, CDS and other lab systems, giving scientists one view of all their data with Benchling at the center of the experimental record.

BenchlingThousands of instrumentsAnIML open standardDays, not months
Why it matters

Why Do Benchling Teams Need Direct Instrument Integration?

Benchling is where your scientists design experiments in notebook entries, register sequences and custom entities in the Registry, and track samples in containers and plates across Inventory. The data that completes those entries still starts life on an instrument PC.

Without integration, scientists export a file, tidy it in Excel, paste it into a results table, then match each row to the right entity and container by hand. That costs bench time, risks a mismatched barcode or a missed row, and keeps results out of reach until someone finds time to upload them.

Most labs also run more than one system. Benchling may hold discovery work while a LIMS manages QC samples and a CDS holds chromatography data. Scientists end up comparing results across tools that were never designed to talk to each other.

Splashlake solves both problems. Requests and workflow tasks in Benchling become worklists on the instrument, and results come back as structured rows in the right results table or run, linked to their entities, batches and containers. Because Splashlake also connects to your LIMS, CDS and other sources, scientists get a complete picture of their data, with Benchling as the experimental record.

Find Out More
The Splashlake approach

How Does Splashlake Connect Instruments to Benchling?

Splashlake appears on the Benchling user interface as a Canvas app, making it easy to add instrument interactions directly to the notebook. Instruments plug into Splashlake once, using standard data conventions instead of custom scripts, mapping tables or parsing rules. Splashlake then writes to Benchling through its REST API, so data arrives in the results tables, runs and Registry entities your admins have already defined. Your Benchling configuration stays exactly as it is; Splashlake fits the data to it.

There is no Benchling App to build for each instrument, no parser to maintain, and no rework when an instrument vendor updates its software. Splashlake is built for labs that want a wider instrument library, an archive-grade open data standard, and one data layer across every system they run. Benchling stays at the heart of the experimental record either way.

Find Out More
Scientist recording results at a laboratory bench
one Benchling tenant / thousands of instruments / every lab system
What we manage

Which Types of Scientific Data Can Splashlake Manage Within Benchling?

Splashlake handles six types of scientific data and puts each one where Benchling users expect to find it, with a full AnIML copy kept for every result:

Files – Raw instrument files attached to the right run or notebook entry, with acquisition metadata preserved, so reviewers can always trace a result back to its source.

Simple instrument data – Balance, pH meter and pipette readings written straight into results tables or container volumes in Inventory, with no retyping.

Time series data – Bioreactor, fermenter and environmental sensor streams summarized into results tables, with the full series kept for trending and analysis.

Metadata – Instrument, method, operator and timestamp captured automatically, or added manually, and mapped to schema fields and dropdowns to support GxP review.

Relational data – Every result linked to its entity, batch, container and plate well by barcode, so the Registry, Inventory and notebook entry all tell the same story.

Chemical structures – Structures matched to molecule entities in the Registry, so analytical results sit alongside the compounds and sequences they characterize.

The outcome is a notebook entry with full scientific context, plus a vendor-neutral data foundation that also serves your LIMS, CDS, AI models and long-term archive.

Find Out More

Ready to Connect Your Instruments to Benchling?

See how Splashlake turns Benchling requests into instrument worklists and brings structured results back into your notebook entries, from thousands of supported instruments. Integration time drops from months to days, and every result is stored in open AnIML, so your data stays readable and portable for the long term.

Contact us to discuss connecting your Benchling instance with Splashlake, connecting your instrument fleet and providing your scientists with a holistic view across all data sources.

We'll only use your details to respond to your inquiry.