LabOS.

The work on the floor.
The record behind it.

I built LabOS for the extraction lab I run. It connects the material coming in, the work happening to it, and the jars going onto the shelf.

Follow a batch
Made by
Cody · design, build & daily use
Project
003 · Software
LabOS / Batch 2608.108Inspect screen ↗ LabOS batch record for fictional Sour Diesel 2608.108, showing received and packed weights, finished output and linked jars.
Real interface. Fictional lab records.
Local build captured September 24–26, 2026.

A batch becomes jars.
The record stays with them.

Follow Sour Diesel 2608.108 from its batch record to a jar’s pull history and the matching label sheet. These captures show different views of the same fictional batch.

Batch record / 2608.108Open full size ↗
Sour Diesel batch 2608.108 with its weight summary and jar list.
The batch page holds the stage history, weight summary and linked jars together.

Sour Diesel / 2608.108

One place to trace the work.

The received weight, packed weight and finished output sit above the jars linked to this batch. The same batch ID follows the material through the app.

Provider
Twin Pines Farms
Material
Cured
Shown here
Batch record & jar list

Archived app captures with fictional data. Select a view, then open the image to read the detail.

LabOS batch record, fictional demo data.
Open original image ↗
01

Recordings

Four screen recordings of a local build, 2026-09-26. Fictional demo data. Muted until asked.

These are screen recordings of the app on a Mac, not live controls. Three are 30 fps captures, one is 25 fps.

02

The lifecycle, illustrated

An illustration of the stages using fictional figures, not a recording of one batch progressing.
Demo, not the appBatch 2608.108 · Sour Diesel · Twin Pines Farms · curedfictional

    This illustration uses the recorded totals from demo batch 2608.108. It does not show captured history for each earlier stage.

    03

    Around the lab

    Archived workflow screens from different fictional batches, September 2026
    CommandDemo data

    04

    What comes out

    Real documents generated by the app, on demo data
    05

    The showcase frames

    Fifteen frames, 2026-09-26. Dithered until you hover, focus or tap.
      06

      Before and after

      Making labels, in Cody's own words
      Before
      At least 1 hour, 2-3 times a week
      Now
      5 minutes for a week's worth

      “It took at least an hour to make labels and that was two or three times a week. Now it takes five minutes to print a week's worth.”

      Cody, who runs the lab and built LabOS

      Making labels is the one task measured here, and these are Cody's own figures from using LabOS at the lab.

      07

      The lab it runs in

      What shows, and what never does

      LabOS was built on the floor of a licensed New Jersey extraction lab by the person running it. The cannabis is in the vocabulary, not in a claim: biomass comes in on a manifest, fresh frozen or cured; a batch is packed into socks, run, and finished in ovens; jars go on a shelf; every jar gets a label.

      The demo lab's strains are named the way strains are named. The providers, the batches, the weights and the dates are made up for the demo and marked so wherever they appear.

      • neverReal SUN batches, weights, yields or providers.
      • neverTime or performance numbers beyond the one Cody measured above.
      • neverA recording styled as a live control.
      • neverCustomer or sales claims; there are no outside customers.