Choose MeristemLab if
You are in Australia, you grow aroids, and being an early user of something close to home — with the influence over its direction that brings — appeals more than a product whose shape is already settled.
Comparison
xPlant Pro and MeristemLab, compared
The closest product to ours in shape: culture tracking, lineage, media and contamination, in a browser. The differences are maturity, reach and what the record is asked to prove.
Free plan to start. No card needed.
What each one says about itself
Read from their published pages rather than inferred, so you can check every row yourself.
| Compared | MeristemLab | xPlant Pro |
|---|---|---|
| Stage | MeristemLabEarly access — “now available for testing”. | xPlant ProIn production use, with released versions and public release notes. |
| Free | MeristemLab“Get Started Free”. | xPlant ProA free plan with no time limit, no card. |
| Base | MeristemLabAustralia. | xPlant ProSouth Korea, serving labs in seven languages. |
| Crops named on the site | MeristemLabAroids — Philodendron, Monstera, Anthurium. | xPlant ProOrnamentals, berries, bananas, potatoes, woody stock, medicinal plants, and cannabis where legally permitted. |
| Lineage | MeristemLabLineage visualisation with generation counting and parent-child trees. | xPlant ProLineage from source plant through every subculture, reported by lot and cut week. |
| Beyond the lab record | MeristemLabCulture tracking, media, contamination, dashboards. | xPlant ProThe same, plus media recipes shared publicly, a supplies catalog, and records shaped for a plant-health authority or an exporter. |
| Written guides | MeristemLabA blog. | xPlant Pro21 guides, a history series and public recipes. |
Which one to pick
Two products aimed at the same bench, at different stages of their lives.
Choose xPlant Pro if
You want something in production use today, your team does not all read English, or your lab has to hand a record to somebody outside it — an inspector, an exporter, a customer asking where a plantlet came from.
What one lot's record holds
The record is built on the lot, a lab code and a cut week, and every stage adds to it. When somebody asks, the history is already assembled.
- 1
Initiation
The lot starts under its lab code and cut week.
Lab code and cut week
- 2
Multiplication
Transfers add to the same lot.
Tubs and plants counted at the stage
QR labels for jars, trays and batches
- 3
Rooting
Observations land where they were made.
Contamination logged where it was seen
- 4
Acclimatization
The lot's history reads end to end.
Reported by lot, crop and stage
An overview of what the record keeps, not a protocol.
Where it earns its place
Three moments a lab usually recognises.
Somebody asks for the record
A customer, an exporter or an inspector wants the history of a batch. Open the lot by lab code and cut week and it is already there: each stage, the tubs and plants counted at it, and the contamination seen along the way.
A season's losses need explaining
Contamination is logged where it was seen and reported by lot, crop and stage, so a rise at one stage shows up as a pattern you can point at rather than a feeling at the end of the season.
The spreadsheet has become the problem
Bring the export and the import reads it. Start one crop on the free plan, run it beside the sheet until you trust it, and move the rest when you know.
Where the two records diverge
Both hold cultures, lineage, media and contamination, and both run in a browser with a QR label at the hood. If that is the whole of what a lab needs, the honest answer is that either will do it and the choice is about who you would rather work with.
The divergence is at the edges: what happens when the lab ships across a border, when a regulator asks for the record in its own vocabulary, or when the lab plans by cut week and counts in tubs and plants at the same time. Those are the parts of xPlant Pro that came from a real contract lab's own sheets, and they are the reason the record is shaped the way it is.
Questions a lab asks before it buys
Is xPlant Pro a MeristemLab alternative?
Yes, and the reverse is equally true — the two are close enough in shape that a lab should try both rather than read a table about them. The differences that last are stage, languages and whether the record has to satisfy somebody outside the lab.
Is MeristemLab a competitor or a peer?
Both, honestly. They are building the same kind of record for the same kind of lab, and the category is better for having more than one serious attempt in it. This page exists because people search for the comparison, not because we think they should not exist.
Which is further along?
Their own site describes early access and testing; ours publishes release notes against numbered versions. That is a difference in stage, not in ambition, and stages change.
Can I try both?
Yes, and you should. Both start free. Put the same week of work into each and see which one answers the question you actually ask on a Monday.
We write about this on LinkedIn
Longer thinking on the same problem, from the xPlant Pro company page.
The problem wasn't new. It just became visible.
How variability that experience quietly absorbed at a small scale shows up once there are more cultivars, more batches and more people.
A 2% drop rarely triggers concern
Small changes that are each easy to explain, and the harder question of telling a meaningful change from normal variation across many cultures.
Put the same week into both
One lab code, one cut week, one crop. The free plan takes it, and the comparison stops being a table and becomes your own record.
Free plan to start. No card needed.
Every row about MeristemLab was read from meristemlab.com on 16 September 2026. Plans and prices move; if a row is out of date, it is our mistake and we would like to know. Check any row yourself at meristemlab.com. MeristemLab is their name, not ours, and they do not endorse this page.