Client site hosting for studios, on European infrastructure
A studio roster does not belong scattered across one hosting account per client. VibeDeploy puts every client site in one dashboard on EU infrastructure: an own domain with automatic SSL per client, preview links behind a password for sign-off, working contact forms and a DPA on every paid plan.
Deploys arrive however you work: from a Lovable project, a Claude artifact, or straight from Cursor or Claude over MCP, and a local build you upload yourself.
One dashboard for every client site
Deploy status, domains, SSL, snapshots and visibility settings for the whole roster sit side by side in a single view. There is no juggling a separate hosting login per client and no password spreadsheet. Plans scale by site count, so a growing roster is a plan change rather than a migration; the plan comparison shows what each tier holds.
Sign-off on the real site, behind a password
Sign-off works best on the real thing. Keep a new client site on With a password until launch, or put a redesign on a separate preview site, and the client reviews the actual pages in their own browser instead of a PDF of screenshots. Approval then means switching the site to Everyone, or deploying the approved build to the live site. Where several people review and no password should circulate, Invite only issues each of them a personal access link. Password and invitations alike are part of Maker and every tier above it.
Staging (Studio and above) gives a live site a second address for internal checks before promotion; it carries no password of its own, so client reviews belong on a protected preview site. Every access setting is described under private sites and client previews.
A real domain and SSL per client
Each client gets what they are paying you for: their own domain, served with a certificate that issues and renews itself. Point the domain at VibeDeploy with a CNAME, add it in the site settings, and SSL is live typically within minutes. Every site also keeps a free platform subdomain that doubles as a preview URL.
Contact forms that just work, no backend
The one thing nearly every client site must do is deliver an enquiry to an inbox. The built-in forms relay does exactly that for static sites: submissions from the contact form arrive at the address you configure, with no backend for you to host, patch or babysit per client. Should a project outgrow a form, the site can carry containers as well: an application server built from your code, Postgres, MySQL, Redis or background workers, started by your assistant with the MCP tool deploy_app and sandboxed by gVisor. Snapshots do not yet include what those containers store.
Rebuild their old site with the Website Converter
Taking over a client whose site dates from another decade? The Website Converter reads the existing site and produces a rebuild brief, real images included, ready for your AI tool to recreate as a modern static site that then goes live here. The migration guide walks through the takeover per platform.
When you grow: teams, approvals, audit log
The moment the studio is more than one person, invite teammates with roles. The Business tier layers governance on top: deploy approvals so nothing reaches a client production site without sign-off, an audit log recording who deployed what and when, and IP allowlisting for dashboard access. A DPA is included on every paid plan for the clients who ask about GDPR; the Business page details the governance set.
Pricing that maps to a client roster
Flat plans instead of usage meters: Maker for a first few sites, Studio for a working client roster with staging, Business for a large portfolio with team governance. VAT is included in the displayed price where it applies, every account begins with a 14-day trial without a card, and what you charge the client on top is your margin to set. Full details on the pricing page.
Frequently asked questions
Is it possible to charge the hosting on to the client?
It is, and most studios do exactly that. You hold the subscription and set your own price to the client, whether that is a straight pass-through or a managed-hosting margin inside a care plan. Nothing on the platform ties billing to the end client; the invoice you send them is entirely your business.
What access can the end client have?
Anything from none at all to full team membership. A client who wants visibility gets an invite to your team with an appropriate role; a client who prefers hands-off gets a password-protected preview link at review time and nothing else. Both are common setups and you can change your mind per client.
What does offboarding a client look like?
Three steps and no lock-in. The domain transfers to wherever the client goes next, the site files go with them as plain static assets, and the site itself is deleted from your dashboard. Files and domain move anywhere; for a site that runs containers, take your own export of their data first, since snapshots do not cover it yet.
Whose name should the client domain be registered in?
The client's, as a rule. Ownership registered in their name protects them if the relationship ever ends, while the DNS simply points at VibeDeploy for hosting. Agencies holding client domains in their own name is how hostage situations start; avoid being that story.
Talk it through
Bringing a studio's client roster across, or weighing which plan fits your volume? Write to us and we will work through it with you.
Put the whole roster on one platform
Studio covers a working client roster with staging and custom domains on EU infrastructure, and you can cancel from the dashboard at any time.
Or begin the 14-day trial first: one site, no card.