VibeBridgeWith Claude, Cursor or ChatGPT, building a client website takes days instead of weeks. The handoff has not caught up. If you want to hand off a website your client can edit, the usual options are bad. Send a zip and you stay the bottleneck forever: every typo, price change and photo swap comes back to you. Hand over the code and it is worse: now a nervous client is one stray keystroke away from a broken layout.
VibeBridge is the publishing and maintenance layer for AI-built websites, and it turns the client website handoff into four short steps. You publish the site, connect the client's domain, and invite the client to edit text and images in a visual editor that cannot break the layout. You keep MCP and API access for structural changes and new pages. Content requests stop landing in your inbox.
What you need
- The finished site as HTML files, from Claude, Cursor, ChatGPT or another AI tool
- A VibeBridge account (7-day free trial, no setup fee)
- The client's domain, or a line to whoever manages its DNS
- The client's email address for the invite
Step 1: Publish the finished site to VibeBridge
Sign up at app.vibebridge.ai/signup, then get the site in by one of two routes. The browser upload takes the exported folder as it is: drag HTML files and images in together, relative paths resolve automatically. Or connect the tool you built with over MCP: Claude Code, Cursor and Windsurf use an API key from the portal; Claude on the web and ChatGPT sign in with VibeBridge. The click-by-click path per tool is at app.vibebridge.ai/connect. Either way the site is live on a URL right away, hosted in the EU (Frankfurt) with automatic SSL.
The infrastructure around the site is already handled. Contact forms are detected and connected automatically; submissions land in a leads inbox and trigger an email notification. Analytics is built in, cookieless and first-party. There is no form service or tracking snippet to set up, and no hosting dashboard to explain to the client later.
Tip: If you build client sites regularly, set up the MCP connection once. Publishing the next site becomes a sentence in your tool instead of a file transfer.
Step 2: Connect the client's domain
Add the client's domain in the portal. VibeBridge shows the exact two DNS records to set at the registrar and provisions SSL automatically once they resolve. Propagation usually takes minutes, at most 24 hours.
If the client controls the registrar account, send them the two records as shown, or set them together in a short call. Do this before the invite, so the client first sees the site on their own domain.
Step 3: Hand off a website your client can edit
Invite the client to the site as a team member. They sign in and get the visual editor: click any text and retype it, click any image and swap it. There is a color picker and AI-assisted wording help, but no code access and no way to drag the layout apart. The editor changes content, not structure, which is why the design survives the client.
Then show them the editor once. Fifteen minutes on a call is enough: change a sentence, swap a photo, publish, done. A client who has changed one price themselves will never again email you about changing a price.
Tip: Make the first edit on that call something real: an opening time, a price. The handoff sticks once the client has published a change with their own hands.
Step 4: Stay connected for real changes, not typo tickets
Handing off does not mean disappearing. Your own access and your MCP connection keep working against the live site: new pages, new sections, SEO titles and descriptions, redirects. When the client wants a second landing page or a rebuilt offer section, that is a real job at your rate, from the same tool you built with.
Everything below that threshold no longer goes through you. Each publish regenerates sitemap.xml, robots.txt, canonical tags and llms.txt, so the technical SEO baseline holds itself. Plans start at 9 € per month (excl. VAT); details on the pricing page. Questions during a handoff: support@vibebridge.ai.
Frequently asked questions
How do you hand off a website your client can edit without handing over the code?
Publish the site to VibeBridge and invite the client. They edit text and images in the browser; the source code never changes hands. You keep MCP or API access for structural work: content is theirs, the build stays yours.
Can my client really not break the design?
The editor only lets them change content: text, images, colors of existing elements. They cannot edit code, delete sections or move the layout around. The worst they can do is write something you would have phrased better.
Who pays for the subscription, me or the client?
Both setups work. You can hold the account and bill the client as part of your service, or the client signs up and invites you as a team member. Plans start at 9 € per month (excl. VAT) with a 7-day free trial and monthly cancellation.
Can I manage several client sites?
Yes. Each client site runs on its own plan, and you can be a team member on all of them. One MCP connection works across the sites you have access to.
What if the client wants a bigger change later?
That is your job again, and a paid one. Make the structural change from your AI tool over MCP or upload the revised pages, and the client carries on editing content as before. Nothing about the handoff needs to be undone.
Does the client see leads and analytics too?
Yes. Form submissions land in a leads inbox with status, search and file attachments, and trigger an email notification. The built-in analytics is cookieless and first-party. Both live in the portal the client was invited to, with nothing extra to install.