Health, home and travel decision

Komoot Premium

A single developer can build a useful route planner, routing API, GPX export and a PWA, but cannot reproduce komoot’s proprietary community route database, polished native apps, and device integrations—so building a narrow replacement is realistic, replacing the full paid product is not.

Visit website
Subscription$5/month
Initial build80 hours
Monthly upkeep8 hours + $150
Evidence2/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

What a replacement has to do

  • Allow a user to find/plan a route, compute turn-by-turn directions, save/export the route, and follow basic navigation on a phone.

What it still won’t have

  • Large community route database and user-contributed highlights/photos
  • Polished native mobile apps and device integrations (Garmin, Wahoo, Apple Watch)
  • Mature offline maps & voice navigation quality from an established product
  • Discovery features, collections, and social/community reach

What remains hard

  • Proprietary data8M + Routes in over 100 countries – for hikes, rides, and runs
  • Proprietary data850M + Photos, tips, and highlights shared by the community
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 32 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

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

Not run yet
Build a minimal route-planning web service and PWA using PostgreSQL + PostGIS, a hosted routing engine (OSRM or GraphHopper service), and Mapbox (or OSM tile host) for tiles. Core features in scope: (1) search POIs and map display; (2) create and edit routes on the map; (3) compute routing and turn-by-turn steps for walking/hiking/cycling profiles via the routing engine; (4) save routes to Postgres and serve JSON APIs; (5) GPX export/import; (6) a mobile-first PWA that displays current location and step list. Out of scope: large-scale community content ingestion, multi-device sync beyond basic JWT auth, native apps, advanced offline map packaging, and device integrations (Garmin/Apple Watch). Include error handling, input validation, logging, and unit/integration tests for routing API and DB persistence. Provide Dockerfiles to run the web app, Postgres+PostGIS, and a local OSRM/GraphHopper container for development.
How we checked5 sources · 2/3 runs agreed · evidence score 57

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 5 cited sources+3
  • Hard moats found in the evidence-3
  • Evidence score57

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.

! Price not confirmed on the page — this pricing page renders its price in the browser! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 2 moats quoted from the page