Skip to main content

Your instruments.
Part of the workflow.

Seal works with any instrument whose software saves a file. Each original arrives linked to its sample, method and run, ready for your team and Neil.

Illustration of a seal linking a balance check to run, sample and batch records.

Find your instrument.

Search 4,589 models from 248 manufacturers.

Not listed? The route is the same: if the instrument’s software saves a file, Seal Edge 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 Edge collects what your software exports.

It runs on the workstation and sends each exported file to Seal over outbound HTTPS. Your instrument software keeps controlling the run.

HPLC-07 workstation

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

Seal Edge

  1. Watch the export folder
  2. Wait for file-size stability
  3. Run the upload script
  4. Send over outbound HTTPS
Runs › RUN-0412
Originals
3 files
Sample
S-042
Method
ASSAY-07 v04
Batch
B-0847

Seal Edge 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 map into the sample’s record. 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
EvidenceWhat Seal keeps
Original filesThe export, as it was written
IdentityRun or sequence, injection and sample
MethodThe method and its version
ValuesTyped fields, with their units
ParserIts version, beside each extracted value
TimesAcquisition and capture, kept apart
ReprocessingA 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.

AreaWhat to confirm
HostWindows or macOS, with access to the files
NetworkOutbound HTTPS on port 443
Inbound portsNone for the folder-upload route
Folder accessThrough the running account
Allowlistseal.run, plus sign-in and update services
CredentialsScoped to the destination workspace
Unattended useA 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 works from the captured runs, within the permissions of the person asking. Your team inspects the sources and decides.

QuestionNeil preparesYour team decides
Which runs support batch B-0847?The runs and their originalsWhether the evidence is enough
Why is S-042 above specification?The evidence, with its sourcesCause and impact
What changed between two reports?The changed processingWhether the change is justified
Capture a new plate reader’s exportThe template and its checksWhether they match the source
The instrument software was upgradedA changeset with its verificationApproval 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 decides nothing in GMP work. It helps set up configuration, which your team verifies and releases under change control. See how Neil fits Annex 22.

Connection guides.

Each guide takes one kind of instrument data: what to export, how it maps to Seal and the checks to run. See all connection guides.

Start with your instrument.

Bring your model and an example output. We’ll map the connection and test it with a late file, a duplicate and a failed integrity check.

Book a demo