14 questions people actually ask

No. If you can describe your business in a message, you can run your website here. Your AI does the technical work; the platform makes sure it can't do anything irreversible without your say-so.

Any assistant that supports MCP connectors. Claude on the web and Claude Desktop are the ones we've verified ourselves, and MCP is an open standard, so the list keeps growing. If you don't have an assistant yet, say so on the access form and we'll help you get set up.

Yes. Point it at us or transfer it in — either way it stays registered to you. The platform tells your AI exactly which DNS record needs changing, checks when it resolves, and issues the HTTPS certificate itself.

There's a console at portal.thedesignerscode.cloud — you sign in with an emailed link, so there's no password to forget. It shows your visitors, your releases and what each one changed, your enquiries, your orders and your domains. You never need it to change a page; it's for the days you'd rather point than type.

Ask your AI for an upload link. It sends a private page that works on any phone or laptop — drag your photos in and they land already resized, stripped of camera and location data, and converted to fast WebP. Even a 25 MB phone photo comes out as a quick-loading page asset, and the same photo uploaded twice is only stored once.

Yes — via YouTube or Vimeo. Upload the video there and your AI embeds it on your page. That's deliberate: video hosting is a specialised business, and embedding keeps your site fast and your bill sane.

Yes, and it's a setting rather than a redesign. Your colours, fonts and corner style are stored as brand tokens; every page and every new section obeys them from then on. Change one token and the whole site follows on the next publish.

On the Store plan, yes. Your AI manages a product catalog and puts a PayFast checkout on your own domain. The amount charged always comes from the catalog rather than the page, so a stale page can never mischarge anybody, and sandbox mode lets you run the whole flow before real money is involved.

No, and we don't sell them. You bring the assistant you already pay for; we charge for the domain, the hosting, the build pipeline and the connection. Nothing here runs out halfway through a job.

Four nets, in order. Drafts: nothing a visitor sees changes until you approve a preview. Undo: a draft can be walked back 25 steps before it is ever published. A pre-publish check: broken links, missing image descriptions and wonky heading order get caught before the page is public. And releases: every publish is kept, so "put it back how it was on Friday" takes seconds, with no rebuild.

They're validated, spam-screened and stored with your site, and you get an email the moment one lands. In your console you can mark each one read, spam or archived and reply to the customer with your own address on the reply — or just ask your AI “anything new this week?” and it reads them back, or exports the lot as a spreadsheet.

No. Your sign-in scopes your assistant to your sites and your plan's features — other customers aren't hidden from it, they're invisible to it. Payment credentials are held server-side and never appear in a page, a draft or a chat.

Your site is honest HTML, CSS and images on your own domain — there's no proprietary format holding it hostage. Ask for an export and you get the whole live site as a zip of plain HTML, CSS, JavaScript and images that runs on any static host, plus your domain, which was always registered to you. It's a button, not a favour.

Less than you'd think, and that's on purpose. Your published site is plain files served over HTTPS — there's no plugin to update, no database to corrupt and no code running when a visitor arrives. If we vanished tomorrow, your last export would still work.