Tools, not code.
The output is something you click on, not something you run from a terminal.
Describe the lab tool you need. Get a working, validated app back.
LabWren turns a scientist’s plain-language description of a lab task into a validated, ready-to-ship software tool.
They get a script, not a tool.
Scientists already use ChatGPT and Claude for code, but hit a wall: they can’t run it, can’t trust it, and can’t hand it to a labmate.
Labs run on a mess of fragile spreadsheets, one-off scripts, and manual copy-paste.
How it works
- 1
Describe
Describe the task and upload a real example file (plate reader export, instrument CSV, Excel sheet).
- 2
Build
LabWren asks the clarifying questions a good lab engineer would, then generates the tool.
- 3
Verify
The tool is checked against your example data, and the math is shown so you can trust it.
- 4
Ship
Get an app the whole lab can use: a hosted link, a single offline file, or a desktop app.
Starter templates:BCA protein assayELISA 4PL curve fitqPCR ΔΔCtPlate map designerOD600 growth curves
Tools, not code.
Trust is the product.
A tool that’s wrong once never gets used again. Every tool shows its math, runs against real example data, and flags anything suspicious.
Domain knowledge beats generality.
LabWren should know what a BCA assay is, what a 96-well plate looks like, and what a SpectraMax export looks like, before the user explains it.
Works in real labs.
Lab computers are locked down, sometimes offline, and often run old Windows. Tools must run where the science happens.
Data stays private.
Unpublished research data is sensitive. Handle it that way from day one.
Built for the bench scientist — grad student, postdoc, research associate, lab manager — who knows exactly what the analysis should do but isn’t a programmer.
The PI, core facility director, or R&D ops lead who wants reproducible analysis across the lab.
LabWren is in private beta.
v0 is rolling out to a small group of labs. Join the waitlist and we’ll send your invite when a spot opens.