CanTrip_

## why

## how it works

1. 2 views
   01 drop in your receipts Upload PDFs, screenshots or photos, or paste a confirmation email. Each one is read in the background and sorted into flights, stays, activities, food, transport, and rentals. Every detail says whether it came from the receipt or was a guess, and a booking that's seen twice is merged, not added again.
2. 2 views
   02 see the itinerary Bookings become a day-by-day list on the phone and a week calendar on desktop. Each day is drawn in its own local time, so a flight from Singapore lands at the Japan time it really lands.
3. 2 views
   03 sort what's missing CanTrip points out the gaps nobody booked for, like nights without a bed, a change of city with no ride, two places too far apart to walk. Tap a gap to see transit routes with the fare, a taxi time and a walk, timed to arrive before the next thing starts.
4. 2 views
   04 plan the rest Paste Google Maps links for places to eat or things to do. They come with opening hours, warn you when a place is closed on the day you picked, and can be dragged onto the calendar. Once one is reserved, its receipt turns it into a booking.

## stack

Go net/http + html/template// backend

The same setup as Expensieve and Jalan; the server renders every page as plain HTML, and the itinerary is worked out fresh on each load.

SQLite / Turso// database

SQLite for fast iteration in development; Turso, a hosted SQLite, in production.

OpenRouter// ai

Reads the receipts. A digital PDF's text is extracted on the server and scrubbed of emails, phone numbers and card digits before it's sent; only scans and photos go to the vision model.

Google Maps + HERE// maps

Google Maps for places, opening hours and routes. HERE fills in public transport where Google has none, like Japan.

Turbo + Stimulus// frontend

Pages swap in place and the calendar's pop-ups stay put, with no build step, and every page still works with JavaScript off.

Google Drive / S3// storage

Receipts go to a CanTrip folder in your own Google Drive, filed by trip and kind, or to an S3 bucket if you'd rather not connect it.

Fly.io// infra

Cheap, and friendly to both users and agents.

$ git log --oneline

1. HEAD → main2026-10-10

   Export the itinerary as a PDF or an Excel sheet

   The calendar or the day-by-day list, downloaded or saved straight into the trip's Google Drive folder.

2. 2026-10-10

   Placeholder flights for tickets not bought yet

   Add a flight by its number and day; check-in and the rides around it are worked out as if it were booked, and the real ticket replaces it once its receipt comes in.

3. 2026-10-09

   Plans on a day their place is closed are flagged

   Opening hours from Google Maps turn "closed on Wednesdays" into a gap to sort, warned of the moment the plan is put there.

4. 2026-10-08

   Pages swap in place with Turbo; the JavaScript is split into Stimulus controllers

5. 2026-10-06

   A ride can go through a stop you pick

   The quickest way isn't always the easiest, so a ride can be asked to pass the station with the express train.

6. 2026-10-04

   Rides between places, check-in times and layovers

   Gaps between bookings get transit routes from Google, or from HERE where Google has no timetables, and flights get a check-in and a ride to the airport.

7. 2026-10-03

   Plans from Google Maps links

   Things you don't book, with their opening hours, dragged onto a day on the calendar.

8. 2026-10-02 · initial commit

   Receipts in, day-by-day itinerary out

   The first MVP: receipts read into bookings, the travellers named on them, and a week calendar on desktop.