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 a question travels through PlantAdvocate before it reaches you.

The species record

Every plant in PlantAdvocate is matched to a curated entry in the species database: light needs, watering cadence, humidity range, soil preference, seasonal behavior, common problems. This is verified reference data, not model-generated text.

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, your home, 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, your language

Ask however you'd actually ask — "why are the edges going brown," not a dropdown menu of ten preset symptoms. You get a specific answer back, in plain English, traceable to real data.

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

If your plant's species isn't verified in the database yet, PlantAdvocate says so 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?