Project and task management decision

Pestle

A capable developer can build the core save/parse/store/scale recipe workflow in a week and self-host it, but Pestle's native app polish, multi-device households, SharePlay sync, and brand reach are meaningful product differentiators that a DIY replacement would lack.

Visit website
You pay

$1.99/mo

$24/yr

Not verified against a pricing page.

You’d pay instead

$50one-off30 h to build

$25/mo8 h/mo upkeep

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

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Save a recipe URL or upload a photo/PDF, extract ingredients and steps, store the recipe, view and edit cookbook entries, and scale/convert ingredient quantities.

What it still won’t have

  • Polished native iOS app experience and App Store distribution
  • SharePlay synced cooking sessions
  • Households realtime device-to-device sync and multi-user sharing
  • Beautiful widgets and tight calendar sync
  • Lifetime-tier management, gift cards, and built-in discovery features

What remains hard

  • Brand trustLoved by over 90,000 people
  • Switching costsWhen you save a new recipe to your cookbook, it'll instantly be available on all of their devices.
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 15 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 single-tenant web app (Next.js frontend, Node.js + Express backend, Postgres DB, Redis for jobs) that lets a signed-in user save a recipe by URL or by uploading a photo/PDF, extracts ingredients and step text (use node-html-parser and Tesseract OCR fallback), normalizes ingredient quantities and supports unit conversion/scaling, and provides a responsive UI to list, view, edit, tag, and export recipes. Out of scope: native iOS app, SharePlay, multi-user households/real-time sync, app-store distribution, marketing/discovery features. Include background job handling for heavy parsing, error handling for failed extractions, unit tests for parser and API endpoints, and deployment scripts (Docker + one-click deploy to Render).
How we checked2 sources · 3/3 runs agreed · evidence score 57

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score57

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

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✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 2 moats quoted from the page