GSA LabOS
The laboratory information management system we run our own bench on, licensed for yours. It drives the instruments, moves a sample from carrier scan to signed certificate without anyone retyping a number, and bills the work on the way through.
Installs on your own hardware. Your data never leaves your network unless you publish it. Licensed per seat with the instrument drivers included.
Thirty-day evaluation, full feature set, no instrument limit. No card.
- Released
- 2 Sep 2026
- Instrument drivers
- 11 platforms
- Deployment
- On your hardware
- Database
- PostgreSQL 15
- Validation package
- IQ, OQ, PQ included
One system from carrier scan to signed certificate
Most laboratories run a LIMS for samples, a separate folder of instrument files, a spreadsheet for prep, and an accounting package that never sees either. LabOS is one record per sample, and every stage writes to it.
Sample intake and custody
Carrier scan opens the record, receiving photographs every container, and the accession carries a check digit and a bench blind code.
- Barcode per container and per aliquot
- Client portal submission and label issue
- Retained-sample store with expiry alerts
Preparation
Prep sheets generate from the method. Balances and pipettes report their own numbers, so dilutions are captured rather than transcribed.
- Reagent and standard lot traceability
- Dilution and spike calculators
- Expired reagent blocks the prep
Instrument control
Worklists are built, pushed and watched. Raw files come back, integrate against the stored method and never get edited in place.
- Agilent, Thermo, Shimadzu and Waters
- Daily system suitability gate
- Out-of-tolerance instrument lockout
COA generation
Certificates compile from the record: results, spec, methods, instrument IDs, LOD and LOQ, chromatogram, signature and hash.
- Your template and your logo
- SHA-256 at signature, public URL optional
- Retraction and revision history
Accounting and billing
The invoice is raised from the panel that actually ran, not from what was quoted, so rushes and add-ons never go unbilled.
- QuickBooks, Xero and Mercury sync
- Stripe, ACH, wire and net terms
- Per-client price lists and volume tiers
Quality management
Calibration schedule, service records, deviations, CAPAs, training records and document control in the same system as the results.
- Calibration due alerts per instrument
- SOP versions with read-and-understood
- Audit pack export for an assessor
Drives the instruments, not just the paperwork
LabOS builds the worklist, pushes it to the instrument, watches the run, pulls the raw file back and integrates it against the method. No one exports a CSV and no one types a result.
| Platform | Models we drive today | Connection | What LabOS does |
|---|---|---|---|
| Agilent LC and LC-MS/MS | 1290 Infinity II, 1260 Infinity II, 6490 and 6470 triple quad | MassHunter and OpenLab, ECM API | Sequence push, raw pull, integration |
| Agilent ICP-MS | 7850, 7900 | MassHunter ICP-MS, CSV and API | Sequence push, QC gate, raw pull |
| Agilent GC and GC-MS | 8890 GC, 5977 MSD, 7010 triple quad | MassHunter GC, OpenLab | Sequence push, raw pull, integration |
| Thermo LC-MS | Vanquish, Q Exactive, TSQ Altis and Quantis | Chromeleon eWorkflow, Xcalibur | Sequence push, raw pull, integration |
| Thermo ICP-MS | iCAP RQ, iCAP TQ | Qtegra, watched folder | Sequence push, result ingest |
| Thermo GC-MS | ISQ 7000, TSQ 9000 | Chromeleon | Sequence push, raw pull |
| Shimadzu and Waters | Nexera, LCMS-8060, Acquity, Xevo | LabSolutions, Empower toolkit | Sequence push, result ingest |
| Endotoxin and sterility | Charles River Endosafe, plate readers | Serial and vendor export | Result ingest, PPC check |
| Balances and titrators | Mettler Toledo, Sartorius, Karl Fischer | Serial or network capture | Live weight and volume capture |
What the driver does
- Builds the sequence from the ordered panel and the stored method
- Interleaves calibrators, check standards and blanks the method requires
- Blocks the run when suitability has not passed or the instrument is out of tolerance
- Pulls the raw file back and stores it read-only with a hash
- Integrates against the method and writes the peak table to the record
- Flags a result outside specification before an analyst sees the number
What it will not do
- Replace MassHunter, Chromeleon, Empower or LabSolutions
- Modify, overwrite or delete an acquired raw file
- Hide a failing result or re-run a sample without a logged reason
- Release a certificate signed by the analyst who ran the sample
LabOS is a laboratory information system. It does not replace the instrument vendor's acquisition software, and it does not modify a signed raw file.
What happens to a sample
Seven stages, each one writing to the same record. Click a stage to see what LabOS does and what it writes down.
Receiving
A carrier scan opens the record before anyone touches the box. LabOS photographs the contents on the receiving camera, weighs each container and holds the package as unaccessioned until a second person confirms the manifest matches.
- Carrier scan time and tracking number
- Photograph per container, hashed
- Gross and net weight per container
- Receiving analyst and confirmation
Built for an audit you have not had yet
The record is the product. LabOS is designed so that an auditor can reconstruct any number on any certificate from the raw file that produced it.
| Feature | What it gives an auditor | Scope |
|---|---|---|
| Append-only audit trail | Every create, change and view with the identity, time and previous value. Nothing is deletable from the application. | System wide |
| Electronic signature | Signature bound to the record content, so any later edit invalidates it and shows as invalidated. | Release and review |
| Read-only raw files | The acquired file is hashed on arrival and stored write-protected. The hash is printed on the certificate. | Every instrument run |
| Segregation of duties | The system enforces that the reviewer is not the analyst, by role rather than by policy. | Review and release |
| Method and SOP versioning | Each result records the method version it ran under, so a method change never rewrites history. | Methods, SOPs, specs |
| Audit pack export | One command produces the records, trails and raw files for a date range or a single accession. | On demand |
LabOS is built to 21 CFR Part 11-style expectations for electronic records and signatures. Software cannot make a laboratory compliant on its own: your SOPs, training records and method validation are still yours to hold. We supply the validation package and the audit trail specification so your assessor has something to read.
Licensing
Priced per instrument and per analyst seat, billed annually. Instrument drivers, updates and the validation package are included at every tier. No per-sample fee and no charge for certificates you publish.
Bench
One to three instruments, up to five analysts
- Up to 3 instrument drivers
- 5 analyst seats
- Intake, prep, COA and billing
- Email support, next business day
- Validation package included
Laboratory
A working contract lab, most common tier
- Up to 12 instrument drivers
- 25 analyst seats
- Everything in Bench
- Client portal and public certificate hosting
- Quality module: CAPA, training, documents
- Phone support, four-hour response
Multi-site
Several laboratories under one quality system
- Unlimited instruments and seats
- Everything in Laboratory
- Cross-site harmonised methods
- Single sign-on and directory sync
- Named implementation engineer
- Source escrow available
Migration from an existing LIMS, method porting and on-site installation are quoted separately. Academic and non-profit laboratories are priced at half the listed rate.
Download and evaluate
The evaluation build is the production build with a thirty-day licence file. Nothing is stripped out, and an evaluation database converts in place when you license it.
- Operating system
- Windows Server 2019 or later
- Processor and memory
- 8 cores, 32 GB
- Storage
- 2 TB, raw files grow ~40 GB a month per LC-MS
- Database
- PostgreSQL 15, bundled or your own
- Instrument PCs
- Same subnet, agent installed per instrument
Builds are released to named laboratories. Tell us the site and the instruments and we send a signed installer and a licence file the same business day.
Already a testing client?
Laboratories that send us work get the first year at half price, and your existing accessions import with their certificates attached.
Talks to the rest of the stack
- REST API and MCP serverThe same interface this site runs on, pointed at your instance
- QuickBooks, Xero, MercuryInvoices, payments and reconciliation
- Stripe and ACHCard, bank transfer and net terms on the same order
- WooCommerce and ShopifyPublish certificates to a client product page automatically
- Shipping carriersPrepaid label issue and inbound scan events
Same REST API and MCP server this site runs on. Read the API reference.
Questions about LabOS
If your question is not here, ask and a person who has installed it will answer.