What we publish
- AI itineraries and destination guides for 170+ destinations — Gemini-generated, cached in Redis, formatted as day-by-day plans with real place names, pace metering, and advance-booking warnings for attractions like teamLab Planets or the Louvre that need 1-3 months' lead time.
- Accessibility guides for 10 European cities — sourced from OpenStreetMap contributor tags (real humans verifying venues on the ground) with honest neighborhood terrain ratings and a named human editor who will say “no, this neighborhood is a cobblestone gauntlet” when true.
- Dietary guides (halal, kosher, vegan, gluten-free) for the same 10 cities — OSM
diet:*tags + local-dish compatibility ratings (“always” / “usually” / “ask” / “never”) so you know whether traditional Polish żurek can be made gluten-free or whether you’re just going to be asking a lot of questions at every restaurant. - Visa matrix for nine passports × eight destinations — 72 hand-curated entries, every one backed by an official government source URL (Japan MOFA, Thailand MFA, UAE MOFAIC, Singapore ICA, etc.) with a visible last-verified date. Quarterly manual review.
Why the split
AI generates useful itineraries at scale — fast, cheap, endlessly flexible. It also hallucinates hotels, misses visa requirements, invents ramps that don’t exist, and books people into restaurants that closed two years ago.
Our split-content approach matches the rigour to the stakes. Trip inspiration: AI. Wheelchair accessibility, dietary compatibility, visa requirements: curated, cited, dated. We’re trying to be the reference layer travelers verify AI output against — not another AI content farm. The full protocol — how we source every layer, where AI sits and where it doesn’t, and what our deindex discipline looks like — lives on the methodology page.
Who's behind it
Szymon Łysek — one person, in Bielsko-Biała, Poland. No venture capital, no staff. He writes the code, runs the OpenStreetMap pipeline behind the accessibility and dietary pages, and entered every visa requirement by hand against the issuing country's own authority. The legal entity is a registered Polish sole proprietorship; the formal details are in the privacy policy.
This section used to say “a solo-founder indie project operating from Poland” and name nobody, which was an odd position for a site whose privacy policy, terms and contact page had carried his full name and company registration from the start. On pages about wheelchair access and coeliac safety, the reader is entitled to know who is answering — so here he is, including the audit that found this site's own AI inventing things.
How we make money
Two ways: display ads (Google AdSense) and affiliate commissions when you book a hotel, tour, or travel insurance through our outbound links. Your price is never affected. See our affiliate disclosure.
We don’t favor partners in content — ranking and venue inclusion are based on OSM verification and editorial judgment, not commission rate.
What we don't do
- We don’t book anything directly — all bookings happen at the partner’s site.
- We don’t take your payment.
- We don’t sell your data.
- We don’t use UGC we can’t verify — every community check-in is reviewed before publication.
- We don’t use stock photos in first-party content — only Unsplash images (attributed) or first-party photos from the Tripozi team and contributors.
Where we're going next
Polish-language variant, more passports in the visa matrix, more cities in accessibility + dietary, first-party photo library across all covered destinations, and (eventually) a community-submitted check-in system with moderation. The infra is in place; content scales slower than code, and that’s the point.
Get in touch
Found a closed restaurant, an inaccurate visa fee, a wrong ramp grade, or a beautifully unexpected gem we’re missing? Email [email protected]. We read every message, usually reply within 48 hours.