Health, home and travel decision
Loggd․life
A single developer can build a useful self-hosted habit-and-timer web app (year grid, streaks, timer) using existing OSS components, but reproducing the polished mobile apps, AI integrations, leaderboards and production polish of the paid product is larger work and not covered by the minimal replacement.
Visit website↗$7/mo
$84/yr
Read off the official pricing page.
$100one-off160 h to build
$0/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 2 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
- Record/check habits and tasks, earn XP and see year-grid visualizations.
What it still won’t have
- Native iOS/Android apps and App Store/Play Store distribution
- Polished UI/UX animations and production polish
- Built-in AI integrations (Connect Claude, ChatGPT) and webhooks
- Leaderboards, community features and lifetime purchase handling
- Push notifications / iOS Live Activity (native features)
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
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 self-hosted minimal web habit tracker using Next.js (React) + TypeScript, Supabase (Postgres + Realtime), and Vercel for hosting. In scope: user auth (email/OAuth), Postgres schema for users/habits/tasks/goals/xp/badges, CRUD web UI with a year-grid visualization, a browser focus timer that records sessions and links to tasks, realtime sync (Supabase Realtime or WebSocket) across tabs/devices, background job to compute streaks/XPs and simple analytics endpoints, and CI + Dockerfile for the API. Out of scope: native iOS/Android apps, ChatGPT/Claude integrations, leaderboards and community features. Require input validation, error handling, API tests (unit + integration for core endpoints), and basic end-to-end tests for the main user flows.
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- 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 · 2
Every page the run actually retrieved.
- official productloggd.life — Track Your Life. See your Year
- official pricingloggd.life Pricing — Free, Pro & Lifetime
Integrity checks
What held up, and what did not.
