Try the booking widget right here.
Below is a working demo tenant — Noosa Hoverboards,
a fictional flyboarding operator running on the platform. It’s the
same backend as
demo.bookingapp.com.au,
just embedded here with the simple
<script src=".../embed.js"> one-liner.
Stripe is in test mode, so nothing is charged.
The widget above loads in an iframe from
https://dapp.bookingapp.com.au/embed. The Astro page you
are on right now does not fetch anything cross-origin — it just
sits the iframe in the DOM and listens for
postMessage events. That’s the whole integration.
What you just touched
Every part of that widget is a feature documented elsewhere on this site. In rough order of appearance:
- The catalog screen — grid of 4 seeded Noosa Hoverboards products. See the full booking flow →
- The calendar and time picker — day-view availability powered by real sessions in the demo Postgres database. Zero Dead Ends →
- Options & add-ons — pick a pricing tier and optional skipper for the hoverboard + jetski combo. How add-ons work in admin →
- Checkout — the widget redirects to Stripe Checkout (test mode) for the actual payment, because Stripe Checkout blocks iframing. Why the parent page takes over at checkout →
- Success page — the “Back to website”
button points at
demo.bookingapp.com.au, the canonical marketing face of the demo tenant.
Same backend, two surfaces
The demo tenant’s own marketing site at demo.bookingapp.com.au embeds the richer version of the widget — the one that lives inside the marketing clone and fetches product data directly, the same pattern real customer tenants use on their own domains.
This page you’re on is the simpler integration: one script tag, full iframe isolation, no cross-origin fetches from the host page at all. That’s the integration a WordPress or Shopify site would use.
Want your own tenant?
If you liked what you just tried, get in touch and we’ll spin up a real one in your own brand.
Get in touch