Archive position — measured, not model output
1 like on Devpost
506 of the 7,856 archived projects have more likes, and 1,758 share exactly 1 — so this project's #1,255 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
Jardinly Live is a smartphone-first AI-powered plant doctor built as a progressive web app (PWA), designed to guide users through a live scan of their plants using real-time voice guidance and visual evidence collection. The product claims to combine plant identification, diagnosis, care planning, progress tracking, reminders, and an AI chat into one experience.
The author states that the project was developed during the OpenAI 2026 hackathon, with core technologies including React, TypeScript, Node.js, PostgreSQL, and integrations with multimodal models like GPT-5.6 and Codex. It is described as a working mobile PWA with most features implemented but still in development ahead of submission.
Key commercial due-diligence read
The description does not indicate any revenue, customers, or traction beyond the author's own account. There is no evidence of market validation, pricing, or business model implementation. The single most important open question is whether there is any external validation or early user feedback that would suggest real demand for this product.
What The Product Actually Is
The description states that Jardinly Live is a smartphone-first AI plant doctor built as a progressive web app (PWA). It guides users through a live scan using voice and visual input, collecting evidence from the whole plant, leaves, stems, soil, and environment. The system then generates a structured diagnosis and personalized rescue plan.
It integrates real-time voice guidance, visual evidence capture, plant identification, diagnosis, care planning, progress tracking, reminders, and an AI plant-care conversation into one interface.
Evidence
- "Jardinly Live is a smartphone-first AI plant doctor."
- "It guides the user through a calm live scan, asks for useful views of the whole plant, leaves, stems, soil, and environment."
- "The experience combines real-time voice guidance, visual evidence capture, plant identification, diagnosis, care planning, progress tracking, reminders, and an AI plant-care conversation in one PWA."
Inference
- The product is a digital tool aimed at helping users diagnose and treat plant problems.
Positioning & Claim Evolution
The author positions Jardinly Live as a solution to the difficulty of describing plant problems with a single photo. It claims to offer a calm, guided experience that turns visual evidence into personalized care plans.
Evidence
- "Plant problems are difficult to describe with a single photo."
- "A damaged leaf may be caused by watering, pests, light, soil, or the surrounding environment."
- "Jardinly Live is a smartphone-first AI plant doctor...turning visual evidence into a personalized diagnosis and rescue plan."
Inference
- The positioning suggests an intent to simplify complex plant care issues for non-experts.
Target Customer & ICP
The description does not explicitly define the target customer or ideal customer profile (ICP). It implies that users are plant owners who struggle with diagnosing plant problems, but no demographic or behavioral segmentation is provided.
Evidence
- "Plant problems are difficult to describe with a single photo."
- "Anxious plant owners rarely know which details matter."
Inference
- The product targets individuals who own plants and seek help in identifying and solving plant health issues.
Business Model & Pricing Evidence
There is no evidence in the description of any business model or pricing structure. The author does not state how the product will be monetized, whether it's free-to-use, subscription-based, or otherwise.
Evidence
- No mention of pricing, monetization strategy, or revenue model.
Inference
- The business model remains unknown and unverified.
Technical & Delivery Signals
The project is built using a stack including React, TypeScript, Node.js, PostgreSQL, and Google Cloud Run. It integrates multimodal models such as GPT-5.6 and Codex, and was developed during the OpenAI 2026 hackathon.
Evidence
- "Built with (author-declared): azure-openai, gemini-live-api, google-cloud-run, gpt-5.6, node.js, openai-codex, postgresql, react, typescript"
- "The product is built with React, TypeScript, Node.js, PostgreSQL, realtime multimodal model integrations, and Google Cloud Run."
- "During OpenAI Build Week, GPT-5.6 and Codex were used to extend an existing proprietary Jardinly foundation..."
Inference
- The tech stack suggests a modern, cloud-native approach with AI integration.
Traction & Maturity Signals
The description states that Jardinly Live runs as a working mobile PWA and includes most features such as live scan, diagnosis flow, rescue plan, garden, progress tracking, and AI chat. However, no evidence of traction, user adoption, or customer data is provided.
Evidence
- "Jardinly Live runs as a working mobile PWA."
- "The live scan, evidence collection, diagnosis flow, rescue plan, garden, progress tracking, and AI chat are integrated into the deployed product."
- "Additional Build Week features and the final demo narrative are still being completed before submission."
Inference
- The product is functional but not yet fully released or validated in the market.
Competitive Context
The description does not provide any information about competitors or competitive positioning. No mention of existing solutions in the plant care or AI diagnostics space is made.
Evidence
- No reference to competitors, similar products, or market landscape.
Inference
- The competitive context is unknown and unverified.
Key Risks & Red Flags
Key risks include:
- Lack of traction, revenue, or user data.
- Single-founder team with no external validation.
- Unclear business model and monetization strategy.
- No evidence of market demand or customer feedback.
- Product is described as a hackathon submission, not yet fully released.
Evidence
- "Everything above is the authors' own account. It is not independently verified."
- "No revenue, customer or traction data is available beyond what they state."
Inference
- The lack of external validation and early adoption raises concerns about product-market fit.
Diligence Questions To Ask The Founders
- What specific user problems are you solving, and how do you know?
- Have you tested the product with real users? If so, what feedback did you get?
- How do you plan to monetize this product?
- What is your go-to-market strategy?
- What are the key assumptions in your business model that you’re testing?
- Are there any existing competitors or substitutes in the market?
Investment/Partnership Verdict
Not evidenced — The description provides no information on financials, traction, customers, or revenue. It is a self-reported account of a hackathon project with no external validation.
The author states that the product is functional and includes most features but is still in development. There is no indication of any commercial activity or market validation beyond the author's own claims.
Confidence level Low — based entirely on unverified self-reporting, with no evidence of traction, revenue, or customer data.
Verdict This project appears to be an early-stage idea or prototype, not yet validated in the market. Any investment or partnership decision should be contingent upon further due diligence including user testing, business model validation, and competitive analysis.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.
The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.