Lab data, in order

// The problem

A discovery biotech keeps thousands of samples across freezers and a liquid nitrogen store, tracked on a spreadsheet, and scientists lose hours looking for aliquots that were used up months ago.

// What we would build

An inventory app for samples, reagents and storage, with every tube and box labelled with a barcode, scanned in and out from a phone or a cordless scanner, and each sample linked to the experiment in your lab notebook that used it.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• Zebra label printers
• AWS Canada (Central)

// The problem

A screening lab's plate readers and analysers write files to a shared drive, and a scientist copies the numbers into a spreadsheet before anyone can see a dose response curve.

// What we would build

Instrument files picked up as they are written, stored in managed cloud storage, parsed into one database with the plate map and the sample IDs, and shown as assay dashboards your team and your board can read. We run the pipeline for you, with monitoring and backups.

// What is in it

// Stack

• Python
• PostgreSQL
• Amazon S3
• Metabase
• AWS Canada (Central)
• Terraform

// The problem

A contract research lab runs an electronic lab notebook, a LIMS, a freezer inventory and a handful of instruments, and every hand-off between them is a person retyping IDs.

// What we would build

An internal integration hub that joins your notebook, LIMS, inventory and instruments through their published APIs, so a sample registered once appears everywhere it is needed, results flow back to the right record, and every sync is logged. We check each system's API before we quote.

// What is in it

// Stack

• Node.js
• PostgreSQL
• OpenAPI
• Benchling API
• AWS Canada (Central)

// The problem

A contract lab still runs its studies on a LIMS built in Access fifteen years ago, a vendor replacement stalled half done, and nobody can say which of the two to trust.

// What we would build

We start with an architecture review of the old system and the stalled one, and write down what is worth keeping. Then we rescue the work: a web LIMS built to the requirements your quality team sets, every record moved and checked, and the old database kept read-only until your team signs off.

// What is in it

// Stack

• Next.js
• PostgreSQL
• Access import
• AWS Canada (Central)

// The problem

A biotech's scientists spend hours each week searching papers, patents and their own internal reports, and the company will not paste unpublished work into a public chatbot.

// What we would build

A literature assistant on an open-source model that runs on GPUs we set up for you, so nothing leaves your control. It searches the papers you choose, your internal reports and your notebook exports, answers with the passages it used, and says when it does not know. It helps your scientists read; it does not make scientific or medical judgements.

// What is in it

// Stack

• Python
• Open-source LLM
• PostgreSQL with pgvector
• Next.js
• DigitalOcean GPU Droplets

// The problem

A contract research lab takes study requests and sends results by email, sponsors in several countries ask the same status questions every week, and the lab's site does not look like the work it does.

// What we would build

A sponsor portal designed for your lab: sponsors submit requests, track their samples and studies, and download reports, with a help centre and an assistant that answers from it in the languages your sponsors use, handing anything about a study to your project managers.

// What is in it

// Stack

• Next.js
• Claude API
• PostgreSQL with pgvector
• Headless CMS
• AWS Canada (Central)

// The problem

A biotech, two contract labs and a university partner pass samples and results between them, and each keeps its own record of what was sent, received and released, which never quite match.

// What we would build

A shared web app where each organisation records samples sent, received and released, with every hand-off written to a private permissioned ledger that each partner runs a node of. A shared database run by one partner, or signed PDFs, often do this job; the ledger helps when several organisations need one record that no single party controls.

// What is in it

// Stack

• Next.js
• Hyperledger Besu (private, permissioned)
• PostgreSQL
• AWS Canada (Central)