Manufacturing & Laboratory Software

What this industry needs from software

Testing laboratories, calibration labs and manufacturing quality teams have requirements that most web agencies never meet. Their work is governed by standards - ISO/IEC 17025 for labs, GMP in pharma, national standards bodies for precious metals - and those standards care about one thing above all: the integrity of the record.

That produces a very specific software brief:

• Instrument integration. Data comes off a balance, a calibrator or a multi-instrument bench, usually over a serial port. Retyping a reading is both slow and an integrity risk, so the software has to talk to the hardware directly.
• Immutable records. An auditor wants to know a measurement could not have been altered after the fact. Insert-only databases, no edit or delete paths, and colour-coded audit logs are the design, not a feature.
• Offline, on-premise, licensed. Lab benches are frequently air-gapped or on restricted networks. The software runs as a desktop application on the machine next to the instrument, with licensing handled locally.
• Automated calculations. Fineness, delta, repeatability, calibration due dates, certificate numbering - the arithmetic the standard requires, done by the software so it is done the same way every time.
• Templates and documents. Certificates of analysis, calibration certificates and quality records have to come out in the client’s exact format, exportable to PDF, hundreds of templates deep.
• Role-based access. Technician, reviewer, approver. Who can see, who can sign.

How we approached the builds

Every desktop tool in this group is an Electron.js application with a React or Tabulator front end and Node.js underneath, using SQLite for the local database and the Serial Port API for instrument communication. That stack lets one codebase ship as a Windows installer, run fully offline, and still be built with the same web technologies we use everywhere else - which is why these projects go from requirements to deployment in weeks rather than the months a traditional lab-software vendor quotes.

The pattern that emerged across five projects:

1. Talk to the instrument first. Get the balance or bench sending clean readings before touching any UI.
2. Make tampering impossible by construction. Insert-only tables, signed audit trails, no admin override that could edit history.
3. Encode the standard’s arithmetic as tested functions rather than spreadsheet formulas.
4. Ship, watch it run on the bench, iterate. The first version of the BIS system was in daily use four weeks after the first conversation.

The same team also built the marketing site for QMS Total, the SaaS product family that grew out of this work - so this group spans desktop software, a licensed offline product line, and the Next.js website that sells it.

Confidence has compounded: the Bureau of Indian Standards commissioned three further desktop applications after the first, and Kemwell’s multi-instrument system followed the same architecture.