Health, home and travel decision
Citron App
A capable engineer can reproduce core recipe storage, OCR/image and URL parsing, meal planning, and grocery aggregation (especially using cookcli as prior art), but reproducing Citron's native apps, polished social-video imports, multilingual transforms, and cloud-sync polish is significantly more work—so building a useful subset is realistic but full parity is not.
View on the App Store↗$2.5/mo
$30/yr
Read off the official pricing page.
$100one-off80 h to build
$50/mo5 h/mo upkeep
On cash alone, building overtakes the subscription at 24 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Citron App alternatives, with the arithmetic →
What a replacement has to do
- Import recipe (URL/image/clipboard) → parse into structured recipe (ingredients, steps, metadata) → store recipe → add to weekly meal plan → generate grocery list
What it still won’t have
- Polished native iOS/iPad apps and App Store-managed in-app purchases
- Advanced social-video imports (Instagram Reels, TikTok, YouTube) with audiovisual extraction
- Built-in multilingual translation pipeline and production-quality diet-transformation engine
- Priority customer support and app-review distribution
- Scale-tested cloud sync across multiple devices and users
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 24 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a single-tenant web recipe keeper using Node.js (Express) + React, Postgres, and Redis for background jobs. Core features in scope: (1) web UI to paste a recipe URL, upload images, or paste text; (2) scraper that fetches a URL and extracts recipe HTML; (3) OCR pipeline using Tesseract for images; (4) NLP heuristics to parse ingredients and steps into structured fields; (5) recipe CRUD, collections, a drag-and-drop weekly meal planner, and aggregated grocery list generation with aisle sorting; (6) simple email-based auth, background worker (Bull/Redis) for OCR and scheduled grocery generation, and REST API for a single-user mobile sync. Out of scope: native iOS/iPad apps, automated imports from TikTok/Instagram/Reels/YouTube video audio, advanced diet-transformation AI, paid in-app purchase handling, and multi-user team sharing. Require error handling, unit tests for parsing logic, and end-to-end tests for meal-plan→grocery flow.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score67
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productCitron: Recipe Keeper Cookbook - App Store
- open sourceTandoorRecipes/recipes
- open sourceulsklyc/yuvomi
Integrity checks
What held up, and what did not.
