TREK Hosting

How TREK works

TREK groups planning material around a trip. Travellers can arrange itinerary entries, places, reservations, documents, packing items, tasks, and shared notes, then invite companions to contribute to the same workspace. Map and schedule views help connect activities to dates and locations, while public links can share selected travel information where the operator chooses to expose it.

Some TREK capabilities depend on add-ons or third-party providers. Mapping, place search, route optimisation, weather, currencies, reservation import, booking-forward workflows, and other integrations may require external services, credentials, compatible data, or optional components. The catalogue configures the core application URL, administrator account, encryption key, data directory, and uploads, but it does not supply provider subscriptions or API keys.

Key TREK features

Itineraries create a shared order for transport, accommodation, meals, and activities. Uploads and trip documents keep supporting files near the plan, while packing lists and tasks turn preparation into assignable work. Collaboration is useful for a trusted group, but participants should receive only the access needed for the trip and public share links should be reviewed before distribution.

The catalogue creates an administrator account and persistent application data. Application email is disabled across hosted services, so mail-dependent password recovery, invitation delivery, and booking-forward workflows are unavailable. Participants may still collaborate through accounts and links supported inside the application, but onboarding must not depend on messages sent by TREK.

TREK vs Wanderlog

TREK and Wanderlog both organise itineraries, maps, reservations, collaboration, budgets, and packing information. TREK is self-hosted and can be extended through its add-on model, while Wanderlog is a provider-operated service with official mobile applications, reservation import, travel discovery, and managed collaboration features.

Wanderlog may suit travellers who want a maintained consumer service, official apps, and provider-managed travel integrations. TREK is more attractive when a group wants a private planning workspace and accepts responsibility for accounts, external providers, add-ons, backups, and the availability of trip data.

Who uses TREK

Families coordinate multi-stop holidays, friends build shared city itineraries, and clubs organise group travel with documents and packing lists. Trip leaders can centralise the current plan while participants update tasks and details instead of exchanging several versions through chat.

TREK is not a booking agent, insurer, emergency service, visa authority, live transport guarantee, or source of verified weather and route conditions. Reservations, prices, opening hours, border rules, and safety information should be confirmed with authoritative providers before travel.

Self-hosting TREK: requirements and cost

TREK resource use grows with traveller count, simultaneous editing, itinerary size, map activity, uploads, documents, reservations, public links, add-ons, and external requests. The catalogue provisions no PostgreSQL or MariaDB service and persists /app/data plus /app/uploads. The software itself is free to run; external travel providers and optional services may have separate limits or costs.

On AvaHost, TREK uses Plan 1 at €2. The hosted TREK package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Application email, booking-forward mailboxes, provider API keys, map or weather subscriptions, reservations, insurance, route accuracy, border advice, and emergency assistance are not included. Review public links, protect the generated administrator account, and verify travel-critical facts with their authoritative source.