Health, home and travel decision
Recipe One
A capable developer can build a useful recipe extractor and personal cookbook web app (narrow workflow) using OSS tools and the Gourmand project, but reproducing the polished native apps, cross-device sync, and any proprietary extraction tuning would be expensive to match.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off120 h to build
$100/mo6 h/mo upkeep
No published price to break even against.
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 Recipe One alternatives, with the arithmetic →
What a replacement has to do
- Ingest a URL/image/video, extract structured recipe data (ingredients, steps, cook time), store and index recipes, UI to view/search/filter and organize into cookbooks, export/share recipe as PDF.
What it still won’t have
- Polished, native iOS and Android apps with App Store ratings and existing users
- Proprietary AI tuning and engineering optimizations behind their extraction pipeline
- Cross-device sync polish and account/session mgmt at scale
- Existing user base, reviews, and curated UX details
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Recipe One does not publish a price we could read, so there is nothing to compare against. What building costs is below.
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 minimal Recipe Keeper web app using Node.js (Express), Postgres, and React; use Tesseract for OCR and youtube-dl/yt-dlp plus ffmpeg to extract video captions/frames, and use a small NLP pipeline (spaCy or an LLM API) to parse ingredients and steps. Core features in scope: (1) accept paste of URL, image upload, or video link; (2) extract structured recipe (title, ingredients, steps, cook time, tags); (3) store recipes and cookbooks in Postgres with full-text search and tag filters; (4) a responsive web UI to save/view/search recipes and a distraction-free cook mode; (5) export recipe to PDF and share link. Out of scope: native mobile apps, cross-device background sync service, and large-scale user management. Include error handling, retries for external fetches, input validation, and unit/integration tests for extraction and API routes.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
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 · 5
Every page the run actually retrieved.
- official productRecipe One: The #1 Recipe Keeper App
- official productRecipe One: The #1 Recipe Keeper App
- official productRecipe One: The #1 Recipe Keeper App
- open sourcemealie-recipes/mealie
- open sourceTomBursch/kitchenowl
Integrity checks
What held up, and what did not.
