"A rented itinerary app forgets you on purpose. That forgetting is the product."
The Market Is Full — and Empty
There is no shortage of travel software. TripIt parses your confirmation emails into a timeline. Wanderlog builds pretty day-by-day itineraries. Google Trips did maps and reservations before it was retired. A Notion template can hold anything. So why build another one? Because every one of those is an itinerary app, and an itinerary app is structurally amnesiac: it helps you organize this trip and then, when the trip ends, the knowledge settles into an archive you almost never reopen. The market is saturated with trip organizers and empty of trip memory.
Whose Data Model Is It?
When you rent, the data model belongs to the vendor. Your trips live in their schema, answer their queries, and surface only what their product decided was worth surfacing. Ask a rented app "which places did I plan across four trips but keep skipping, and why?" and it simply has no shape for the question — because it was never built to reason across journeys, only to organize one. Owning the engine means owning the schema: you decide that a place has a different meaning on every trip, that a recommendation keeps its rationale, that a skipped plan is carried forward instead of deleted. The questions you can ask are bounded by the model you own.
The Same Bet, Three Engines
This is the exact bet Ember and Bonfire made before Waystone. Ember refused to rent A1111 or ComfyUI and built its own image engine. Bonfire refused to rent a tab service or bend a DAW into a teacher and built its own music-learning engine. Waystone refuses to rent an itinerary app and builds its own travel-memory engine. In all three, the thing you refuse to rent is not the feature — plenty of rented apps have prettier features. The thing you refuse to rent is the ownership of your own accumulated context. Rent the feature and you rent the forgetting along with it.