How it works

Four layers between your plant and an answer you can trust.

Nothing about your plant's care advice is improvised. Here's exactly how advice is put together before it reaches you.

The species record

Every plant in PlantAdvocate is matched to its species in the catalog: light needs, how dry the soil should get between waterings, humidity, soil, temperature, size, and toxicity. Each value is cited to the extension service or botanical garden that published it, not written by a model.

Your plant's living record

Every watering, every repot, every "the leaves look a little sad today" note builds a real history. This is the context no generic plant app has, because it's specific to your plant, its growing area, your habits.

The advocacy engine

This is the layer that does the reasoning. Its job is narrow on purpose: read the species record and the plant's history, then work out what's actually going on — never to supply facts that aren't already in the record.

Plain language

The Gnome tells you what your plant needs in plain English — specific to that plant, and traceable to cited facts. Every species page shows which source each care fact came from.

Most plant apps skip straight to layer 3.

They answer a care question with no species record and no plant history behind it — which means they're guessing, fluently. PlantAdvocate won't answer a question the data can't support.

01

No record, no answer

When the catalog has no cited value for something, PlantAdvocate says it has no record instead of improvising.

02

History changes the advice

The same species with different watering history gets different, specific guidance — not a one-size answer.

03

You can always ask "why"

Every recommendation can point back to the specific fact and the specific signal that produced it.

Curious what your plant would say?