TREK is a self-hosted, real-time collaborative travel planner — with maps, budgets, packing lists, a journal, and AI built in. Runs on your server, owned by you, ready in two minutes.
An itinerary you can think with. Places snap into days, days reshuffle in seconds, and the map updates while you're still deciding.
Drag a place between any two days. Reservations and notes follow.
OpenStreetMap by default. Google Places if you want it. Your choice.
One click reorders by distance. Send the day to Google Maps for turn-by-turn.
Open-Meteo forecasts per day, baked into the itinerary. No keys.
Everyone edits the same itinerary at the same time. Live presence, notes, polls, chat — without leaving the trip. WebSocket sync, no refreshes, no merge conflicts.
Stop juggling Notion, Sheets, Tripit and Splitwise. The boring parts of a trip live next to the fun parts — so you actually look at them.
Confirmation numbers, files, status. Surfaced on the day they happen.
Multi-currency. Per-person, per-day. No spreadsheet required.
Templates per trip type. Assign items to people. Check off as you go.
A trip is one weekend. The bigger picture is the years of them. Turn on what fits — leave the rest off.
Every country you've set foot in, every continent left to go. A bucket list that's also a map, also a habit tracker.
Plan your time off across the whole year. Public holidays, weekends and carry-over are tracked automatically, so you always see how many vacation days you have left.
Magazine-style spreads from your trip. Photos pulled from Immich or Synology Photos. Maps, moods, captions — auto-laid out, hand-curated.
Arrival in Shinjuku
+27
TREK ships an MCP server with OAuth 2.1. Add it once as a connector in Claude, Cursor or your own agent — and let the AI read the itinerary it's asking about.
No copy-paste. No “let me explain my plan again.” It just sees Day 3.
"You land in Tokyo at 14:20 — Shibuya Sky is open until 22:30. If we skip Meiji Jingu today, you'd make Shibuya Sky for golden hour. Want me to shuffle Day 1?" Claude · with TREK connected via OAuth
TREK runs on the box you choose. Not somebody else's cloud, not as a side-effect of a free tier. Your itinerary, your photos, your group chat — all on hardware you control. That's the only mode.
JWT sessions, OAuth 2.1, OIDC SSO with your IdP, TOTP MFA. Bring Authelia, Authentik, Keycloak — TREK speaks them all.
Scheduled snapshots with retention policies. Restore a trip from Tuesday. Or last week. Or 30 days ago.
Including Arabic. The whole app — dates, currencies, plurals — is internationalized, not just the menu items.
Users, invites, templates, API keys, deployment history, GitHub releases — all in a UI you'll actually open.
A live TREK instance with a sample Lisbon trip, four collaborators, and every addon turned on. Resets every hour.
Try the live demoDocker pulls the multi-arch image. Data lives in a single SQLite file on a volume — no external database to run. SSL is your reverse proxy's job — TREK doesn't care which one.
# One container. Data lives in a single SQLite file on the volume. $ docker run -d --name trek \ -p 3000:3000 \ -v trek_data:/app/data \ -e ENCRYPTION_KEY=$(openssl rand -hex 32) \ mauriceboe/trek:latest # open http://localhost:3000 and create your first user
Try the demo, or pull the image and have your own running before the kettle boils.
