The GxP execution system.
Seal runs your whole GxP operation on one record, from eBR and QMS to LIMS.Neil, your AI agent, does the paperwork across all your systems. You sign.
Illustrative CAR-T release. Eight runs of version 4 of a procedure in Seal, post-thaw viability drifting down toward its 90% specification and reaching 91.4%. Neil drafts a reduction in the post-thaw hold from 45 to 30 minutes. The process owner reviews and approves version 5, whose runs hold around 96%.
Every run better than the last.
Usually the deviation, the procedure, its tests, the training and the batch record live in separate systems. In Seal they are one.
Found, Mon 19:40: Neil
Lot 26-0917 › Record review, shown belowFeed track at 0 A
21 min
Record“No interventions”
A 21‑minute stop the batch record left out.
Neil drafts the deviation for QA. The lot stays held.
Agreed, Tue 09:07: QMS
DEV-041 › Review, shown belowHappened before?
4 times
12 weeks of Line 21,310 read
Neil finds 4 earlier jams. QA agrees an hourly check.
A look through the glass, so no new media fill.
Approved, Tue 11:20: VLMS
SOP-FIL-007 › Changeset #15, shown belowStep 4.3, bowl check every
2 hourshour12 of 12 pass
Validation09:52
Production10:40
QA11:20
All 12 test cases pass. QA approves version 13.
3 new: Neil drafts, Validation approves, then they run.
Effective, Tue 21:34: DMS and LMS
SOP-FIL-007 › Version 13, shown belowNight shift trained
4 of 4
v12v1322:00 shiftNight shift trained. Version 13 in force.
The day shift's seven train before their next shift.
On the line, Wed 02:10: eBR and MES
Lot 26-0918 › Fill, shown belowStep 4.3Hourly, new in v13
No jam
Confirmed by A. Okafor
01:1009:10
The next lot's record calls the hourly check.
The fix: a new feed track, then ten lots without a jam.
30 hours from the finding to the check on the line, every step of change control signed. The procedure's last change, raised before Seal, took 15 weeks.
Blubber Biologics is a fictional plant. What customers measured is below.
GxP execution system
eBR, MES, QMS, DMS, LMS, LIMS, ELN and CMMS on one record. Use one, or all of them.

- This entry
- What it stands on
- One square, one entry
- This entry
- What it stands on
- One square, one entry
Fill weight 10.19 to 10.22 g
Neil
Neil reads your records where you keep them, from SAP to AVEVA PI, and drafts the paperwork. People decide.

Fri 6 Nov, the fill
The batch recordStep 4.3: “No interventions”
F-02's feed track, by Edge0 A from 02:08 to 02:29
Line 2's channel, Teams02:11 “Stopper bowl jammed again”
Neil, first night on Line 2WorkingDone 00:18
- Read the batch record, 1,912 entries
- TeamsRead Line 2's shift channel and handovers: 653 messages
- EdgeLine 2 stopped 21 min; the record says no interventions
- Teams“Stopper bowl jammed again”
- DEV-041 drafted on Blubber's form, for QA
- Endotoxin run invalid, spike recovery 31%
- Bulk held 29 h 40 min; the study covers 26 h
- Checked Blubber's review checklist (RC-014 v6): 45 of 50 met
- Cited each met check to its entry
- Brief ready for QA: seven to decide
Lot 26-0917: record review
QA confirms all 50. Each met check opens to its entry
GxP › QMS
Deviations, CAPA and change control on the record they are about. Neil takes the minutes, for QA to accept.

- Detected
- Drafted
- QA triage
- Investigation
- CAPA
- Closed
- 1,240 messages, 61 meetings, 9 maintenance entries
- 13 batch records
Has this happened before?
Nothing compared the records with the machine or the messages until Neil joined the line on Monday.
Minutes
Tue 10 Nov, 09:00 to 09:30GxP › Continuous validation
Validated, not frozen. Every change is tested against your processes, then your QA approves it.

Step 4.3: Stopper feed
- Bowl checkEvery
2 hourshour during filling - If it jamsStop the line. Clear it as intervention INT-07. Record it before restarting.
Proposed by Neil at 09:31 from DEV-041's review. The check is a look through the glass; clearing a jam is still INT-07, so no new media fill.
v12Next check in 45 min
v13Overdue: the record holds its next entry
12 of 12 test cases passed on v13 at 09:54
3 new: Neil drafted, R. Haldane approved
- Clearing a jam needs a recorded intervention
- Its start, end and rejected vials are required
- A stop over 10 min opens a deviation for QA
9 standing: written by Blubber at go-live
- The check falls due after 60 min
- An overdue check holds the record's next entry
- Steps 4.1 and 4.2 are unchanged
- Steps from 4.4 on are unchanged
- Fill weight limits are unchanged
- Lot 26-0917's record stays on v12
- The next fill starts on v13
- Untrained operators can't sign 4.3
- The audit trail records both versions
R. Haldane10 Nov, 09:52 GMT
3 new test cases approvedK. Brandt10 Nov, 10:40 GMT
ReviewedAwaiting signature
GxP › DMS and LMS
A new version is approved, trained and effective before the next shift. The line can't run on the old one.

- Proposed
- Tested
- Approved
- Trained
- Effective
Version 13 is effective
- A. Okafor20:48
- J. Lindqvist20:59
- M. Rossi21:12
- R. Mensah21:34
- Version 12In forceWithdrawn 21:34
- Version 133 of 4 signedEffective 21:34
Check the stopper bowl every 2 hours hour during filling. If it jams, stop the line. Clear it as intervention INT-07. Record it before restarting.
Step 4.3 can't be signed by anyone not trained on the version in force.
Audit trail
Version 13GxP › eBR and MES
The batch record directs the run. It calls each check, reads the instrument, and Neil flags a trend before it reaches a limit.

- Dispense
- Formulate
- Filter
- Fill
- Cap
- Inspect
- Label
- Pack
- QA review
Fill weight check
Trimmed at 02:14. Pump 2 never reached its limit.
Batch record
SOP-FIL-007 v13Neil › Voice and vision
Hands in the glove ports can't type. Neil sees what they do through smart glasses and drafts the entry for the operator to sign.
Batch record
SOP-FIL-007 v13Edge
Seal Edge reads your equipment, instruments and historian from inside your network. Each reading lands on its lot and its step.

Measured by the teams that run on Seal.
Supports clinical trials50%less time from “this procedure needs updating” to “approved and everyone trained”Against procedures in Google Drive and training by email.Runs QMS on Seal.
Allografts from donated placental tissue40%fewer non-conformances, with training checked before executionAgainst handwritten batch records.Runs eBR and QMS on Seal.
An implantable brain–computer interface90%less time engineers spend reviewing travelersAgainst 3 to 4 hours a day on paper travelers.Runs QMS, ELN, eBR and MES on Seal.
Antibodies for diagnostic analysers80%less document admin time for revision, approval and trainingAgainst a paper quality system run for over two decades.Runs QMS and ELN on Seal.
Omega-3 algae, by fermentation75%less time writing, filing and retrieving records of the processAgainst paper batch records, notebooks and spreadsheets.Runs eBR, QMS and ELN on Seal.
ERP
Costing on the record production already wrote: what a stop cost, to the dollar, and stock free to sell the minute the lot is released.

- Planned
- Issued
- Filled
- Released
- Allocated
- Invoiced
Cost a vial
- 21 min line stop$1,470
- 61 vials rejected$2,378
Both are DEV-041. Neil puts five jams since August at about $18,940.
- Held by QA
- 0
- Free to promise
- 1,339
- Promised
- 40,000
41,860 filled, 61 rejected at the stop, 318 at inspection, 142 sampled and retained, 41,339 held41,860 filled, 61 rejected at the stop, 318 at inspection, 142 sampled and retained, 41,339 released
Ledger
Lot 26-0917Portal
Your clients and partners see a deviation on their lot, and the change it brings, the same day your QA does. They see only what you share.

- Ordered
- In production
- Released
- Shipped
- Delivered
- Invoiced
Shipment SH-0771
Shared with you
By Blubber BiologicsDeployment
Line 2 was off paper in 38 days; Blubber's last system took 14 months. A Seal strategist stays on your site until you accept the result.

Ready for your quality and IT review.
SOC 2 Type 2 audited. Part 11 and Annex 11 e‑signatures and audit trail. Your data trains no AI. Neil decides nothing in GMP work.

- Intended use
- Criteria
- Evaluated
- Approved
- In use
Against QA's own reviews
Lots 26-0909 to 26-0916, each already reviewed by QA, read from the batch record alone
- 387 met
- 11 QA findings
- 2 differences
Criteria, set by S. Amato before the evaluation
Setting Neil's result beside QA's, record by record2 differences: Neil flagged, QA had accepted
Validation record
Mon 9 NovQuestions about Seal.
What is Seal?
Seal makes every GxP run better than the last. The Seal platform runs lab, manufacturing and quality work, with QMS, batch records, MES, ELN and LIMS on one record. Neil, the AI agent, reads the systems you connect, drafts the paperwork and proposes improvements for your team to approve, with Seal or without. Seal ERP adds materials, costing, orders and invoicing on the same record. Seal Edge reads your equipment, instruments and historian on site and puts each reading on its lot's record, and Seal Portal opens the record to your clients, as far as you share it.
Why Seal over a standalone LIMS, QMS or MES?
Lab, manufacturing and quality run on one platform, so a result, its batch and its investigation are linked rather than reconciled across systems, and Neil can work across all of them. Start with one workflow and add the next when you are ready.
How are changes validated?
Each change carries its specifications, test evidence and required approvals, so a validated process can keep improving instead of freezing. Your team approves each change before it takes effect, and earlier runs keep the version they used.
Can Neil change a live process?
Neil proposes changes. Each is tested, and your team approves it before it goes live. Neil works within your permissions; you can disable AI across the organisation.
How is Neil itself validated?
For each job you give Neil, your team evaluates it on representative cases against acceptance criteria your experts set, and again after any change of model or configuration. In line with the EU's draft GMP Annex 22 on AI, Neil doesn't decide anything in GMP work: a qualified person reviews what it finds or drafts, and what runs is configuration your team has tested and approved under change control.
Do we have to replace our existing systems?
No. Neil reads the systems you keep, from SAP to AVEVA PI, and drafts its work for your team. Start Seal with one process and move more work into it when you’re ready.
Where is our data hosted?
Seal agrees the hosting region with you at onboarding, and confirms the AI provider, where it processes data, retention and model terms for your organisation during onboarding and supplier review. Under Seal’s agreements, your data is not used to train AI models.
Who uses Seal?
Paradromics, Bioventix, Acclinate, Skye Biologics and MiAlgae. Read their customer stories for measured results.


See your process in Seal.
Working 48 hours after we agree its scope: tested, with evidence your QA approves.



