Prep
You accession the sample, build the plate map, and generate the sample sheet for the instrument.
ProductWellGS covers the work a bioinformatics lab does between a sample arriving and a result going out: accessioning, plate maps, sample sheets, instrument runs, analysis, and reporting. You prep the run in WellGS, send the analysis to AWS HealthOmics, and the results land back on the sample record.

The system of record for your bioinformatics lab.
The path from sample to result is held together by hand: plates are laid out in Excel, extraction logs live in an Access database, and sample sheets are reformatted for each instrument. Analysis runs on a high-performance computing cluster, and the results come back somewhere other than the sample record.
Plate maps are built by dragging rows in Excel, where the index moves with the row and nothing flags the break.
DNA extraction logs sit in an Access database, apart from the accession record they belong to.
The same plate is reformatted by hand into a different sample sheet for every sequencer on the bench.
Analysis finishes where it runs and stops there, so someone re-keys the results, re-attaches the files, and re-checks the mapping by hand.
Each handoff is a chance to lose traceability or to silently break the mapping between a sample and its data. The work still gets done, but it costs the lab attention that should be going to the science.
You prep the run, sequence it, send the FASTQs for analysis, and get the results back on the same record you started from. Reporting goes out from there, so nobody has to leave WellGS to finish a run.
You accession the sample, build the plate map, and generate the sample sheet for the instrument.
The lab runs the sequencer, and the FASTQ files come back into WellGS from the instrument.
WellGS stages the run and sends those FASTQs to AWS HealthOmics, where the pipeline runs on high-performance compute.
The output comes back into WellGS, tied to the sample by accession.
WellGS reshapes the result for ELR, PulseNet, or an NCBI submission and sends it on their schedule.
Accessioning, sample tracking, plate maps, sample sheets, and LIMS integration all live here, which is where the lab actually works.
A launcher is a thin front end that turns a staged run into an AWS HealthOmics job. WellGS integrates with Easy Genomics, and runs just as well without a launcher at all.
This is where the analysis actually runs, on high-performance compute, whichever route a run takes to get there.
We build on AWS HealthOmics and integrate with its launcher, Easy Genomics. We can also tailor WellGS to the workflow a lab already wants, so no single external tool’s interface dictates how the lab works.
Putting samples onto a 96-well plate is a decision someone makes by hand, usually in a spreadsheet. In a spreadsheet, dragging a row takes the index with it, and nothing tells you the mapping just broke.
You can rearrange a plate without silently ruining it.
A launcher shows you the status of a job, not the state of your lab. Analysis output comes back into WellGS instead, tied to the sample by accession and carrying a validation receipt, a file manifest, and presigned downloads, so your team never has to learn another tool to find it.
Your people stay next to the record they already trust. Each returned file has somewhere it belongs, and WellGS routes it there: receipts to the lab record or LIMS, operational logs to your cloud console, and scientific artifacts to the review tools built for them.
The result ends up on the same record the sample started on.
run 20240824110543 · nf-core/bacass · presigned downloads
Accessioning sits in the data model itself, so it behaves like part of the record rather than an add-on. WellGS replaces the Access database that DNA extraction logs live in today.
It integrates with LabWare LIMS to meet the lab where its data already is, supports multiple instruments because that lab needed it to, and runs inside the lab’s own AWS account.
Pull data straight from where the lab's data already lives.
NextSeq, MiSeq, and iSeq sample sheets from one plate map. More sequencer integrations coming soon.
Runs in the lab's own AWS account, or hosted by us.
Bring a real workflow, from accessioning through the report you owe, and we will show you which handoffs WellGS removes.