The most complete open-source travel planner: real-time collaboration, bookings, budgets, packing lists, journals, offline PWA, SSO and an AI-ready MCP server, with planet-wide place search and routing built in.
AI summary: A self-hosted travel planner to visually organize trips, track expenses, and manage reservations with AI assistance.
TypeScriptAGPL-3.0Created Mar 19, 2026Last push 2d agoLatest release v5.1.4+307 stars this week+963 this month
Quick answers
What is TREK?
A self-hosted travel planner to visually organize trips, track expenses, and manage reservations with AI assistance.
What does TREK do?
TREK is an open-source, self-hosted travel planning application serving as an alternative to commercial services like Wanderlog. It provides a highly visual, drag-and-drop interface for users to build comprehensive day plans, plot routes on interactive maps, and collaborate in real-time with other travelers. Beyond route mapping, the platform tracks shared trip budgets, manages ticket reservations, and stores essential documents in one centralized location. Additionally, it integrates a built-in MCP server that allows AI agents to automatically generate packing lists, plan itineraries, and analyze trip costs based on user prompts.
Who is TREK for?
TREK is designed for frequent travelers, homelab enthusiasts, and friend groups who want a private, comprehensive tool to plan and document their trips. It is ideal for users looking for a feature-rich, self-hosted alternative to proprietary travel planners.
How do I get started with TREK?
docker compose up -d
How popular is TREK on GitHub?
liketrek/TREK has 15,814 stars and 1,352 forks on GitHub, and gained 307 stars in the last 7 days.
What license does TREK use?
liketrek/TREK is released under the AGPL-3.0 license.
Star history
since Jul 29, 2026
15.8K stars as of Nov 19, 2026. Measured daily since Jul 29, 2026; GitHub no longer exposes earlier star timestamps.
Update history
4 recorded
Nov 15, 2026New release v5.1.4 (previously v5.1.0).
Nov 1, 2026New release v5.1.0 (previously v4.3.3).
Nov 1, 2026Description changed from "A self-hosted travel/trip planner with real-time collaboration, interactive maps, PWA support, SSO, budgets, packing lis" to "The most complete open-source travel planner: real-time collaboration, bookings, budgets, packing lists, journals, offli".
Oct 4, 2026Previously tracked as mauriceboe/TREK; its 1 daily snapshot and 3 trending appearances were merged into this profile. Stars: 11,124 on 2026-07-29 under the old name, 14,528 on 2026-10-02 (+3,404).
Contribution activity
commits per day, last 52 weeks
4,846 commits in the last yearLessMore
Signals and awards
derived from tracked data
Widely adopted
15,814 stars
Very active
4,846 commits in 52 weeks
Community-driven
~106 contributors
Well documented
High community health score
Continuous integration
Automated checks passing
Repeat trending
3 trending appearances
What TREK does
TREK is an open-source, self-hosted travel planning application serving as an alternative to commercial services like Wanderlog. It provides a highly visual, drag-and-drop interface for users to build comprehensive day plans, plot routes on interactive maps, and collaborate in real-time with other travelers. Beyond route mapping, the platform tracks shared trip budgets, manages ticket reservations, and stores essential documents in one centralized location. Additionally, it integrates a built-in MCP server that allows AI agents to automatically generate packing lists, plan itineraries, and analyze trip costs based on user prompts.
TREK is designed for frequent travelers, homelab enthusiasts, and friend groups who want a private, comprehensive tool to plan and document their trips. It is ideal for users looking for a feature-rich, self-hosted alternative to proprietary travel planners.
Interactive trip mapping: Features a drag-and-drop planner paired with 3D terrain maps to optimize daily travel routes.
Expense splitting: Tracks multi-currency trip costs and calculates who owes whom, similar to Splitwise.
Real-time collaboration: Utilizes WebSockets to instantly sync itinerary changes, chat messages, and polls across multiple users.
Reservation management: Imports and organizes flights, hotels, and tickets from booking confirmation emails or PDFs.
AI automation: Exposes a built-in MCP server allowing AI assistants to plan days, build budgets, and create packing lists.
Where teams use it
Group trip coordination
Friend groups use the platform to collaboratively plan itineraries, vote on activities, and split shared expenses equitably.
Offline travel access
Travelers install the PWA on their mobile devices to access maps, tickets, and plans reliably without cellular service.
AI-assisted itinerary generation
Users connect their AI assistants via the MCP server to automatically draft day-by-day travel plans for new destinations.
Homelab travel archiving
Privacy-conscious individuals host the app locally to securely store their travel history, photos, and passport documents.
Getting started: docker compose up -d
README
main branch
Every part of your trip. One app you own.
TREK has grown from a travel planner into a whole ecosystem for trips: plan together in real time on a live map, build hikes, tours and road trips, keep bookings and shared costs in order, pack, write the journal, lay out the photo book and hand the busy work to the built-in AI. Self-hosted, on the web, on your phone and offline.
PUBLIC SERVICES PROUDLY SPONSORED BY
What you get
See all features
Most of what follows is an addon an admin switches on or off. Lists, Costs, Documents, Collab, Tours, Vacay and Atlas ship on; Journey, Collections, MCP, the AI assistant, AI Parsing, Road trip, Dawarich and AirTrail ship off and are marked below.
🧭 Planning
Day plans: drag places, notes and bookings between days with undo, or drop a map marker straight onto a day
Maps: Leaflet, Mapbox GL or MapLibre GL (OpenFreeMap, no token) with clustering, photo markers, route lines and a whole-trip route overview
Places: search the TREK Places index and OpenStreetMap with no key, or Google Places and Amap with one. Descriptions, hours and photos from Wikipedia, Wikidata and Wikimedia Commons, plus a rating and a custom image per place
Explore: nearby places by category for the map view, from the TREK Places index with Overpass as fallback
Routes: auto-sort a day (nearest neighbour then 2-opt, locked stops and hotels stay put), a travel mode per leg over OSRM or Valhalla, then open the day in Google Maps or CoMaps and a place in seven navigation apps
Public transport: door-to-door itineraries over Transitous, or Google where Transitous has no data
Import and export: Google Maps and Naver Maps lists, Google Maps directions links, GPX, KML and KMZ in; GPX and an ICS feed per trip or across all trips out
Weather: 16-day forecast from Open-Meteo, no key, and the archive for dates beyond it
Trip dates: move a trip and its days re-date themselves, with the bookings along or re-anchored. Trips also copy and archive
Road trip (off by default): drives with stops, day windows and arrival times that recompute, route alternatives, hazards and EV charging with range
🥾 Tours
Seven tour types: hike, city walk, run, bike (touring, road, gravel, MTB), paddle (kayak, canoe, SUP), horse ride, and ski and winter (alpine, cross-country, touring, snowshoe, winter hike)
Routing: legs routed over Valhalla with shaping points, hand-drawn legs, route variants, round hikes of a wished length and trip places as stops, all with undo
Hikes: routed within a maximum SAC grade (T1 to T6), the trail grades along the way, and via ferratas on the map
Terrain: elevation profile, ascent and descent, and a 3D terrain map with grade colouring and a flyover, no token needed. Topo, hiking, cycling and satellite bases with sea marks and ski pistes as overlays
Multi-day tours: one route cut into stages and spread across the trip's days
Along the way: viewpoints, huts, water, food and more within a corridor of the route, inserted as a stop with the detour it adds
Ski, paddle and city walks: a piste router by difficulty and lift type; a water router with portages, locks and a wind forecast; city walks with stays, opening hours and transit between stops
Plan against reality: link a recorded GPX to a planned day and compare distance, ascent and time. Import trails from a wanderer instance, save tours to a collection and take them into another trip
🧳 Bookings and money
Reservations: 18 booking types with status, confirmation code, travellers and attached files
Flights and trains: several legs with stopovers and endpoint timezones, against 4,045 bundled airports so local times resolve without a key
Accommodation: a stay spans a range of nights with a check-in window
Booking import: EML, PDF, PKPass, HTML, TXT and photos of confirmations, through KItinerary or an AI model, with a review step before anything is saved. Prices become linked costs
AirTrail (off by default): import flights from a self-hosted AirTrail instance and keep them in sync
Costs: split in integer cents with equal or custom shares, several payers, settle-up suggestions, a per-person summary, a settlement log and CSV export. A receipt photo can fill in an expense
Currencies: one per expense with the rate frozen at entry, from Frankfurter with no key
Packing lists and to-dos: categories, templates, assignees and visibility tiers; bags with weights as an admin switch; to-dos with due dates, priorities and reminders
Files: attach to a trip, place, day or booking, 50 MB each and 500 MB for video, with trash and restore
PDF export: cover, place photos, day notes, bookings and costs, with an optional page break per day
👥 Collaboration
Real-time sync (WebSocket): edits land live for everyone who has the trip open
Members: add by email or username, hand over ownership, or add guests who have no login at all
Permissions: an admin maps each of 17 trip actions to admin, trip owner, trip member or everybody
Invites: one reusable link per trip with an optional expiry, and admin signup invites that drop a new account straight into a trip
Public share: a read-only trip page without an account, with switches for map, bookings, packing, costs and chat
Collab: group chat with replies, reactions and link previews, shared notes, links, polls and a What's Next list, each one its own switch
Notifications: an inbox grouped by day with answers right from the notification, and a per-user matrix of events against in-app, email, webhook, ntfy, Web Push and plugin channels
📔 Journey and TREK Studio
Journey (off by default): dated entries with story, mood, weather and tags, photos and video from uploads, Immich or Synology Photos, map views, co-authors, drafts and a public share link
Linked journal: a trip can show one journal as its own, with the members picked on the trip as viewers or editors
Recorded days (with Dawarich): keep a day's recorded route and turn its stays into entries
TREK Studio: turn a journal into a printable photo book. 34 print-licensed typefaces, 17 themes, 108 designed pages in twelve styles, 160 recolourable stickers, text effects, layers and a Travel tab with route maps, country stamps and trip figures
Auto layout: lays the whole book on the designed pages in the style of its theme, every photo in a frame, or rebuilds one spread
Print and share: PDF export as pages or spreads with crop marks, several people editing at once, and design files to move a spread into another book
🗺️ Atlas, Vacay and Collections
Atlas: countries and regions visited on geoBoundaries outlines, a bucket list, travel stats, and a tour activities tab with planned against recorded totals
Vacay: leave calendar with half days, public holidays from nagerholidays.com, school holidays for 16 European countries, company holidays, carry-over between years, and joint or read-only sharing
Collections (off by default): a place library outside any trip with lists, labels, ratings, a status per place, cover images, GPX and file export, copy into a trip, and sharing by invite
Dawarich (off by default): link a Dawarich instance for recorded tracks, suggested stays and countries for the Atlas
🤖 AI assistant and MCP
AI assistant (off by default): a chat that plans with you in a trip, across all your trips, in a journal and in Studio, and works with tours, costs, bookings, packing, Vacay and the Atlas
Your own model: an API key for Anthropic, OpenAI, Gemini or OpenRouter, a ChatGPT plan, or any OpenAI-compatible endpoint, set for the instance or per user
You stay in charge: reads run at once, every change waits as a card to apply or discard and can be undone for 15 minutes. Nothing leaves before you agree to the provider, and a file's text only with your consent
Attachments: drop a booking confirmation, a GPX file or a photo into the chat, and the assistant offers what to do with it
MCP server (off by default): OAuth 2.1 with mandatory PKCE and dynamic client registration, 410 tools, 30 resources and 4 prompts, 35 scopes in 17 groups ticked on the consent screen, and every call in the audit log
Addon-aware: twelve addon gates decide which tools a session sees, and flipping one re-registers live sessions
🧩 Plugins
Third-party plugins: install from the TREK registry or sideload a zip, with their own pages under /plugins/<id>
Sandboxed: one child process per plugin, 66 grantable permissions, an admin-edited outbound host allowlist, memory and call caps
Trust: registry downloads are pinned by sha256 and checked against the author's minisign key, a sideloaded zip is marked unverified, and TREK_PLUGINS_ENABLED=false turns the whole system off
Extension points: map layers, place details, day schedules, PDF sections, Atlas layers, journal rows, trip warnings, search and photo providers, route profiles, notification channels and MCP tools
SDK: trek-plugin-sdk with a CLI to create, validate, run against real data, sign and publish
📱 Mobile and offline
Apps: TREK Travel Planner for iPhone, iPad and Android connects to any TREK server, and the browser installs TREK as a standalone app with a themed status bar too
Phone layouts: their own screens for every part of the app, with a bottom bar and dashboard widgets the user orders
Offline reads: the app shell is precached and trips, places, tours, files and nearby places live in a per-user IndexedDB store, so a trip opens with no network
Offline writes: changes queue and replay with an X-Idempotency-Key, and a stale edit waits for a keep-mine or keep-theirs choice
Offline maps: raster and vector tiles of a trip downloaded ahead, and a switch that takes the whole app offline on purpose
⚙️ Admin, accounts and security
Sign-in: password, OIDC and passkeys each switch on and off on their own, OIDC_ONLY leaves SSO as the only way in, and an OIDC claim can grant admin
SSO and 2FA: one OIDC provider by discovery with PKCE (Authentik, Keycloak, Google and the like), TOTP with backup codes that an admin can require, and passkeys that count as the second factor
Sessions: every sign-in is a session you can see and end, one by one or all others at once
Hardening: rate limits on sign-in, reset and 2FA, a password policy, secrets encrypted at rest and masked on read, and an SSRF guard on every URL you configure
Admin panel: users and the permission matrix, defaults for new users, categories and templates, addons, plugins, storage, notifications, MCP tokens, backups, audit log and releases
Backups and storage: scheduled backups with retention that restore their own secrets, and local or S3-compatible storage per content category with replicas
Appearance: light, dark or follow the OS, seven colour schemes plus a custom accent, transparency, density, reduced motion and text size
28 languages: en, de, es, fr, it, nl, hu, ru, zh, zh-TW, pl, cs, ar (right to left), he (right to left), br, id, tr, ja, ko, uk, gr, sv, vi, ca, az, et, sk, th
Help center: a ? in the top bar with 381 step-by-step guides with screenshots, searched together with the wiki that ships in the image
Every TREK installation in the world searches through servers that dataforest cloud sponsors.
The place index with over 88 million places, the address search in every TREK language and the planet-wide routing all run on dataforest cloud in Frankfurt, Germany, free of charge for everyone who self-hosts TREK. Without this sponsorship, these services would not exist in this form.
Thank you, dataforest, for backing open source this generously. 💚
Looking for a server for your own TREK? dataforest cloud is where TREK's own services live.
AI usage
We use LLM-assisted coding tools across parts of this codebase. Nothing ships that a
maintainer has not read and understood: every change goes through a pull request, is
reviewed and tested, and has a human who can answer for it. "The AI wrote that" is not
an answer any of us would accept from ourselves.
Open http://localhost:3000, or http://<server-ip>:3000 from another machine. On first boot TREK seeds an admin account — if you set ADMIN_EMAIL/ADMIN_PASSWORD those are used, otherwise the credentials are printed to the container log (docker logs trek).
COOKIE_SECURE=false is only for trying TREK over plain HTTP: without it the browser drops the session cookie and the login does not stick. Once TREK sits behind HTTPS (see Reverse Proxy), remove it.
No server yet? TREK's own public services run on dataforest cloud, our infrastructure sponsor. A small seed is plenty for a TREK instance and is ready within a minute.
Real-time sync via WebSocket (ws). Backend on NestJS 11. State with Zustand. Auth via JWT + OAuth 2.1 + OIDC + Passkeys (WebAuthn) + TOTP MFA. Weather via Open-Meteo (no key required). Maps with Leaflet and Mapbox GL.
Docker Compose (production)
The repository ships a ready-to-use docker-compose.yml
with secure defaults and every option documented inline. Download it, then:
TREK works as a Progressive Web App, and the TREK Travel Planner app for iPhone, iPad and Android connects to the same server (Native Apps). To install the web app instead:
Open TREK in the browser (HTTPS required)
iOS: Share ▸ Add to Home Screen
Android: Menu ▸ Install app (or Add to Home Screen)
TREK then launches fullscreen with its own icon, just like a native app.
Updating
See Updating — Docker Compose,
Docker run, Helm, Portainer, Unraid, TrueNAS SCALE and Proxmox, plus the encryption-key note.
Reverse Proxy
For production, put TREK behind a TLS-terminating reverse proxy. TREK uses WebSockets for real-time sync, so the proxy must support WebSocket upgrades on /ws.
If you use the MCP addon, the proxy must also pass the Mcp-Session-Id header through in both directions on /mcp — Nginx and Caddy do this by default, but a proxy that strips it makes every tool call open a new session instead of reusing one. See the Reverse Proxy wiki page for details.
Nginx
server{listen80;server_name trek.yourdomain.com;return301 https://$host$request_uri;}server{listen443ssl http2;server_name trek.yourdomain.com;ssl_certificate /etc/ssl/fullchain.pem;ssl_certificate_key /etc/ssl/privkey.pem; # 500 MB covers backup-restore uploads (capped at 500 MB server-side).client_max_body_size500m;location / {proxy_passhttp://localhost:3000;proxy_http_version 1.1;proxy_set_header Host $host;proxy_set_header X-Real-IP $remote_addr;proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;proxy_set_header X-Forwarded-Proto $scheme;}location /ws {proxy_passhttp://localhost:3000;proxy_http_version 1.1;proxy_set_header Upgrade $http_upgrade;proxy_set_header Connection "upgrade";proxy_set_header Host $host;proxy_read_timeout86400;} # Only needed if you use the MCP addon. Responses are Server-Sent Events, # so buffering must be off or tool results arrive late.location /mcp {proxy_passhttp://localhost:3000;proxy_http_version 1.1;proxy_set_header Host $host;proxy_set_header X-Real-IP $remote_addr;proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;proxy_set_header X-Forwarded-Proto $scheme;proxy_buffering off;proxy_read_timeout3600s;}}
The Atlas map's country and sub-national (province/county) boundaries come from
geoBoundaries (Runfola et al., 2020), licensed
CC BY 4.0; Ireland's counties come from
Tailte Éireann, also CC BY 4.0. See
NOTICE.md for full third-party attributions.
License
TREK is AGPL v3. Self-host freely for personal or internal company use. If you modify and offer TREK as a network service to third parties, your modifications must be open-sourced under the same licence.
## 5.1.4
[Full diff since 5.1.3](https://github.com/liketrek/TREK/compare/v5.1.3...v5.1.4)
This release keeps Vacay's public holidays working past January 2027, when the old holiday API ends, and fixes AirTrail sending its stored API key to a newly entered address. Update before February; the apps for iPhone, iPad, Apple Watch and Android are still in a closed test, and you can join: 👉 **[Sign up at liketrek.com/app-test](https://liketrek.com/app-test)**.
### Added
- Bakeries and groceries on the map and along a hike ([#3026](https://github.com/liketrek/TREK/issues/3026)). The map's place search and a tour's stops along the route also find bakeries and supermarkets, for restocking on a multi-day hike.
- Settings say what they reach. On a phone and in the app the sections stand under "Your account", which follows you to every device, and "This device".
- An install guide for TrueNAS SCALE in the wiki ([#3060](https://github.com/liketrek/TREK/issues/3060)), from the TrueNAS Community catalog, including updates.
### Fixed
**Security**
- AirTrail kept its API key for a new address. Saving the settings with another host and the key field left as it was kept the stored key, and t
## 5.1.3
[Full diff since 5.1.2](https://github.com/liketrek/TREK/compare/v5.1.2...v5.1.3)
This release fixes the SSO sign-in of the TREK apps, which kept many testers of the closed app test from signing in at all. If you run TREK with SSO and test the app, please update your server; the app itself needs no update for it. The next app build will ask for TREK 5.1.3 on the server, so it is worth updating now.
The apps for iPhone, iPad, Apple Watch and Android are still in a closed test, and you can join. 👉 **[Sign up at liketrek.com/app-test](https://liketrek.com/app-test)** and connect the app to a TREK server on the newest version, such as this one, or to the demo; please don't test with TREK Cloud.
### Fixed
**Sign-in**
- Signing in to the app with SSO or a passkey still ended in the web app for many. A browser that had run TREK before 5.1.1 keeps that version in its service worker, and the worker answered the app's handoff page from its cache with a version that has no such page, so the sign-in ended on the dashboard in the browser instead of in the app. The app now starts its sign-in on a page the server always answers itself; it takes the old worker off the browser, and
## 5.1.2
[Full diff since 5.1.1](https://github.com/liketrek/TREK/compare/v5.1.1...v5.1.2)
### Test the TREK apps
**The TREK apps for iPhone, iPad, Apple Watch and Android are in a closed test, and you can join.** They run on your own TREK server and add what a browser cannot: home and lock screen widgets, an Apple Watch app, encrypted push notifications, offline maps, sharing from any app into a trip, Wallet passes, and layouts made for iPad, tablets and foldables.
👉 **[Sign up at liketrek.com/app-test](https://liketrek.com/app-test)**: pick Apple or Android, tick the devices you can test on, and leave the email of your Apple ID or Google account. Connect the app to a TREK server on the newest version, such as this one, or to the demo; please don't test with TREK Cloud.
### Fixed
**Photos**
- Synology Photos: journey photos took the capture date and place of the next photo. On libraries where Synology's item and thumbnail ids match, the metadata came from the neighbouring item; TREK now takes only the item the thumbnail belongs to. Photos attached before this release are asked again once after the update and get their own date and place back. (Closes #3019)
**Trips and pa
## 5.1.1
[Full diff since 5.1.0](https://github.com/liketrek/TREK/compare/v5.1.0...v5.1.1)
### Test the TREK apps
**The TREK apps for iPhone, iPad, Apple Watch and Android are in a closed test, and you can join.** They run on your own TREK server and add what a browser cannot: home and lock screen widgets, an Apple Watch app, encrypted push notifications, offline maps, sharing from any app into a trip, Wallet passes, and layouts made for iPad, tablets and foldables.
👉 **[Sign up at liketrek.com/app-test](https://liketrek.com/app-test)**: pick Apple or Android, tick the devices you can test on, and leave the email of your Apple ID or Google account. Access goes out once the builds pass Apple's and Google's review. Connect the app to a TREK server on the newest version, such as this one, or to the demo; please don't test with TREK Cloud.
### Fixed
**Assistant**
- The assistant on Claude Sonnet 5.5 came back without an answer. The model at times ended a turn on its follow-up suggestions alone; it is now asked for the answer, and the suggestions show under it. (#2930, Closes #2789)
- A chat failed with HTTP 400 after leaving the page. Leaving while the assistant
## 5.1.0
[Full diff since 5.0.1](https://github.com/liketrek/TREK/compare/v5.0.1...v5.1.0)
### Highlights
**TREK now runs its own map services, on servers sponsored by [dataforest cloud](https://cloud.dataforest.net/en?mtm_campaign=trek).** Place search, address search and routing come from TREK's own servers instead of public services that limit, slow down or drop requests. Every installation is connected on its own, without any setup. A big thank you to [dataforest](https://cloud.dataforest.net/en?mtm_campaign=trek), who make all of this possible for every TREK installation: cloud servers made in Germany, in Frankfurt, billed by the hour.
- **Routes that match the road.** Every day, road trip and assistant route is calculated by TREK's own planet-wide Valhalla with elevation data. It knows road classes, turns, tolls, ferries and climbs, so routes and driving times come far closer to what you will actually drive.
- **The right place first.** Search now finds the place you mean far more often, and answers three times faster.
- **Place details in milliseconds**, from TREK's own copy of OpenStreetMap instead of the public Overpass servers.
- **Place details from the wh
Code frequency
additions and deletions
+3.6M lines added, -911K removed over the last year.
Commits per week
last 52 weeks
4.8K commits in the last 52 weeks.
When work happens
weekday and hour
Commit volume by weekday and hour (UTC). Larger dots mean more commits.