Health, home and travel decision
Nomads.com
Build a narrow self-hosted city search and scoring frontend/backend yourself, but keep paying if you need Nomads.com's active paid community, large crowdsourced data volume and meetups.
Visit website↗Built by @levelsio, who ships 6 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
$50/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
- Search and filter city profiles; ingest and normalize public datasets (cost, weather, internet, safety); display scores and maps; let a user log trips and view who is in a city now.
What it still won’t have
- Large active paid community and chat/meetups
- Scale of crowdsourced samples and historical dataset volume
- Proprietary ranking history, analytics and reports
- Brand recognition and membership-driven revenue/engagement features
What remains hard
- Brand trust
Millions of people use our software to travel and move to new places and meet people there.
- Brand trust
We have a 50,000+ people member base who log their trips to meet other people in the same place , and chat everyday on Telegram to ask questions, share information and make friends.
First-year cost
No published price
Nomads.com 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 lightweight Nomads-style city discovery app using Postgres, FastAPI, React, and Leaflet. In scope: (1) ETL scripts to fetch/normalize public data (weather, air quality, internet speed datasets) into Postgres; (2) backend endpoints to compute a per-city score and return paginated, filterable search results; (3) React SPA with map and list views, city detail pages, photo voting UI; (4) simple user auth and trip logging; (5) a scheduled job runner (Docker + cron or Kubernetes CronJob) to refresh time-sensitive data hourly. Out of scope: paid membership billing, full chat, large-scale analytics dashboards, and advanced personalization. Include error handling for failed API calls, retries, input validation, basic unit tests for ETL and scoring logic, and an integration test that exercises search -> city page -> trip log flow.
How we checked
How the score was reached
- Partly verdict base52
- 3 cited sources+3
- Evidence score55
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 productNomads.com frontpage
- official pricingNomads.com city search (Beijing)
- official docsNomads.com FAQ
Integrity checks
What held up, and what did not.
