Built In Our Lab
Active production shelving at Subculture Laboratories
Osiris
Plant tissue culture lab management
Track subcultures and media demand with enterprise level accuracy.
Osiris is built around batch-first inventory tracking for in vitro and ex vitro plants. It scales to your lab. You keep shelf and section location, batch IDs, vessel types, dates, notes, and extensive logging in one record, with unique vessel tracking when you need more granularity. That significantly reduces relabeling overhead while keeping subcultures, planning, traceability, projects, and sales tied to the same operating history.
We built this tool to leverage your expertise in plant tissue culture and asceptic technique by automating away the attention it takes to keep track of the endless vessel churn and data collection necessary to understand trends.
Product Features
See where batches live across the lab
Lab Layout
A visual rack-and-section layout shows where material sits, where alerts are concentrated, and what needs attention first.
Why This Matters
Shelf context is operational context. The layout view makes it easier to see where batches actually live before technicians decide what to move, review, or touch next.
- Rack and section placement stay visible at a glance
- Shelf alerts surface pressure areas without scanning a spreadsheet
- Lab layout stays tied to the same batch and vessel record
Why Labs Choose Osiris
Built around how tissue culture work actually moves through the lab.
Osiris is actively being shaped by the constraints our lab deals with every day: bench time, vessel turnover, shelf context, media prep, and downstream handoffs. We are building a product that first and foremost is for streamlining our own workflows because we use it every day.
Track batches without labeling every jar
The inventory model is batch-first for in vitro and ex vitro plants. Shelf location, section, batch IDs, vessel types, dates, notes, and extensive logging stay together, with unique vessel tracking when you need more detail.
- Avoid removing labels from every jar before autoclaving.
- Shelf, section, batch, and vessel context stay in one record
Run subculture and prep from live vessel demand
Subculture timing is tracked by batch with add, remove, move, acclimate, sell, postpone, and mark-subcultured actions. Media demand gets automatically calculated from active in vitro vessels and the pre-subculture review audit feature allows technicians to pinpoint how much media is required week by week.
- The daily queue reflects real batch age and status
- Prepared media and demand planning stay tied to live vessels
Carry the same record into downstream work
Where we went further than most plant trackers was intentional: pesticide scheduling with inline chemical safety PDFs, a protocol library with citation links, lineage lifecycle views, project tracking with updates and vessel linkage, and live Etsy and Squarespace inventory sync.
- Traceability survives projects, sales, and handoffs
- Protocol, safety, and commerce context stay attached to operations
Surface what needs attention before it slips
Timing pressure becomes easier to manage when overdue work, review accuracy, and projected demand stay visible in the same operating system instead of being reconstructed from memory.
- Alarm windows make overdue batches harder to miss
- Review and demand signals stay visible before prep bottlenecks compound
Workflow
Move from shelf state to the next lab action without losing the record.
Sterilize and initiate new cultures.
Sterile prep starts the cycle. Division, transfer tools, and vessel setup happen in the hood before the batch moves forward.
Adjust quantity, vessel type, and media type at subculture.
Fresh vessels inherit the batch context so propagation can restart without rebuilding the record or labeling every jar.
Move explants into acclimation.
Young plants can leave the vessel and keep the same history as they enter covered acclimation and early ex vitro care.
Track all stages of growth.
Ex vitro inventory, scheduling, and downstream handoffs still point back to the same lineage and action history.
Roadmap
What we are building toward after the current core workflow.
The near-term roadmap starts with a stronger core operating system for tissue culture labs, then expands outward into downstream integrations and lab-specific AI tools.
Current focus
Beta
Refine the core batch tracker, subculture workflow, media planning, and day-to-day operating surfaces with real lab feedback. Onboard 2-3 beta testers.
Next major release
V1 Launch
Stabilize the system for a broader rollout with tighter onboarding, cleaner operational flows, and a more complete first production release.
Downstream expansion
Deeper E-Commerce Integrations
Expand and accommodate more e-commerce platform integration. Evaluate user feedback and implement most wanted features.
Applied lab intelligence
Contamination Diagnosis
Use image analysis and operational context to flag likely contamination patterns and help technicians review issues earlier in the workflow.
Longer-range direction
Autonomous Lab Ops Agents
Layer in specialized agents for planning, review, and operational assistance so the system can support decisions instead of only recording them.
FAQ
Why name this system Osiris?
In Egyptian mythology, Osiris is associated with order, wisdom, and renewal. That felt fitting for plant tissue culture, where division and transfer lead to regeneration rather than loss. The name also reflects our location in Southern Illinois, a region known as Little Egypt. For us, Osiris represents both the order needed to manage living material and the regenerative process at the heart of plant propagation.
What kind of lab is Osiris being built from?
Osiris is being shaped inside our own plant tissue culture lab around the real constraints we deal with every day: vessel turnover, media prep, subculture timing, shelf context, traceability, and downstream handoffs.
Why did you build Osiris instead of using generic lab software?
We could not find a system that matched how our lab actually works. Most tools either treated the workflow like generic inventory or forced too much manual labeling and re-entry. Osiris is our attempt to make the tracking model match the real flow hood workflow.
Why use batch-first tracking instead of labeling every jar?
The system is built so in vitro and ex vitro inventory can stay tied to batch, shelf, section, vessel type, dates, notes, and action history without forcing an individual label onto every jar. That keeps cleaning and autoclave turnover simpler while still allowing unique vessel tracking when the workflow needs more granularity.
What does Osiris track through the lab workflow?
Osiris tracks where batches live, how they change, and what happens next: add, remove, move, acclimate, sell, postpone, mark-subcultured actions, media demand, prepared-media inventory, and the record that carries forward as material leaves the vessel and moves through later stages.
Does the system stop at subculture and media planning?
No. The same record can extend into protocol references, lineage traceability, project tracking, pesticide scheduling with inline chemical safety PDFs, and E-Commerce inventory handoffs, so downstream work keeps the same operational context. Direct Etsy OAuth and Squarespace API integrations support live listing creation, updates, and inventory sync.
Is Osiris already being used in a real lab?
Yes. Osiris is being actively shaped around our live lab workflow, which means product decisions come from actual operating problems rather than a hypothetical feature list.
Who is Osiris for?
Osiris is designed for plant tissue culture labs that need batch-first tracking, media planning, subculture workflow visibility, and downstream traceability without turning every jar into a separate admin burden.
Who is Osiris not for?
Osiris is probably not the right fit for teams looking for a generic CRM, a simple plant collection tracker, or a lightweight greenhouse-only inventory tool.
What does early access look like?
Early access is hands-on. We start with a walkthrough of your current workflow, identify the operational bottlenecks, and use that to evaluate fit before rollout.
Can I buy tissue culture plants from you for my own lab?
Yes.
Visit our shopWhy are you sharing your lab's workflow publicly?
Because the system only makes sense if you can see the operating assumptions behind it. We want labs to understand the workflow model before they spend time evaluating the product.