Uncategorised decision
Indieworldmap
A single competent developer can reproduce the core site (interactive globe, browse, submit, basic moderation) in about a week; there are no evident durable moats on the product pages to require buying.
Visit website↗Built by Yuyu, who ships 11 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-off34 h to build
$30/mo6 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 a 3D globe, discovers product pins, clicks a pin to view details, and optionally submits a new product via a form.
What it still won’t have
- Existing site SEO and domain age
- Any established user community and existing product listings
- Brand recognition and any proprietary editorial curation
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Indieworldmap 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 an interactive Indie World Map clone using a React frontend (Vite), Three.js (or deck.gl) for a 3D globe, a Node.js + Express API, and Postgres for storage. Core features in scope: render globe with clickable pins, product detail pages, product submission form with validation and reCAPTCHA, server-side moderation endpoint, basic search/filter by tag and proximity, and email notifications on submission. Out of scope: payments, complex analytics, user accounts/social features. Provide error handling, basic unit/integration tests, Dockerfiles for frontend/backend, and a deployment guide for a single VPS or managed host (e.g., DigitalOcean).
How we checked
How the score was reached
- Build verdict base78
- Evidence score78
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 →Integrity checks
What held up, and what did not.
