The travel log, the chain map, the public profile, the loyalty ledger — free, forever. Premium covers everything that takes deliberate configuration to use: planning the next trip, optimising redemptions, scenario comparisons, power-user privacy controls.
Coming from another travel app? See how Pelgrim compares →
For everyone, forever
Everything in free, plus tools for the next trip
No payments yet. Drop your email and we'll write when premium ships. Pricing default: EUR.
Anything that captures or surfaces your past and present is free. Anything that requires deliberate configuration to act on the future is premium: planning the next trip, optimising a redemption, building scenarios, configuring power-user privacy controls. Casual users never bump into the boundary; power users self-select into it.
Logging every flight and stay, building trips from them, the worldwide chain catalog, country and airport pages, basic insights (calendar, map, red-eyes, time zones, fleet, year-in-review), the loyalty balance ledger, the browser extension for capturing balances, basic visibility controls, and shareable trip links. Smart-paste AI parsing is free with a monthly credit cap.
Pelgrim is in alpha. Premium is on the roadmap but pricing and payment integration aren't live yet. Request early access via the button above and we'll email you when it ships.
It's the feature that takes the most deliberate setup (capturing balances, defining trip context, tuning preferences) and the one that delivers the most concrete value (one well-chosen redemption usually beats a year of subscription cost). It's the textbook fit for the deliberate-configuration premium rule.
Nothing is deleted. Your travel log, trips, balances, public profile, shareable links — all stay in your account untouched. The premium tools (planner scenarios, optimizer recommendations, power-user privacy, future-trip mode) become locked. Re-upgrade and everything reactivates immediately.
Not yet. Single-account premium first. Team and business plans land as their own product later, once we know what workflows are most requested.