Effortless.
Transparent.
See the code. See the fees. See the difference.
4.5%. That's the
whole model.
Every booking costs you exactly two things: Stripe's payment processing fee, passed through at cost, and our 4.5% commission. There is no third line. No commission tiers to climb, no visibility programs, no fees invented on the guest's side of the receipt.
Why so low? Because 4.5% is what it actually costs to run this; servers, support, infrastructure, development. No padding for a growth budget. Bigger commissions often fund bids on your own hotel's name in search engines, so you'd be renting back a guest who was already looking for you. We skip that entirely.
Why believe it? Because you don't have to take our word for the fees — the booking engine and fee logic are public code on GitHub. And ranking can't be bought: no host, however large, pays for placement.
Stripe fee shown for standard EEA cards. We add no markup to payment processing.
What would
you keep?
Three numbers about your property. Change any of them and watch the year's commissions recalculate — ours next to the platforms you'd be leaving.
That's €172,800 in booking revenue per year, across 480 bookings.
more than with Booking.com, every year — about 129 nights of revenue at your own rate.
Competitor figures are typical published commission rates and vary by market and agreement. OpenBookings cost includes Stripe processing (1.5% + €0.25 per booking, standard EEA cards), passed through with no markup.
A number you can
plan around.
Our commission is set at 4.5%. Any change requires 30 days' notice, is published here before it takes effect, and never applies to bookings already made.
Update deps, TS configs, Docker & CI tweaks
0e59807·Wouter van der Wal·4m ago
Use bun --cwd in app Dockerfiles
d7e7c94·Wouter van der Wal·1h ago
Add @types/geojson to web devDependencies
24d2b58·Wouter van der Wal·1h ago
You don't have to trust the pledge — you can watch it being kept.
Two kinds of data flow through a booking — and they deliberately never travel together.
Reservations, guest names, messages, preferences. OpenBookings stores lives in EU-certified data centres and never leaves the European Economic Area. GDPR compliance is by design, not a policy document.
Card details go directly from your guest to Stripe — PCI-DSS Level 1, the highest certification in payments — and settle straight to your account. Our servers never see a card number, so there's nothing to breach.
A note from
the founder.
Every year, independent hotels hand over a share of their revenue to booking platforms, then pay again to rank above their own name in search results. I watched this happen from your side of the desk, and kept waiting for someone to build the obvious alternative. Nobody did. So I started building it.
OpenBookings is built and run by one person today, that's a current stage, not a promise. What isn't dependent on any one person is the commission itself: it's written into the code, publicly versioned, and changeable only with 30 days' notice.
You're not trusting a founder. You're trusting a business model you can read.
The rate exists to keep the lights on, not to fund growth at your expense.
Ranking is determined by relevance to the guest. It is not, and will never be, for sale.
EU data residency by design. Payments route directly to Stripe.
Answers to the
questions that matter.
Is the 4.5% on top of Stripe's fees?+
How can it be so much cheaper than Booking.com or Expedia?+
What stops you from raising the rate later?+
Do payouts go through OpenBookings?+
What exactly is open source?+
Where is guest data stored?+
Am I locked in?+
Keep your margin.
List your property in minutes, or talk to us first. Either way, the rate is 4.5% — same as it says on the tin.