I got tired of my travel confirmation emails getting buried in my inbox — flight here, hotel there, dinner reservation somewhere in a thread from three weeks ago. So I did the most logical thing: skipped the part where you Google whether a solution already exists, and took the easier path of building my own.
Forward your confirmation emails to a private alias, and Trippy turns them into an organized, mapped itinerary — dates, times, addresses, and contact info all in one place, in order, where you can actually find them at the airport.
The real app runs on my own inbox and is invite-only (it's my stuff, after all). The demo does the party trick in reverse: describe a dream trip in plain text, and it builds you a full mock itinerary — parsed, structured, and mapped — in a few seconds. No account, nothing stored.
- Runtime
- Next.js · Vercel
- Database
- Supabase Postgres · RLS
- Parsing
- Claude · never-invent-data
- Privacy
- Auto-redaction of PII
- Scheduling
- IANA timezone-aware
- Maps
- Server-side geocoding
- Limits
- IP-bucketed rate limiting
- Ingest
- Email-forward pipeline