The story
Why a garden needs a memory.
By Gardn Labs Limited · 9 May 2026 · 6 min read
Ask a good gardener why something’s struggling and they rarely answer straight away. They ask questions first: when did you plant it, what’s the soil like, what was last winter like here. The advice that follows is only as good as the memory behind it.
Most apps start from zero.
Open a typical garden app and it knows nothing about you. It can identify a leaf, or remind you to water on a Tuesday, but it can’t tell you that this maple scorched in the same spot last August, or that the lavender you keep replacing hates your heavy soil. Every session begins from scratch, so every answer stays generic.
That’s the gap Gardn is built to close. Not a smarter reminder, not a bigger plant encyclopaedia — a memory.
Context is the whole point.
When Gardn knows your dahlia is in the west border, that you fed it three weeks ago, and that frost is forecast tonight, the advice stops being a fact about dahlias in general and becomes a sentence about your dahlia. That’s the difference between information and help.
You can’t take a garden’s memory with you. So we keep one for yours.
It compounds, quietly.
The longer you use Gardn, the more it has to work with. A border photographed across two springs tells a story a single photo can’t. A plant that struggled and recovered is a lesson the app carries forward. None of this needs effort from you beyond the gardening you were doing anyway — the memory builds in the background.
And it stays yours.
A memory this personal has to be handled carefully. Your garden’s record is yours — kept for your benefit, not packaged up as someone else’s product. That’s a promise we’d rather make plainly than bury in a policy.