Health, home and travel decision
Pokédex Checklist
A single technical user can reproduce the core checklist functionality in about a week; there are no strong durable moats shown on the site that prevent a DIY replacement.
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-off31 h to build
$10/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
- Browse National Pokédex entries, mark owned cards, persist a personal checklist, and import/export progress.
What it still won’t have
- Official branding, domain & traffic/SEO built by the existing site
- Any proprietary curated catalog or licensed card images the site may host
- Built-in analytics, user accounts, or integrations the product provides
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Pokédex Checklist 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 single-developer Pokédex checklist web app using React, Node.js (Express), and Postgres deployed to a $5/month VPS (or Vercel for frontend + a small managed Postgres). Core features: import a JSON/CSV catalog of National Pokédex TCG entries with thumbnails; responsive checklist UI with search, filters, and per-card owned/quantity toggles; backend REST API to save per-user progress (simple email + magic-link auth or local-only option); CSV/JSON import-export of progress; CDN-backed thumbnail storage. Out of scope: payment processing, multi-tenant billing, advanced analytics, mobile native apps. Include error handling, input validation, automated tests for API endpoints, and deployment scripts (Dockerfile, simple CI).
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.
Integrity checks
What held up, and what did not.
