Health, home and travel decision

WilderTrips

A single competent developer can build and run a minimal WilderTrips replacement in about a week and maintain it; no durable proprietary moats are evident from the supplied page.

Visit website
SubscriptionCustom pricing
Initial build30 hours
Monthly upkeep6 hours + $25
Evidence2/3 runs agree

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

  • Create a multi-day road-trip itinerary, visualize days on a map, save and export the plan

What it still won’t have

  • WilderTrips brand and any proprietary curated trip content
  • Any hosted user accounts, analytics, and cross-user features (if present)
  • Polish, design iterations, and mobile-first UX refinements from the vendor
  • Managed uptime, backups, and support handled by the vendor

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

WilderTrips 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

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 self-hosted road-trip planner web app using Next.js (React) + Node/Express backend, Postgres for storage, and Mapbox for maps. Core features in scope: user sign-up (email/password), create/edit/delete multi-day itineraries with per-day activities, map visualization of route and distances using Mapbox Directions, PDF export of an itinerary, and REST APIs for CRUD. Out of scope: multi-tenant billing, complex recommendation engine, mobile native apps. Include input validation, error handling, unit tests for backend endpoints, and a small deployment guide for DigitalOcean (one droplet) with backups.
How we checked1 sources · 2/3 runs agreed · evidence score 78

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 →

Cited sources · 1

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded