Taking over your website

Your website, , is moving out of ’s accounts and into accounts that belong to you, . When this is done you own all of it: the website, its address, the blueprints, the money and the email. keeps a key to come in and make changes when you ask, and you can take that key back at any time.

Your part is small: create a few free accounts and hand a handful of codes. This guide walks you through it one station at a time, with a button for every page you need to open and a check for every code, so you know it is right before you send it. Nothing here can break anything. You can stop and come back; this guide remembers where you were, on this computer, in this browser.

Have ready: the business email () and its password; your phone, for the confirmation codes; and, for Stripe only, the business’s bank details and tax number. Budget about an hour.

Start with Cloudflare

The stations

Click a count to see each step inside it. Green means done.

Who owns what, when this is done

ThingPlain wordsWhere it livesCosts
The websiteThe pages people see, the booking form, your dashboard, and the database behind themCloudflare, your accountFree at your size
The address, which is what people typeToday at ; later at CloudflareAbout $10 a year
The blueprintsThe code the website is built fromGitHub, your accountFree
The emails it sendsBooking confirmations, your alerts, receiptsResend, your accountFree up to 3,000 a month
The moneyCard payments, straight to your bankStripe, your accountAbout 3% of each payment, nothing monthly
What does actually do with the codes?

His tool copies the website and its database out of his account and recreates them in yours: the same pages, the same bookings, the same photos. The codes are what let the tool into your accounts to do that. He never sees your passwords; the codes are separate keys that open only the doors you tick, and each one can be cancelled from the account it came from.

At the end you will have the dashboard address and PIN, the login email for each account, and a one-page note of where everything is. Updates afterwards work the same way they do now: you ask, he changes the code, and the tool puts the new version in your account.

Is it safe to type codes into this page?

The codes you type stay in this browser, on this computer, until you send them. The checks talk to the company that issued the code (GitHub directly; Cloudflare and Resend through this guide’s own small helper, which keeps nothing). When you send, the last station scrambles everything with a lock that only ’s computer can open, so the message can travel by text or email. When he has it, the last station also has a button that makes this browser forget everything.