Choose your integration
| Hosted site | Links & embed | Your own UI | |
|---|---|---|---|
| Effort | None — the studio fills a form | Minutes | Hours |
| Who writes code | Nobody | Copy-paste | You |
| Look and feel | Mr Charles templates + the studio’s colours and logo | Your page, our booking screen | 100% yours |
| Custom domain | Yes (studiouno.com) | Keeps your domain | Keeps your domain |
| Payments, SMS codes, legal pages, reminders | Included | Included | Included (you call the API) |
| Updates when we ship features | Automatic | Automatic | You adopt them |
| Best for | A studio with no website, or a bad one | A studio with a website it likes | Agencies, directories, platforms |
Hosted site
Section titled “Hosted site”The studio gets a complete website on slug.sites.mrcharles.app, or on its own domain with two DNS records. Rooms, photos, prices, hours, map, legal pages, and bookings 24/7 — all driven by what the studio already maintains in its dashboard.
Links & embed
Section titled “Links & embed”Keep the website you have. Add a Book button that deep-links into the hosted booking screen for a specific room, or drop that screen into your page with an <iframe>. Payments, codes and emails keep working; you write no JavaScript.
Your own booking UI
Section titled “Your own booking UI”Call the public API from your frontend and render everything yourself: a calendar, a slot grid, your own fonts and copy. The API still owns prices, policy, conflicts, codes and payments, so you cannot create an invalid booking by accident.
Mixing them
Section titled “Mixing them”They are not exclusive. Common combinations:
- Own homepage + embedded booking. Your design everywhere, our booking screen in a modal.
- Hosted site + API read. The studio’s site is hosted; your directory reads
/public/sites/{slug}to show live prices and a “next free slot” badge, then links out. - Own UI + hosted manage page. Build the booking flow, then hand the guest the
manageUrlwe return, so you never implement cancellations.