Health, home and travel decision

Crouton

A competent engineer can build a useful Crouton-like web replacement (import, OCR, scaling, meal planner) in a few weeks; the product’s durable value appears to be platform polish and Apple-native sync rather than proprietary data or network effects, so building is reasonable.

Visit website
You pay

$1.99/mo

$24/yr

Not verified against a pricing page.

You’d pay instead

$100one-off80 h to build

$25/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 17 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 Crouton alternatives, with the arithmetic →

What a replacement has to do

  • Save recipes (URL/photo/text) → extract & normalize ingredients/steps → store in DB → assign recipes to a weekly meal plan → generate shopping list and scaled ingredient quantities.

What it still won’t have

  • Native iOS/iPadOS/macOS/visionOS/watchOS apps and App-Store distribution
  • iCloud Sync across Apple devices
  • Vendor polish, accessibility and native multi-timer UX
  • Press kit / marketing and ongoing product support

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 17 seats.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a minimal recipe organizer & meal-planner web app using Next.js (React), PostgreSQL, and Node.js. Core features: (1) paste-a-URL importer that fetches a page, extracts title/ingredients/steps (use Readability/Mercury-style parsing + heuristics), (2) photo upload OCR for recipes (Tesseract or Google Vision API) with ingredient/step extraction, (3) normalize ingredients and implement unit conversion and recipe scaling, (4) CRUD API and DB schema for recipes, photos, and weekly meal-plan slots, (5) UI to assign recipes to week/day slots and produce a consolidated shopping list, (6) multiple timers per recipe step. Out of scope: native iOS/visionOS/watchOS apps and iCloud sync. Requirements: include input validation, graceful failure modes for parser/OCR errors, authentication (email+password or simple JWT), automated tests for parsing/scaling and API endpoints, Docker-compose for local dev, and deployment instructions for a single VM (e.g., DigitalOcean).
How we checked6 sources · 2/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 6 cited sources+3
  • Evidence score60

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 · 6

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! Price not confirmed on the page - this pricing page renders its price in the browser! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded