Sites and hosting
Hand a site to your client
What each client site depends on, what you can offer a client who wants more of it in their own name, and what keeps running if you stop using Klaudius.
Every client site Klaudius builds lives on your accounts: your hosting, your database and, for the receptionist, your voice-platform account. That's what lets you charge for hosting and care, and it's what the standard offer assumes. This page helps you answer a client who wants to own more of it.
What each part runs on
| Part | Runs on | Good to know |
|---|---|---|
| The website | Your hosting account | Without add-ons, it's plain files that any host can serve |
| The domain | The registrar account that registered it | It needs renewing every year |
| The editor (CMS) | Your Vercel account, which stores the content, photos and sign-ins | Vercel only |
| The booking system | Your Vercel account and your database; a converted client's booking emails also go through your Resend account | Customers' details are held in your database |
| The live Google rating | Your Vercel account and your Google key | Without the key, the site shows the rating it had at launch |
| The AI receptionist | A number and an assistant on your voice-platform account | An empty balance can cost you the number |
What you can offer
Their own logins. A client with the editor or the booking system gets their own account, with roles for anyone who helps them: control of their content and bookings, with no access to your hosting.
The domain in their name. A client can register the domain in their own account and add the records you send; the attach steps are the same. Domains covers registering it for them and renewals.
The site on their own hosting. Klaudius has no built-in step for this. A site without add-ons is plain files, so you can ask Klaudius to help you move one. A site with the editor, booking or the live rating depends on your Vercel account (and, for booking, your database), so moving it is a bespoke job: ask Klaudius what it would involve before you agree.
Their booking data. If a booking client leaves, ask Klaudius to export their bookings and then delete them from your database.
The receptionist. The client's own number never changes. To end the service, they dial the forwarding codes off first, then Klaudius releases the receptionist's number so its rental stops.
Never give a client access to your hosting account, or to a booking site's project in it. That project holds the key to your database, which also holds every other client's bookings and your whole pipeline. The logins Klaudius gives the client are all the access they need.
If you stop using Klaudius
When a subscription ends, Klaudius stops starting new runs. Everything you've built stays yours: the websites on your hosting, your client list and database, and your outreach accounts.
Client sites and add-ons run on your own accounts, so they keep working while those accounts stay open and paid: your host, your database, your Google key for live ratings, and a voice-platform balance above zero for receptionists. Monthly fees in your Stripe account keep charging, because Stripe runs them.
What stops is Klaudius's own work: finding and building new sites, follow-ups, recording payments in your ledger, the receptionist check, and any change you'd ask it to make to a site.
Ask Klaudius
- What does Acme Bakery's site depend on if I hand it over?
- Help me move Acme Bakery's site to the client's own hosting account
- Export Acme Bistro's bookings and remove them from my database