Can’t I just use a basic Cloudbeds embed?
You can. The basic embeds help a guest start a booking, then they continue on Cloudbeds’ hosted page.1 Several of the paid date pickers do the same once the dates are picked.1 Only the full Immersive Experience 2.0 keeps the whole booking on your site, and it is the paid premium embed.1,3 We build the pages instead, so the design and the steps are yours.
What does the premium embed cost?
Cloudbeds’ terms (updated as of March 26, 2026) say: “A 1% commission applies to the total value of reservations where the Embed Suite is identified as the originating booking source.” The same terms call 1% the rate for early customers, and say Cloudbeds may change or end the Embed Suite or its terms at any time.3 Cloudbeds’ pricing page separately says direct bookings made through its own online tool are commission free.7
Would that commission apply to a site built on the API?
We do not know yet. The terms charge the 1% when the Embed Suite is the booking source, and they do not mention reservations created through the API.3 We ask Cloudbeds to confirm it for your account, and tell you before you decide.
Does my Cloudbeds keep running the back?
Yes. Your account, rates, availability and reservations stay in Cloudbeds. We build the website guests see and use.
Will the guest pay on my pages?
We do not promise a fully native payment step. Cloudbeds’ booking API says that transferring cards or processing payments is not supported.4 Its payment guides describe two routes: your own payment page and gateway, recorded in Cloudbeds afterwards, which Cloudbeds calls a limited payment integration;5 and an embeddable card form, if the property has a payment gateway integrated with Cloudbeds.6 We check which one fits your account on the call.
Can I add my own payment gateway to the Cloudbeds embed?
Cloudbeds says it does not recommend using unsupported payment gateways in the Immersive Experience, and that custom payment methods should only be used on hosted environments at this time. It says official support for such gateways is scheduled for release in 2026.2 If your property needs a gateway the embed does not support, we look at a site built on the API instead, and check which payment route fits your account.5,6
My site still uses the old iframe embed. Is that a problem?
Cloudbeds says it retired the old iframe version and completed the switch in Q1 2026. Its reasons include clickjacking and data exposure risks, search engines indexing iframes poorly, and passing analytics data to an iframe “required complex workarounds.”8 We look at what your site uses on the call.
What do I pay, and when does the clock start?
In three payments: a part up front, a part at launch, and a last part 90 days after launch, due only if your website booked more than in the same 90 days last year. We go through the numbers on the call. Cloudbeds has to switch on API access for your property first. Cloudbeds says access is either included in your package or on request for an additional cost.9 That step is in Cloudbeds’ hands, and the thirty business days count from the day it is switched on.
Can I see my homepage first?
Yes. A free homepage preview comes first, and we show it to you on a call. You decide after.
Is there a page for my kind of property?
Yes. Read more about websites for retreats and websites for colivings. Comparing systems? See our pages for Mews and Checkfront.