TRIP is a free, open-source self-hosted app for mapping points of interest and planning multi-day trips. See features, setup, and alternatives.
TRIP is an open-source, self-hosted web application designed to help travelers visualize points of interest on an interactive map and organize those points into structured, multi-day trip itineraries. Built and maintained by an independent developer under the GitHub handle itskovacs, the project is distributed under the permissive MIT license, meaning anyone can run, modify, or redistribute it free of charge.
Unlike commercial travel-planning apps that monetize through subscriptions or advertising, TRIP is explicitly positioned around privacy and data ownership: the project states it includes no telemetry, no tracking, and no ads. Users deploy it themselves, typically via a single Docker command or Docker Compose file, and all trip and POI data lives on infrastructure the user controls.
The project has matured through dozens of releases and hundreds of commits, and has built a modest but engaged following in the self-hosted software community, reflected in its GitHub star count and active discussions and issue tracker.
At its core, TRIP lets users drop pins for points of interest directly onto an interactive map, tagging and categorizing them so a growing personal database of places to visit, or places already visited, stays organized over time. These POIs can then be pulled into structured, multi-day trip itineraries that lay out where a traveler plans to be on each day of a journey.
Collaboration is built in: trip plans can be shared with travel companions so groups can coordinate an itinerary together rather than passing spreadsheets or screenshots back and forth. Because the whole application is self-hosted, teams or families can run a private instance accessible only to the people they invite.
Operationally, TRIP is designed to be lightweight and easy to deploy, shipping as a Docker image with persistent storage mounted as a volume. This keeps infrastructure requirements minimal, making it approachable for hobbyists running a home server as well as more advanced self-hosters managing a small fleet of Docker services.
TRIP has no paid tiers. It is entirely free and open source, and the full feature set is available to anyone who self-hosts it; there is no gated premium version or subscription. The only monetization path is voluntary sponsorship of the maintainer through Ko-fi, which does not unlock any additional functionality.
Because there is no managed cloud offering, the real cost of running TRIP is the infrastructure a user provides, such as a small VPS or home server capable of running Docker, rather than any fee paid to the project itself.
TRIP is used to pin points of interest on a map and organize them into multi-day trip itineraries, making it easier to plan and share travel routes.
Yes. TRIP is completely free and open source under the MIT license, with no paid tiers or feature gating.
Yes, TRIP has no official managed cloud version; it is deployed via Docker or Docker Compose on infrastructure you control.
TRIP is created and maintained by an independent developer known as itskovacs, distributed publicly on GitHub.
No. The project explicitly states it includes no telemetry, no tracking, and no advertisements.
Yes, a public demo is available at itskovacs-trip.netlify.app.
Yes, trip plans can be shared with travel companions for collaborative itinerary planning.
TRIP is built with a TypeScript frontend and Python backend, and is distributed as a Docker container image.