There is a quiet shift happening in scientific software in 2026, and most labs have not noticed yet. The SaaS tools that promised to "modernise" bioassay analysis a few years ago — the ones that ask you to upload your raw plate files, your standards, your unpublished IC50s — are now the same tools whose Terms of Service quietly grant a licence to use "aggregated, de-identified" data to train internal models. Your negative controls are somebody else's training set.

This is why local-first has become the fastest-growing pattern in scientific tooling, and why Labreador was built that way from day one.

What "local-first" actually means

Local-first is not the same as "offline mode" or "we encrypt in transit". It is a stricter architectural promise:

Your data never leaves the device. Parsing, fitting, statistics, QC, exports — all of it runs inside your browser tab.
The server has nothing to leak. There is no database row with your OD values, no S3 bucket with your CSV, no log line containing your sample names.
The app keeps working without a network. If the server disappears tomorrow, your analyses do not.

For a bioassay platform this matters more than for a note-taking app. Raw curves, EC50s, batch numbers, and dilution schemes are often the most sensitive artefacts a lab produces — sometimes months before a patent filing, sometimes under an NDA, sometimes covered by GDPR because the samples came from human donors.

Why 2026 made this urgent

Three things changed in the last eighteen months:

Generative models eat any text they can reach. "We do not sell your data" no longer implies "we do not train on your data". The two clauses are separate, and most cloud lab tools only make the first promise.
Regulators started reading TOS. EU AI Act obligations and updated GDPR guidance now treat scientific measurements linked to identifiable samples as processing that requires an explicit legal basis — one that a click-through EULA does not provide.
Journals started asking. Several Q1 journals in analytical chemistry and toxicology now require authors to state where raw data was processed and whether the processing environment could re-transmit it. "In a browser tab, never uploaded" is a much cleaner answer than "on vendor X's cloud".

If your workflow currently pastes standards into a hosted spreadsheet or a SaaS ELISA calculator, you are already answering these questions — just implicitly, and not in your favour.

How Labreador implements local-first

Every calculation module in Labreador — ELISA, Dose-Response, Kinetic Analysis, Parallel Line Analysis, Ecotoxicology — runs entirely in the browser. Concretely:

Parsing of plate-reader CSVs, kinetic time-courses, and grid layouts happens in client-side TypeScript. Nothing is POSTed.
Fitting (4PL/5PL, weighted regression, PLA constrained fits, Monte Carlo draws) uses in-browser numeric routines. No serverless function receives your OD values.
Statistics (Grubbs, Lack-of-Fit, ANOVA, post-hoc, bootstrap CIs) are computed locally.
Exports — PDF reports, CSVs, high-resolution PNGs — are generated in the browser and streamed straight to your Downloads folder.
Offline is a first-class mode. Labreador is an installable PWA; once opened, the calculation modules keep working with the network cable pulled.

The one place a network call happens is the optional AI assistant, and that call carries only the question you type — never the dataset in the workspace. If you want the assistant to reason about your numbers, you paste the specific values you choose to share.

What to ask any lab-software vendor in 2026

If you are evaluating a tool that touches raw assay data, five questions separate local-first vendors from repackaged clouds:

Where is the fitting executed — my device or your servers?
What is retained after I close the tab: nothing, metadata, or the raw values?
Can the app compute results with the network disabled? (Ask them to demo it.)
Are my data used, in any form — aggregated, anonymised, statistical — for model training or benchmarking?
Can you produce an audit trail confirming the answers above?

A vendor that hesitates on question 3 or 4 is not local-first, no matter what the landing page says.

The bigger point

The last decade of scientific software was about moving everything to the cloud because that was where compute lived. In 2026, the browser is fast enough to fit a 5PL curve in milliseconds, run a thousand Monte Carlo iterations on a laptop, and render a publication-ready PDF without a round-trip. The reason to keep sending raw data to somebody else's server is no longer technical — it is commercial.

Local-first is how scientific software should have looked all along. Labreador is one implementation of that idea, and if you want to see the guarantee in action, open the ELISA module, disconnect from the internet, and finish your analysis anyway.