Straight answers.

No. You need to be able to describe what you want, and to look at a page and say whether it's right. The AI writes the code; you never open a file. Plenty of our customers have never seen HTML and never will.

Any assistant that supports MCP — Claude, ChatGPT, Cursor and several others. A standard consumer subscription is enough to build and run a site. If you don't have one, we'll help you choose and set it up during onboarding.

The domain, server and connection are usually live the same day. Getting the site to where you're happy with it depends on you and how much content you have — a simple business site is an afternoon, and unlike a traditional build there's no waiting on a designer between rounds.

Yes, and you don't have to transfer it. Either add two DNS records where your domain is currently managed, or point the nameservers at us once and we handle every record from then on. We'll tell you which of those is less work in your specific case.

It can't, in the way you're imagining. Everything it does happens in a draft that no visitor can see, and the live site keeps serving the last version you approved. Nothing changes in public until you say publish.

If something does go out that you don't like, rollback puts the previous version back in under a second — no restore from backup, no waiting, no support ticket.

This is the realistic failure, and we designed specifically against it. Publishing compares the new version against what's live, and refuses if it would remove a script, form or embed you didn't ask to remove — naming exactly what would disappear. Anything critical, like a tracking tag or booking widget, can also be pinned so any rewrite that loses it fails outright.

That's what happens when a model writes styling from scratch every time, so it doesn't. Your brand — colours, fonts, spacing, corner radius — is stored with the site and injected into every build, and pages are assembled from a library of designed sections rather than invented fresh. A colour that isn't on your palette blocks the publish.

It sees it. Every check renders the page in a real browser and returns an actual screenshot along with console errors, broken images and whether anything overflows on a phone. This matters more than it sounds — a page can pass every automated test and still look terrible, and a model working only from text has no way to know.

Once per publish, roughly. Draft edits, uploads and builds aren't flagged as risky because they aren't — they can't change anything a visitor sees. Builders that ask you to confirm every single action train you to click "always allow", which switches off the one confirmation that actually mattered.

You can display a catalogue, and you can embed a checkout from a service that does payments properly. What you can't do is run the store itself here — there's no database and no server-side code at request time, which is exactly the constraint that makes the platform fast and secure. If you need a real storefront, say so early and we'll point you at the right thing.

Not on the site itself. Same reason: nothing executes on the server. Member areas, portals and gated content need a platform built for it, and we'd rather say that now than sell you something that almost works.

Those work. Forms post to an endpoint we run, submissions are emailed to you, and spam is filtered. What we don't do is store your enquiries indefinitely in a system you can't see — the mail is the record.

We tell you, and help you move. If the site works and the business grows, you will eventually want bookings, logins or a real checkout. At that point the honest answer is a different platform, and you leave with plain HTML and your full history rather than starting from nothing. We'd rather be the thing that got you there than the thing you resent.

You do. The domain is registered in your name, the content is yours, and the generated code is yours with no licence attached to it.

One command hands you a zip: plain HTML, CSS, images and the complete git history, with nothing TDC-specific in it. Host it anywhere — a bucket, a static host, your own server. There's no export fee, no notice period on the data, and no proprietary format that only imports back into us.

A fair question to ask any small supplier. Your export is standard static files that any host on earth can serve, and your domain is in your name at a registrar you can log into. That's the point of building it this way: the exit doesn't depend on us being around to help.

No. We don't run the model — your AI subscription does, under whatever terms you agreed with that provider. On our side your files are your files.

It's in early access, and we're onboarding a limited number of sites while we do it properly. That means real sites on real domains, with us close enough to fix things quickly. If you'd rather wait for general availability, tell us and we'll let you know when it lands.

Yes. Each person connects their own AI with their own scoped token, and every change is recorded against whoever made it. You can also issue a token that can edit but not publish.

Then we will. Fully managed is a normal way to buy this — you email us what you want changed and it happens, on the same platform with the same safety net. You can switch to driving it yourself later without rebuilding anything.

Ask us during onboarding and we'll tell you exactly, including where backups live. If you have a data residency requirement, raise it early — it's answerable, but not after the fact.