One system for your whole operation
One place where a departure lives — the trip, the itinerary, the rooms, the seats, the money and the people who booked it. On your domain, under your brand, with no commission taken.

Checkout that never leaves your site
An embedded checkout you control, so you can put an upgrade or an add-on in front of a guest without taking the choice away from them. Everyone in a group pays their own share, on their own card, and cancels without dragging the rest of the booking with them.


who live there.Wildlife journeys across India, Patagonia and East AfricaExplore trips



A booking site your team can actually edit
We migrate the site you already have, keep your URLs and your ranking, then hand you a WYSIWYG editor that writes straight to the platform. Guests check out on your own domain, and never see ours.

Transfer, evening briefing, first night at the lodge
Pre-dawn start, Ken river circuit, afternoon at leisure
Two drives, packed lunch, evening talk with the naturalist
Draft the itinerary, then edit it like a human wrote it
Describe the trip and Kap AI lays out the days for you to correct. It also works the task list behind a published departure, clearing what is waiting on an approval rather than on a decision.
Thetrip,therooms,thebookings,themoneyandthepeople—setuponce,andinagreementwitheachotherfromthenon
By plan
Trip management
Trips, departures and visual day-by-day itineraries, with pre- and post-trip add-ons, extensions and a waitlist.
Booking lifecycle
Every stage from enquiry to departure, with the operator and guest notifications firing automatically at each one.
Rules and policies
Deposits, due dates, reminder triggers and cancellation terms, set once and overridden per trip or per departure.
Payments
Bring your own Stripe on Boutique and up; Plaid and more on Enterprise. Group members pay their own share.
Guest CRM
One profile per traveller: documents, preferences, booking history and every message, in one place for the whole team.
Reporting and exports
Bookings by trip and date, revenue by payment method, occupancy against capacity — out to CSV or Excel whenever you want.
Room inventory
A room library, rooming assigned on the departure itself, and the private-room upgrade priced where it belongs.
Advanced CMS
Anyone on your team edits the booking site from a WYSIWYG interface that syncs to the platform in real time.
Custom checkout
An embedded checkout you control, so you can put incentives in front of guests without taking away the choice.
Agency and manual bookings
Staff and agency users book on a guest's behalf, take offline payment, and have invoices generated for accounting.
Loyalty and cancellation credits
Decide how credits are issued and redeemed, and how loyalty is earned and spent. Combines with discounts.
Kap AI
Itinerary generation, a task manager for the operations team, a unified guest inbox, and Instagram comments turned into enquiries.
How you can save time and get started now
Kapuli is in closed beta, so there is no sign-up button. There is a conversation, then a migration, then your first departure.
01 · Talk to us
Thirty minutes on how you actually run departures. No demo script, and no obligation on either side.
02 · We move your site across
Within four weeks of signing. Your content, your URLs and your search ranking come across intact — then it is yours to edit.
03 · Publish your first departure
Trip, itinerary, rooms, seats and dates in one flow. Your engineer stays on the account after that.
Questions operators ask first
The full list, all forty-three of them, lives on the FAQ page.
Yes. Capacity, price, deposit amounts, due dates and cancellation terms are set per trip, and you can override them on a single departure.
Kapuli reads your policy and works out the refund or the credit due. You approve it, and the guest gets the email automatically.
Yes. Staff can create a booking on a guest's behalf, take an offline payment and record it against the same departure.
We move it across for you and keep your content, your URLs and your search ranking intact. After that you get a self-service editor, so changing words and photos never needs a developer again.
No. The booking experience runs on your own domain, under your own brand. There is no Kapuli branding anywhere your customers can see.

Streamline your tour operations today
We will look at how you run departures and tell you whether Kapuli fits.