Wanderer
Decentralized, self-hosted trail database for GPS tracks and routes
AI Summary
Wanderer is an open-source, self-hosted trail database for outdoor enthusiasts. The tool enables uploading and managing GPS tracks, planning new routes and importing existing trails from Komoot or Strava. Through ActivityPub integration, users can share routes decentrally and follow others.
✓ Pros
- + Complete data control through self-hosting without vendor lock-in
- + Decentralized networking via ActivityPub with other platforms like Mastodon
- + Direct import from Komoot and Strava without file conversion
- + Comprehensive JSON API for automation and extensions
✗ Cons
- − Requires own server and technical know-how for self-hosting
- − As a relatively new project, potentially limited community and instances
Use Cases
- → Centrally manage and make GPS tracks from hiking and cycling tours searchable
- → Import and consolidate existing trail history from Komoot and Strava
- → Plan new routes and share them with other users via federated instances
- → Discover trails from other users, comment and follow via ActivityPub network
Who is it for?
Ideal for privacy-conscious hikers, cyclists and outdoor enthusiasts who want to self-host their trail data and share it decentrally.
Tags
What is Wanderer?
Wanderer is an open-source application for self-hosted management of GPS tracks and outdoor routes. Users who prefer not to store their tour data with Komoot or Strava can run Wanderer on their own server, keeping full control over tracks, metadata and sharing permissions. Existing data can be imported directly from Komoot and Strava without manual file conversion. New routes can be planned inside the tool. The key difference from pure file storage solutions is the ActivityPub integration: Wanderer speaks the same protocol as Mastodon, so users on different instances can follow each other and share routes in a federated way.
Core features
- GPS track management: Upload, organise and browse your own tracks on self-operated infrastructure.
- Route planning: Create new routes directly in Wanderer, without external tools.
- Import from Komoot and Strava: Bring in and consolidate an existing trail history without file conversion.
- ActivityPub networking: Share routes across instance boundaries, follow other users and comment on trails.
- JSON API: Query tracks and metadata programmatically to build automations and custom integrations.
Who is Wanderer for?
The primary audience is hikers and cyclists who do not want their movement data stored on third-party platforms. Wanderer is most practical for anyone already running a self-hosting environment, for example Docker on a home server or VPS. Without that foundation, the setup effort increases considerably. Those who want to pull their data out of Komoot or Strava and manage it themselves long-term will find a direct migration path here. The API also makes the tool interesting for developers who want to build custom dashboards or automations around tour data.
Context & alternatives
Wanderer belongs to the category of self-hosted geodata tools. Comparable approaches exist with Nextcloud combined with mapping apps, or specialised self-hosted solutions such as OpenTracks for Android, though none of these offer a web application with social features. The combination of a trail database, route planning and ActivityPub networking is not found in other open-source projects in this category. The project is young and the number of active instances is small accordingly. Users who depend on a broad network for discovering other people's routes will find little there at present. Those primarily looking for a decentralised replacement for Komoot or Strava, and who already have the technical foundation in place, can get productive immediately.
