Trek

Deploy Trek on a VPS in One Click

Utilities

Self-hosted, real-time collaborative travel planner for groups who plan trips together — itineraries, maps, budgets, and packing lists in one place.

  • Ready in ~3 min
  • Free installation
  • We handle the setup
At a glance
Version
Latest (4.x)
Operating system
Ubuntu Server 24.04 LTS
Minimum RAM
1 GB
License
AGPL-3.0
Addressing
IPv4, IPv6
GitHub
15,000
Deployment~3 min
Open source & self-hosted
VPS plans

Choose a VPS plan for Trek

Blazing-fast NVMe drives and powerful processors. Take a ready-made plan or build the configuration yourself.
Minex
Perfect for personal projects and small websites.
€3.20/mo
Save €0.80 per month

  • 1 vCPU core
  • 1 GB DDR5 RAM
  • 20 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 1 TB traffic
Basex
A great balance of power and affordable price.
€4.80/mo
Save €1.20 per month

  • 2 vCPU cores
  • 2 GB DDR5 RAM
  • 40 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 2 TB traffic
Most popular
Corex
For growing applications and businesses.
€7.20/mo
Save €1.80 per month

  • 4 vCPU cores
  • 4 GB DDR5 RAM
  • 50 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Midex
Resources for high-load projects.
€9.60/mo
Save €2.40 per month

  • 4 vCPU cores
  • 6 GB DDR5 RAM
  • 60 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Proex
Maximum power and scalability.
€12.00/mo
Save €3.00 per month

  • 6 vCPU cores
  • 8 GB DDR5 RAM
  • 70 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Scalex
Resources for scaling.
€16.00/mo
Save €4.00 per month

  • 6 vCPU cores
  • 10 GB DDR5 RAM
  • 150 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Maxex
A large reserve of power.
€44.00/mo
Save €11.00 per month

  • 8 vCPU cores
  • 16 GB DDR5 RAM
  • 200 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Apex
The top configuration.
€79.99/mo
Save €20.00 per month

  • 16 vCPU cores
  • 32 GB DDR5 RAM
  • 400 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic

What you can do with Trek

Trek self hosted is a real-time collaborative travel planner built for groups who'd rather plan a trip together than juggle spreadsheets and scattered chat threads. It combines a drag-and-drop day-by-day itinerary, an interactive map with photo markers and route visualization, budget tracking with per-person splitting, packing lists, and a document manager for tickets and reservations — aimed at families, friend groups, and teams coordinating a company offsite.

What sets it apart is how much of a trip actually lives inside it: flight confirmations, passport scans, hotel bookings, and per-person expenses. That's exactly why Trek VPS hosting makes more sense than waiting for some future cloud edition — none of that data leaves a server you control. Trek also ships an MCP server for AI-agent integration and OIDC login via Keycloak or Authentik, so a self-hosted instance plugs into infrastructure you already run.

The applications screen of the control panel with one-click install

Trek features

A server surrounded by app icons — applications running on a VPS

Trek installation brings the full toolkit for group trip planning out of the box, from the first draft itinerary to the final packing checklist. Below are the core features that make it more than a shared spreadsheet.

01

Drag-and-drop itinerary planner

Organize places into day-by-day plans with reordering and cross-day moves.

02

Interactive map with photo markers

A Leaflet-based map with clustering, route optimization, and place search via Google Places or OpenStreetMap.

03

Real-time collaboration

Changes made by any group member sync instantly to everyone connected over WebSocket.

04

Budget tracking

Category-based expenses with a pie chart, per-person and per-day splitting, and multi-currency support.

05

Packing lists and templates

Checklists with user assignment, admin-managed reusable templates, and optional bag-weight tracking.

06

Document manager

Attach tickets, boarding passes, and PDFs up to 50 MB to trips, places, or reservations.

07

Progressive Web App

Installs on iOS and Android home screens with offline support for maps and cached data.

Requirements

Which server to run it on

Minimum requirements for Trek and the configuration worth starting with.
Minimum
  • CPU1 vCPU
  • Minimum RAM1 GB
  • Disk10 GB
Recommended
VPS Basex
  • CPU2 vCPU
  • Minimum RAM2 GB
  • Disk40 GB

Installation is free — you only pay for the server

Getting started

How to deploy Trek

Three steps and the app is running on your server.
Step 1
Choose a server

Pick a plan with headroom on RAM — Trek keeps WebSocket connections open for live map, budget, and chat sync across everyone in the trip.

Step 2
Pick the app

To install Trek on a VPS, just check it in the app list when ordering — Leneex spins up the mauriceboe/trek Docker container with its built-in SQLite database.

Step 3
Get your credentials

After the Trek one click install finishes, the first person to register in the web UI automatically becomes the admin — panel access details are sent to your email.

Why us

Why Host Trek on Leneex

Speed, protection and support you can rely on — on every plan, with no hidden limits.
Deployment speed
Groups often decide to plan a trip on short notice; the ability to deploy Trek in one click means the shared planner is ready before anyone starts a group chat instead of it.
Free installation
You can try Trek with one trip before deciding if the group will actually keep using it, without paying for the setup itself.
DDoS protection
Trek's invite links are public URLs by design, so anyone with the link can reach your instance — DDoS protection matters even for a "private" planner with modest traffic.
Control and support
Rotating Trek's ENCRYPTION_KEY or restoring a database backup runs through a container shell command; root access and 24/7 engineers mean you're not stuck if that migration script fails mid-trip.
99.9% uptime with SLA compensation
If the planner goes down the day of departure, the group loses access to flight numbers, hotel confirmations, and the day's itinerary all at once — uptime matters more here than for a casual tool.
Flexible payment
A friend organizing a group trip can pay by card or crypto, while a company running an offsite through Trek can get an invoice for its finance team.
What to choose

Trek: Self-Hosted vs Cloud — Which to Choose

We compare cost, control over your data and limits, so the choice is an informed one.
Ready-made SaaS
Self-hosted on LeneexRecommended
Resources and limitsTrip and photo storage typically capped per plan; concurrent collaborators often limited on free tiersDedicated CPU/RAM; WebSocket connections and map/uploads storage aren't shared with other groups
Control and accessNo server access; account tied to the vendor's login systemRoot access; direct control of ENCRYPTION_KEY, OIDC provider, and the SQLite database file
Feature limitsFree tiers commonly cap trip count, collaborators, or document storage; advanced sync often paywalledFull feature set — budgeting, packing templates, document uploads up to 50 MB, MCP/AI integration
ScalingScaling means moving to a higher subscription tierUpgrade VPS resources in a few clicks as more trips and members are added
CostRecurring per-user or per-trip subscription that grows with usageFixed VPS price regardless of trip count or member count
Who it fitsCasual users who want a ready account with zero setup and don't mind data sitting with a vendorGroups and teams that want their travel documents, budgets, and PII kept off third-party servers

Trek doesn't have an official paid cloud edition — the project ships a live demo but no hosted SaaS tier. That makes self-hosting on a VPS the practical way to run Trek with full control over your itinerary and document data, rather than a trade-off against a company-run alternative.

Frequently Asked Questions about Trek on VPS

What people ask most about Trek and our servers.

  • Yes — Trek stores everything in the ./data folder (SQLite database and JWT/encryption secret) and the ./uploads folder; copying both over to the new server and pointing the same Docker Compose volumes at them restores the full trip history.

  • Upgrading resources doesn't touch the data volumes, so trips, budgets, and uploaded documents stay intact — Trek's SQLite database simply keeps running with more CPU/RAM available.

  • Trek's SQLite backend comfortably handles the concurrent-editing needs of a typical family or small team; for a handful of trips and a dozen or so collaborators, the baseline resources are usually enough, though heavier map and document use benefits from more RAM.

  • You are — Trek doesn't auto-update itself; running docker compose pull && docker compose up -d pulls the latest image while your data volumes stay untouched.

What's already set up

The one-click deploy brings up the mauriceboe/trek Docker container with Node.js/Express serving the app on port 3000 internally, backed by a SQLite database that's created automatically at /app/data/travel.db on first boot, plus an /app/uploads volume for attached documents and images. Health checks against /api/health and container restart policy (unless-stopped) are configured out of the box, so the process comes back up after a host reboot without manual intervention.

The at-rest ENCRYPTION_KEY used to protect stored secrets (API keys, MFA, SMTP, OIDC credentials) is auto-generated on first start unless one is supplied.

First login

Trek has no default admin account — the first person to open the instance's URL and complete the registration form becomes the administrator automatically. From there, the Admin Panel (visible in the top navigation once logged in) is where you manage users, invite links, packing templates, and optional integrations like Google Places or an OIDC provider.

Backups and updates

Auto-backups can be scheduled from the Admin Panel with a configurable interval and retention, storing snapshots alongside the SQLite database; restoring one is also done from that same panel. Because Trek doesn't self-update, new versions are pulled manually with a Docker Compose command.

Deploy Trek in about 3 minutes

Choose a server — we do the rest: install, configure and send you the credentials.