Health, home and travel decision
Carbsy
A capable engineer can reproduce the core photo→ingredient→nutrition workflow in about a week using cloud vision and an open nutrition DB, but matching the polished native app experience, App Store distribution, subscription handling, and continuous AI accuracy improvements makes a full replacement nontrivial.
View on the App Store↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off34 h to build
$50/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 Carbsy alternatives, with the arithmetic →
What a replacement has to do
- Take a photo or text/voice description → detect ingredients and portions → lookup nutrition values and estimate carbs/macros/glycemic impact → store and display a meal log with edit capability.
What it still won’t have
- Polished native mobile UI and App Store distribution
- Ongoing AI model tuning and accuracy improvements
- In-app purchase/subscription handling and family-sharing integration
- Multi-modal chat-driven editing polish and animations
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Carbsy 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 web replacement for Carbsy using React (frontend), Node.js + Express (backend), and Postgres. Core features in scope: (1) upload a meal photo or enter text/voice (speech-to-text) and send to backend; (2) call a cloud Vision API to extract ingredient labels and return candidates; (3) map ingredients to a nutrition table (CSV or simple DB) and compute carbs, macros, and a simple glycemic-impact heuristic; (4) store meals with timestamp and allow editing ingredients/portions and duplicating meals; (5) a scrollable meal log and simple meal-card UI. Out of scope: native iOS app, App Store in-app purchases, subscription billing, advanced model fine-tuning, and multi-language localization. Include error handling, input validation, and unit tests for API endpoints and nutrition calculation logic.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 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 · 3
Every page the run actually retrieved.
- official productCarbsy on the App Store
- open sourcewger-project/wger
- open sourcesimonoppowa/OpenNutriTracker
Integrity checks
What held up, and what did not.
