Our Story

A trip plan should not live in ten tabs.

Jonetsu started with a familiar problem: a trip spread across browser tabs, group chats, screenshots, and one tired organizer.

JonetsuOne trip, one plan, and everyone on it.

The problem

The plan was in five places, and none of them were current.

Ideas lived in browser tabs. Decisions disappeared into chat. Bookings sat in inboxes. Expenses moved to another app. When anything changed, the group had to reconstruct the plan from memory.

Jonetsu puts those pieces in the trip itself: the days, the ideas, the bookings, the costs, and the people. When someone changes the plan, everyone sees the new version.

What guides us

Three rules we build by.

01

The trip belongs to the travellers

Jonetsu suggests and drafts. It never changes a trip until someone on it approves the change.

02

Keep decisions next to the plan

Votes, comments, bookings, and costs sit in the trip they belong to, not in a chat thread.

03

Useful on the road, not just before it

A booking file, a phrase, or the balance of who owes whom matters most once you have left home.

See it in practice

Start a trip and see for yourself.

Open the web app and start a trip, or read How it works first.