TripHub

Group travel coordination

Plan the trip together.
Then actually pull it off.

TripHub keeps one source of truth for a group of 2 to 15 travellers — everyone’s flights, every hotel, every activity and its plan B — on a shared calendar that never makes anyone do timezone arithmetic in their head.

Sign in See what it does

Installs to a phone like an app. Works offline. Built for the day itself, not just the planning.

What it does

Built around the trip, not around the software

The planning months before, and the messy hours of the travel day — the part most planners stop caring about.

  • One itinerary, not six group chats

    Flights, lodging and activities live in one place. Travellers add their own details; organisers can fill things in on anyone’s behalf when they booked the whole group, and the traveller can correct it later.

  • Fallback plans are first-class

    Every activity can carry an ordered Plan B, C and D. When the restaurant is shut or the weather turns, promoting the fallback is one click — it swaps into the itinerary and everyone attending is told.

  • A calendar that shows both clocks

    Every time is rendered in destination time and in your own home time at once — flights in airport-local time. Month, week, day and agenda views, with conflict warnings when someone is double-booked or an activity starts before they land.

  • Suggestions the group votes on

    Anyone can propose an activity with a few candidate days. Everyone rates interest 1 to 5 per day, results are visible, and the winning day is promoted onto the itinerary with interested members already added.

  • Shared map and deliberate check-ins

    Lodging, activities and member check-ins on one map. Check-ins are a button someone presses — there is no background tracking and no polling, ever. Export pins as an image, GeoJSON, KML or a printable day-by-day map.

  • Reminders that reach people

    Shared or personal reminders set in destination or home time, delivered by web push with email fallback. Templates for the usual ones — “two hours before the flight”, “the night before check-out”.

  • A safety tab that works with no signal

    Local emergency numbers, consulates, nearby hospitals, rally points and lodging addresses in both native script and romanised form — cached offline, and exportable as plain text to paste into any messaging app.

  • An optional Claude assistant

    A trip organiser can link their own Anthropic API key. Other members get permission-gated, prebuilt actions — “this place is closed, find three similar ones open now” — with per-member quotas, a spend ceiling and a full audit log. The key never reaches anyone’s browser.

The hard part

The timezone thing, solved properly

Group trips fall apart on time. Someone reads a departure in the wrong zone, someone schedules a call during a flight, someone at home has no idea when to expect a message.

TripHub stores every instant in UTC alongside the zone it is anchored to, and renders it twice: destination time as the headline, your home time underneath. Before the trip your home time leads; on the start date the two swap automatically. Flights are shown in airport-local time, because that is what the boarding pass says.

Calendar subscriptions export with correct TZID handling, so the events are still right once they land in Outlook or Google Calendar.

Scope, on purpose

What it deliberately is not

Three things TripHub will not do, because leaving them out is the design.

  • Not a booking engine

    Nothing is booked or paid for here. TripHub records what you booked elsewhere and keeps the confirmation codes where the group can find them.

  • Not a live tracker

    No GPS in the background, no geofencing, no “last seen”. A check-in happens because a person chose to post one.

  • Not a social network

    No global feed and no follower graph. Discussion is attached to the decision it is about, on the activity it concerns.

Privacy

Private by default

Think about what a trip planner ends up holding: passport-adjacent paperwork, confirmation codes, emergency contacts, dietary and accessibility notes. That is not ordinary app data, and it is not treated as ordinary app data here.

Documents are encrypted at rest, private by default, and shared per file rather than per trip — so handing someone your flight details does not hand them your passport scan. Permissions are enforced on the server, never just hidden in the interface. Even an administrator does not get to read a member’s private documents.

Third-party services are opt-in and scoped: live flight status and the assistant run on keys the trip organiser supplies, and the map runs on open tiles with no billing account attached. Nothing is sold, and there are no trackers on this page.

Under the hood

  • Frontend React + TypeScript, installable PWA
  • Backend Node + Fastify, PostgreSQL, Redis
  • Maps MapLibre GL on open tiles
  • Documents Encrypted at rest, shared per file
  • Offline Itinerary and safety tab cached
  • Access Per-trip roles, enforced server-side

Already have an account?

Everything above happens in the app. This page is just the front door.

Sign in to TripHub