Your instruments.
Part of the workflow.

Seal works with any instrument whose software saves a file. Seal IoT collects the files and sends them to Seal over outbound HTTPS. Each original stays with its results, linked to the sample, method and run, so your team and Neil, your AI agent, can investigate and improve the work.

Find your instrument

Find your instrument.

Seal works with any instrument whose software saves a file. Search 4,985 models from 248 manufacturers that laboratories connect, or open a manufacturer to see its models.

Not listed? The route is the same: if the instrument’s software saves a file, Seal IoT collects it, and each connection is scoped and tested with a representative export from your installed version. Send us the model and an example output.

Seal IoT collects what your software exports.

It runs on the instrument workstation, watches the folder your software exports to and sends each completed file to Seal over outbound HTTPS. The instrument software keeps acquiring the data and controlling the run.

HPLC-07 workstation

Folder: D:\Exports
Raw data: run-0412.raw
Sequence: run-0412.csv
Report: run-0412.pdf

Seal IoT

Watch the export folder
Wait for file-size stability
Run the upload script
Send over outbound HTTPS

Runs › RUN-0412

Originals: 3 files
Sample: S-042
Method: ASSAY-07 v04
Batch: B-0847

Seal IoT can run on the workstation, a staging machine or any host that reads the network share. It sends no instructions to the instrument, and each source’s formats, extraction and mapping are agreed and verified. Scientific data management explains the capture route in full.

Each result keeps its sample, method and run.

The original file stays with the run, and its values are mapped into the sample’s record rather than retyped. A reviewer reaches the chromatogram from the result.

Runs › RUN-0412 › Raw data

Samples › S-042

review

Result: 4.93 mg/mL
Specification: 4.20–4.80 mg/mL
Method: ASSAY-07 v04
Source: RUN-0412, raw data

Evidence	What Seal keeps
Original files	The export, as it was written
Identity	Run or sequence, injection and sample
Method	The method and its version
Values	Typed fields, with their units
Parser	Its version, beside each extracted value
Times	Acquisition and capture, kept apart
Reprocessing	A derived record; the first one stays

Matching uses the run or sequence, injection and sample rather than a filename, and ambiguous matches go to review rather than to the wrong sample. Define the files each run must produce: a finished PDF does not prove that the raw data, method and audit trail arrived.

Capture is not qualification. Whether the instrument was suitable for the work is recorded in equipment management.

What IT needs to confirm.

The folder-upload route needs no inbound connection to the workstation. Confirm the rest with IT before installation.

Area	What to confirm
Host	Windows or macOS, with access to the files
Network	Outbound HTTPS on port 443
Inbound ports	None for the folder-upload route
Folder access	Through the running account
Allowlist	seal.run, plus sign-in and update services
Credentials	Scoped to the destination workspace
Unattended use	A dedicated account and startup

Test connectivity from the actual host. Files that arrive while the agent is stopped can be picked up when it restarts, if they are still at the source, so agree a retention window and how repeats are reconciled.

The scientific data blueprint sets out installation in full, and connected systems in the regulatory guide covers how a connection is qualified.

Neil prepares the work. Your team decides.

Neil, Seal’s AI agent, works from the captured runs and their originals, within the permissions of the person asking. Your team inspects the sources and makes the decision.

Question	Neil prepares	Your team decides
Which runs support batch B-0847?	The runs and their originals	Whether the evidence is enough
Why is S-042 above specification?	The evidence, with its sources	Cause and impact
What changed between two reports?	The changed processing	Whether the change is justified
Capture a new plate reader’s export	The template and its checks	Whether they match the source
The instrument software was upgraded	A changeset with its verification	Approval and release

Unsupported formats, missing files and unresolved matches stay visible rather than becoming confident guesses, and receiving a file never approves a result.

In line with the EU’s draft GMP Annex 22 on AI, Neil is not used in GMP execution. It helps set up configuration, which your team verifies and releases under change control. See how Neil fits Annex 22.

Connection guides.

Each guide works through one kind of instrument data: what to export, how it maps to Seal records and the checks to run before your team relies on it. See all connection guides.

Start with your instrument.

Bring your model and an example output. We’ll map a connection into your workflow, with instrument control kept in your existing software, and test it with a late file, a duplicate transfer and a failed integrity check before you rely on it.

Book a demo