Versioned plant registry
Every photo of your monstera, tagged and immutable. Cut a release when it sprouts a leaf. Roll back to the version before you overwatered it. The photo is safe. The plant is a separate conversation.
Repot is an API-first inference platform for houseplants. Point a webcam at your fern, pick a model, and find out what your fern already knew.
Every photo of your monstera, tagged and immutable. Cut a release when it sprouts a leaf. Roll back to the version before you overwatered it. The photo is safe. The plant is a separate conversation.
Your is-this-basil-dead endpoint sits at zero until you panic at 11pm. It spins up in 4.2 seconds, returns a verdict, and scales back down. Billed per leaf-second, rounded up.
Buy a fourth pothos and we provision a fourth GPU. The plant does not know it has a GPU. The GPU does not know it has a plant. The invoice has been fully briefed.
Name it. We assign an endpoint, a region, and a billing identity it never asked for.
Any RTSP feed aimed at the soil. We ingest at 30fps and discard 29 of them.
Pull a verified model from the registry, or fine-tune one on a plant you have already lost.
Get a verdict, a confidence score, and a feeling. Scale to zero between panics.
# install $ npm i -g @repot/cli $ repot login # register a plant $ repot plants create greg \ --species monstera \ --region sill-north-1 # deploy a model and run it $ repot deploy soil-moisture-vibes $ repot run greg --model soil-moisture-vibes → "moist enough, emotionally and literally" (0.91)
I deployed a model to tell me the pothos needed water. It told me what I already knew, with 94% confidence. I have never felt so seen and so audited at the same time.
We migrated the entire succulent shelf to Repot over a weekend. Three of them have since died, but the dashboards are immaculate and the latency is excellent.
The cold starts are faster than my last three therapists. I do not know what the model does. I run it every morning before coffee.
greg is online and waiting to be diagnosed.