# Self-hostable collaborative travel planner - Wander — retained record

> Retained reddit record from reddit:selfhosted.

Canonical: https://highsignal.app/data/records/e1edf2183b7efc20

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:selfhosted)  published 2026-09-28 12:12 ingested 2026-09-29 02:40

[original source ↗](https://www.reddit.com/r/selfhosted/comments/1wscwvo/selfhostable_collaborative_travel_planner_wander/)

## retained text



```
I’ve been building **Wander**, an open-source, self-hostable travel planner for collaborative trip planning.

# Repository:

[https://github.com/vahdamv0/wander](https://github.com/vahdamv0/wander)

# Try yourself

[https://meridianx.co.in/](https://meridianx.co.in/)

# Deployment

Wander can be self-hosted using Docker.

The repository contains the required configuration and setup instructions: [https://github.com/vahdamv0/wander](https://github.com/vahdamv0/wander)

The application runs as one container with PostgreSQL.

# What is Wander?

Wander lets multiple people plan and manage the same trip.

The itinerary is built by arranging places in the order you want to visit them. Days are derived from the itinerary, with a map, daily costs, and forecast information alongside it.

It currently includes:

* Collaborative itineraries
* Live synchronization
* Sharing with roles
* Invitation links
* Expenses
* Packing lists
* Bookings
* Offline reading
* Verified backups

# Tech stack

**Spring Boot 4 + Angular 22 + PostgreSQL**

The application is designed to run with **one container and one PostgreSQL database**.

# One interesting design decision

Wander supports **offline reading**, but I deliberately didn't implement an offline write queue.

Offline writes would introduce another conflict-resolution problem when changes reconnect with the live-sync system.

The live-sync design was intentionally built so that this additional complexity wasn't necessary.

I'm interested in whether this is a reasonable trade-off or whether offline writes are important enough to justify the additional complexity.

# Open data

When you open a place, Wander combines information from:

* OpenStreetMap
* Wikidata
* Wikipedia
* Wikimedia Commons

I also wanted image attribution to be handled properly. Each Commons photograph retains its photographer and licence information rather than treating the image as simply "free to use."

# Feedback

I'm particularly interested in feedback from other open-source developers:

* Is the architecture approachable for contributors?
* Is the self-hosting model useful?
* Is the live-sync/offline trade-off reasonable?
* What would make you interested in contributing?
* What would prevent you from self-hosting it?
```



document fetched 2026-09-29 00:30 · canonical https://reddit.com/r/selfhosted/comments/1wscwvo/selfhostable_collaborative_travel_planner_wander
