Health, home and travel decision
Savor
A technical user can build a working self-hosted replacement for scheduling groups, voting, recipes, and grocery lists, but Savor's curated content, membership perks (mail club), and brand polish would be lost — full parity with the paid product isn't realistic without editorial and fulfillment operations.
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-off60 h to build
$0/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 Savor alternatives, with the arithmetic →
What a replacement has to do
- Group members pick a recipe and date, vote, receive a grocery list, then connect to cook together.
What it still won’t have
- Curated, editorial recipe content and brand polish
- Physical membership perks (monthly mail club)
- Polished UX, community features, and any proprietary member systems
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Savor 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 small web app (Node.js + Express, Postgres, React or Svelte frontend) that lets authenticated users create or join 'groups', browse and add recipes, propose events (recipe + date), vote on proposals, and generate a consolidated grocery list from the winning recipe. In scope: user auth (email/password + session), group CRUD, recipe schema (title, ingredients, steps, image), event proposals and vote tallying, shareable grocery-list view, basic responsive UI, tests for API endpoints, Docker-based deployment and documentation. Out of scope: physical mailing fulfillment, payment processing for memberships, heavy editorial content curation, analytics dashboard. Require error handling, input validation, and unit/integration tests for core APIs.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 6 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 · 6
Every page the run actually retrieved.
- official productSavor - Cook Together (home)
- official productSavor - Cook Together (how it works text)
- official productSavor - Cook Together (grocery list)
- official productSavor - Membership features
- open sourceTandoorRecipes/recipes
- open sourceulsklyc/yuvomi
Integrity checks
What held up, and what did not.
