wanderer

Open-source outdoor trail management, honestly reviewed. No marketing copy, just what you get when you self-host it.

TL;DR

• What it is: A self-hosted, federated trail database — upload your GPS tracks, build a searchable catalogue, plan new routes, and share with others, all on your own server [1][2].
• Who it’s for: Hikers, cyclists, and outdoor enthusiasts who are tired of paying AllTrails or Strava subscription fees to access their own activity data, or who want control over where their GPS history lives [2].
• Cost savings: AllTrails Premium runs $35.99/year; Strava runs $79.99/year. wanderer is free software. A $6/mo VPS covers the server, and the software itself costs nothing [1].
• Key strength: The ActivityPub federation layer — your wanderer instance can follow users on other instances, similar to how Mastodon works. This is genuinely unusual for a niche outdoor tool [2].
• Key weakness: With 3,434 GitHub stars and no commercial backing, this is a passion project maintained by a single primary author. No SLA, no support contract, no roadmap guarantees [1]. Independent third-party reviews are essentially nonexistent — the community is small and mostly silent outside GitHub and Discord.

---

What is wanderer

wanderer is a self-hosted GPS track manager and trail catalogue. The core use case is simple: you record a hike or bike ride on your GPS device or phone, export the GPX file, upload it to your wanderer instance, add some metadata (distance, elevation, difficulty, photos, description), and it becomes part of a searchable, filterable personal trail database [1][2].

That’s the baseline. What makes it more interesting than just “Garmin Connect but self-hosted” is two layers of functionality built on top:

Federation via ActivityPub. wanderer is built on the same protocol that powers Mastodon and the broader Fediverse. Your instance connects to other wanderer instances, letting you follow other users, see their trails, comment on routes, and get notified of new uploads — across completely separate servers [2]. This is a meaningful architectural choice: your data sits on your server, but you’re not isolated. The network effect doesn’t require trusting a central platform with your data.

Komoot and Strava import. If you’re already tracking on either platform, you can pull your existing history into wanderer directly without manual file exports [2]. This removes one of the biggest friction points for anyone considering a migration away from subscription-based activity platforms.

The project is maintained under the handle open-wanderer on GitHub (previously Flomp), accepts donations via Buy Me a Coffee and Liberapay, and explicitly describes itself as a passion project [1]. That framing matters — it sets appropriate expectations for support, stability, and feature velocity.

---

Why people choose it

No substantial independent reviews of wanderer exist as of this writing. The GitHub star count (3,434) and active Discord community suggest a real user base, but that base hasn’t produced the kind of public write-ups that tools like n8n or Nextcloud attract. This section is therefore built primarily from the project’s stated design choices and the implied reasons behind them, not from synthesized third-party analysis.

The pattern that shows up in the self-hosted community broadly: people move away from AllTrails and Strava when one of three things happens. First, the price goes up. Strava has raised its subscription prices multiple times; AllTrails Premium is now nearly $36/year for features that used to be free. Second, data portability becomes a concern — both platforms make export cumbersome, and neither gives you a path to leave that preserves your social graph or comments. Third, the GPS data itself starts to feel sensitive. Long-term workout history, home address inference from run routes, recurring location patterns — this is data you might not want sitting on a VC-backed platform indefinitely.

wanderer addresses all three at once: no subscription, you own the data, and the ActivityPub federation means your social layer is also portable [1][2].

The Strava and Komoot import support is a deliberate “bring your history” feature that lowers the switching cost — you don’t have to choose between your new self-hosted setup and your existing seven years of logged rides [2].

---

Features

Based on the README and official documentation:

Core trail management:

• Upload GPX files (recorded tracks) or draw new routes from scratch [1]
• Metadata per trail: distance, elevation profile, difficulty, photos, description, tags [1]
• Advanced search and filter across your catalogue [1]
• Custom lists to group trails by trip, region, or any category you define [1]
• Charts and visualizations for trail data [profile]

Map integration:

• Extensive map integration described as a core feature, with route visualization [1]
• Support for planning new routes directly within the app [1][2]
• Access trail data from any device via the web UI [2]

Federation and social:

• ActivityPub protocol — your instance federates with other wanderer instances [2]
• Follow users on other instances, like and comment on trails [2]
• Cross-instance notifications when followed users add new content [2]
• Interoperability framing with other ActivityPub platforms (Mastodon mentioned as an example) [2]

Imports:

• Komoot: direct import of routes and activities [2]
• Strava: direct import of routes and activities [2]
• No manual file conversion required for either [2]

API:

• Full JSON API for programmatic access [2]
• “Automate your workflows or build on top of wanderer” — the API is documented but the surface area isn’t detailed in public-facing materials [2]

What’s missing or unclear:

• No mobile app is mentioned in any documentation. The web UI is responsive, but native iOS/Android apps don’t appear to exist.
• GPX export is not explicitly mentioned — you can import tracks, but the exit path for your data isn’t prominently documented.
• Multi-user access controls are not described in detail. wanderer describes itself as a community tool, but it’s unclear how permissions work for a shared family or club instance.

---

Pricing: SaaS vs self-hosted math

wanderer has no commercial tier. It is donation-supported open-source software [1]. There is no monthly fee, no per-track charge, no premium plan.

What you pay for:

• Server hosting: $5–15/mo depending on your VPS provider and region
• Domain name: ~$10–15/year (optional, but needed for HTTPS and federation)
• Your time to deploy and maintain

What the alternatives charge:

Platform	Free tier	Paid tier
AllTrails	Basic (limited features)	$35.99/year (Premium)
Strava	Basic (limited analysis)	$79.99/year or $11.99/mo
Komoot	Free base + region purchases	$3.99–$29.99 per region or $44.99/year Highlights
Garmin Connect	Free	Free (Garmin device required)

For a runner or hiker currently paying Strava $79.99/year and AllTrails $35.99/year — a not-uncommon combination — that’s $115.98/year for two subscriptions that still don’t give you full data portability. A wanderer instance on a $6/mo Hetzner VPS runs $72/year with unlimited trails and no recurring vendor relationship.

Over three years: two subscriptions ≈ $348. Self-hosted wanderer ≈ $216 in VPS costs (plus setup time). If you’re already running other self-hosted services on the same VPS — Nextcloud, Home Assistant, Miniflux — the marginal cost of adding wanderer approaches zero.

The AGPL-3.0 license means the software itself is free but carries copyleft requirements: if you run a public wanderer instance and modify the code, those modifications must be published under the same license [1]. For personal self-hosting this is irrelevant. For anyone building a commercial product on top of it, it’s a constraint worth reviewing with a lawyer.

---

Deployment reality check

The recommended install path is Docker Compose. The README’s quickstart is two commands: download the compose file, run docker compose up -d [1]. The first startup takes up to 90 seconds, then the frontend is available at localhost:3000 [1].

What you actually need:

• A Linux VPS (2GB RAM should be sufficient for personal use)
• Docker and docker-compose
• A domain name if you want federation to work properly and HTTPS for external access
• A reverse proxy (Caddy or nginx) for TLS termination
• SMTP setup if you want email notifications

The CORS gotcha: The README specifically flags that if you’re not hosting at http://localhost:3000, you must change the ORIGIN environment variable or you’ll hit CORS errors [1]. This is a common Docker networking trap for people deploying behind a reverse proxy — worth noting up front.

The security key: The README warns that MEILI_MASTER_KEY must be changed in production environments [1]. This is MeiliSearch, the search engine bundled with wanderer. The default key is public — in a production instance exposed to the internet, not changing this is a real security issue.

Bare-metal install is documented but the README points you to the website for details rather than including the steps inline [1]. This suggests it’s more involved than the Docker path.

Federation setup: ActivityPub federation requires your instance to be reachable over the public internet with a valid domain and HTTPS. A local-only install won’t federate, meaning you lose the social layer entirely if you don’t do the domain/proxy setup. This is the part where “15-minute Docker install” becomes “2-hour infrastructure setup” for someone who hasn’t done it before.

Realistic time estimates:

• Technical user with existing VPS and Docker: 30–60 minutes
• Non-technical user following a guide from scratch: 3–5 hours including domain, Caddy, and SMTP
• If federation with other instances matters to you: add another 30 minutes to verify ActivityPub discovery is working correctly

---

Pros and cons

Pros

• Actually free. No subscription, no freemium throttle, no features held hostage behind a paywall. The entire feature set is available to anyone who self-hosts [1].
• ActivityPub federation is genuinely rare. Building a niche outdoor app on the same protocol as Mastodon is an unusual technical choice that pays off: your social graph isn’t locked to your instance, and the network doesn’t depend on a single company staying solvent [2].
• Direct Komoot and Strava import. Removes the friction of GPX-file archaeology for anyone migrating from the major platforms [2].
• Full JSON API. You can build on top of it, automate uploads, or integrate with other tools [2].
• Privacy by architecture. Your GPS history — including home location inference, recurring patterns, health data — stays on your server. No third-party analytics, no ad targeting [2].
• Docker Compose install with a documented quickstart. Not the hardest self-hosted tool to get running [1].
• 3,434 GitHub stars for a niche outdoor utility suggests genuine user enthusiasm, not just GitHub Explore spam.

Cons

• Passion project, single primary author. No commercial backing, no SLA, no guaranteed support. If the author loses interest, the project stalls [1]. Donation-supported sustainability is fragile.
• No mobile app. The web UI is responsive, but there’s no native iOS or Android client for recording directly to your wanderer instance.
• AGPL-3.0 copyleft. Not an issue for personal use, but a constraint for commercial builds on top of the codebase [1].
• Federation requires public infrastructure. Local-only deploys lose the social layer entirely, which is one of the tool’s main differentiators.
• Security defaults require attention. The default MeiliSearch master key and CORS origin setting need to be changed for any internet-facing deployment — these aren’t post-install configuration options, they’re security requirements [1].
• No independent reviews. The near-zero public coverage makes it hard to assess real-world stability, edge cases, and long-term reliability. You’re largely betting on GitHub stars and the README.
• Unclear multi-user permission model. If you’re running a shared instance for a hiking club or family, the docs don’t clearly explain role-based access controls.

---

Who should use this / who shouldn’t

Use wanderer if:

• You’re paying for AllTrails Premium and/or Strava and would rather own your data than rent access to it.
• You want GPS track history in a searchable, self-hosted catalogue and you don’t need native mobile recording.
• The ActivityPub federation model appeals to you — you want a social layer that doesn’t require everyone to sign up on the same platform.
• You’re comfortable with Docker and basic Linux server administration, or you’ll pay someone to deploy it once.
• Your privacy concern about GPS data is genuine — home location inference from workout routes is a real pattern that commercial platforms can extract.

Skip it if:

• You need a native mobile app for recording directly to your trail database. wanderer doesn’t cover this workflow; you’d still need a separate recording app.
• You need guaranteed uptime and support. A donation-supported single-author project is not the right infrastructure for anything critical.
• Your team or club needs fine-grained access controls and you can’t evaluate whether wanderer’s multi-user model fits without more documentation.
• You’ve never managed a Linux server and no one in your orbit has either. The CORS/MeiliSearch security configuration issues can trip up a first-time self-hoster in ways that aren’t immediately obvious.

Stay on AllTrails/Strava if:

• The mobile recording experience is central to your workflow — both platforms have mature iOS and Android apps with offline maps.
• You rely on AllTrails’ curated trail reviews and verified route data rather than your own recorded tracks.
• You want Strava’s segment comparison and competitive social features. wanderer doesn’t replicate that.

---

Alternatives worth considering

• Garmin Connect — Free if you own a Garmin device. Solid activity history and maps, but fully closed, Garmin-exclusive, and your data lives on their servers.
• AllTrails — The largest trail discovery database. Strong for finding new routes in unfamiliar areas. $35.99/year, closed source, no self-hosting option.
• Strava — Best-in-class social fitness tracking and segment competition. $79.99/year, closed source, increasingly restrictive free tier.
• Komoot — Route planning and turn-by-turn navigation for cycling and hiking. Regional purchase model (~$3.99–$44.99/year). Good GPS maps, no self-hosting.
• OpenTracks — Android-only GPS recording app, open source (Apache 2.0), no server component. Records to local storage and GPX export. The recording side of what wanderer handles on the catalogue side.
• Nextcloud + Maps app — If you’re already self-hosting Nextcloud, the Maps app provides basic GPX track visualization without a separate service. Less featured than wanderer but zero additional infrastructure.

For the specific use case of “I want to own my outdoor activity history in a searchable format,” wanderer is the most purpose-built self-hosted option available. The main competition is either closed-source SaaS or cobbling together Nextcloud plugins.

---

Bottom line

wanderer is a technically coherent answer to a real problem: outdoor activity data is valuable, personal, and increasingly expensive to access on commercial platforms. The ActivityPub federation layer is a genuine differentiator — it’s unusual to see a niche tool built on decentralized infrastructure rather than just “self-hosted version of the SaaS.” The Komoot and Strava import support makes migration low-friction.

The caveats are real and worth naming plainly. This is a donation-supported passion project, not a backed company. There are no independent reviews to triangulate against. The security defaults require attention before any internet-facing deployment. And the absence of a native mobile app means wanderer covers the catalogue and social layer, but you still need a separate recording solution.

For a hiker or cyclist currently paying $80–$120/year across Strava and AllTrails subscriptions, a $6/mo VPS and an afternoon of setup is a reasonable trade. The tool is mature enough to be useful, the federation model is forward-thinking, and your GPS data stays where it belongs: on your server.

---

Sources

1. GitHub Repository — open-wanderer/wanderer (3,434 stars, AGPL-3.0). https://github.com/open-wanderer/wanderer
2. Official Website — wanderer.to. https://wanderer.to