Health, home and travel decision
Getfiit
A competent developer can reproduce the core meal-logging workflow in about a week and maintain it cheaply; no durable moats are visible from the supplied page so self-hosting is realistic.
Visit website↗Built by Michael, who ships 5 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off40 h to build
$20/mo3 h/mo upkeep
No published price to break even against.
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
- User opens app → enter quick meal data (text/photo/select) → save meal to personal log → view history and simple summaries
What it still won’t have
- Brand, polish, and trust of the hosted product
- Native mobile app experience (unless added)
- Any proprietary analytics, user base, or network effects
- Third-party integrations the commercial product may include
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Getfiit 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-first meal-logging app using React (Vite) for the frontend, Node.js + Express for a REST API, and Postgres for storage. Core features in scope: fast single-screen meal entry (text, optional photo upload), user auth via magic links, API endpoints to create/list meals, client-side localStorage fallback and background sync, a simple history page with daily summaries, server-side validation, error handling, and unit tests for API routes. Out of scope: payments, social features, advanced analytics, native mobile builds. Provide Dockerfiles for frontend and backend, a docker-compose for local development, automated schema migrations, and a short deploy guide to a single VPS or a managed service (Heroku/Render).
How we checked
How the score was reached
- Build verdict base78
- 3/3 assessment runs agreed+4
- Evidence score82
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 · 1
Every page the run actually retrieved.
- official productGetfiit — Log a meal in 5 seconds
Integrity checks
What held up, and what did not.
