ChatGPT workflow

Take ChatGPT output live on EU infrastructure

OpenAI says ChatGPT Sites supports no data residency at launch, and that covers the deployed site, its code, its stored data and its logs. For a European organisation that is worth knowing before anything goes live. VibeDeploy is an alternative: the files ChatGPT writes are served from Belgium by a Belgian company, under Belgian and EU law, whichever ChatGPT plan produced them.

Why VibeDeploy for ChatGPT

Before a ChatGPT-built page collects a single email address, someone in a European business should ask three things: who processes the data, in which country, and under which contract. On ChatGPT Sites the answers are OpenAI, no residency commitment at launch, and OpenAI's terms for your plan. On VibeDeploy they are Tnet Comm.V, Belgium, and a DPA included with every paid plan, with the subprocessors listed publicly.

account_balance

A host your DPO can name

Tnet Comm.V, a Belgian company, runs the platform on its own cluster in Belgium. Every paid plan includes a DPA, and the eight subprocessors are published with their purpose and country.

shield_lock

Your site's files stay in Belgium

Pages are served from Belgium, and form submissions reach your inbox through a self-hosted mail server in Belgium instead of a form SaaS. The site's files pass no US processor unless you use the AI builder features.

content_paste

Publishing that ignores your ChatGPT tier

Sites is reserved for Plus, Pro and workspace plans. Uploads and the pasted deploy guide also work for output from ChatGPT Free and Go, so nobody needs a paid ChatGPT seat just to publish.

The ChatGPT to production workflow

  1. 1

    Let ChatGPT write the site

    Describe the page in any ChatGPT plan and let it produce the HTML, CSS and JavaScript. Nothing about the prompt changes because of where the site will be hosted.

  2. 2

    Open a trial on vibedeploy.eu

    Fourteen days, no card. The dashboard holds your deploy guide, labelled Magic File: a short markdown document with a private deploy key and the publishing instructions, which belongs in the chat and never in a public repository.

  3. 3

    Give ChatGPT the guide

    Paste it into the conversation and ask for a deploy. Depending on what the chat can do, ChatGPT pushes the files to VibeDeploy and returns the address, or produces a deploy page that publishes from your own browser with one click.

  4. 4

    Prefer manual? Upload instead

    Store the generated code as files and drag them into the dashboard: one HTML file, a folder or a ZIP archive. This path does not rely on any ChatGPT capability at all.

  5. 5

    Point your domain here

    Link the domain to your site in the dashboard, then publish the records it asks for at your DNS provider: a TXT entry proving ownership plus a CNAME, ALIAS or A record towards VibeDeploy. The certificate follows on its own, and name.vibedeploy.eu serves the site meanwhile.

Further reading on ChatGPT

ChatGPT hosting at a glance

How ChatGPT's default hosting and a generic alternative compare to VibeDeploy.

FeatureChatGPT SitesVibeDeploy
OperatorOpenAITnet Comm.V, Belgium
Where site data is keptResidency not offered at launchBelgium, on VibeDeploy's own cluster; restore points stay there too
Plans that can publishPlus, Pro and workspace plansOutput from any ChatGPT plan
Own domainWhere available; Enterprise workspaces excluded at launchIncluded, also during the trial
Changes before productionDeploys are production; save a version to review firstSeparate staging environment on Studio
Server-side componentsD1 and R2; some databases and background services unsupportedContainers via deploy_app (Postgres, MySQL, Redis, your own server)
Visitor accessOwner, invited viewers who sign in, workspace, or public where public publishing is enabledPublic by default; Maker and up include password and invite-only access

Common questions about deploying ChatGPT

Does ChatGPT Sites keep data in the EU?expand_more

Not as a commitment. OpenAI's help center says Sites does not support data residency or inference residency at launch, and names deployed Sites, Site code, D1 and R2 storage, artifacts and logs as covered by that statement. If EU residency is a requirement, publish the site somewhere that commits to it; on VibeDeploy the files are served from Belgium.

What should we check before a ChatGPT-built site goes live for a European business?expand_more

Who hosts it and in which country, which subprocessors can touch visitor data, whether a data processing agreement is in place, and where form submissions end up. On VibeDeploy: a Belgian operator, hosting in Belgium, eight subprocessors on a public list, a DPA with every paid plan, and form submissions emailed through a mail server in Belgium. Site files are stored and served in Belgium. The platform database, which includes the built-in visitor analytics, also runs in Belgium, on the same cluster that keeps its nightly backups.

Does hosting on VibeDeploy keep my build chats out of OpenAI's training?expand_more

No, the host cannot change that. How OpenAI uses your chats depends on your ChatGPT plan and data controls: OpenAI says conversations on Free, Go, Plus and Pro may be used for training when "Improve the model for everyone" is on, while Business and Enterprise conversations are not used by default. VibeDeploy only receives the files you deploy.

Which ChatGPT plans can publish this way?expand_more

All of them. Sites itself is limited to Plus, Pro and workspace plans, but the VibeDeploy route only needs the files: an upload works for output from any plan, and the pasted deploy guide either lets ChatGPT send the files or hands you a deploy page for your browser.

Can the site store data or run a backend?expand_more

Yes, beside the static site. VibeDeploy runs containers for a site in a gVisor sandbox (your own server, Postgres, MySQL, Redis or workers; up to 6 services sharing 2 CPU and 2 GiB), started by an AI agent through the MCP tool deploy_app. Inside ChatGPT, calling that tool takes MCP write permission, and OpenAI's help center says only Business, Enterprise and Edu plans have it for now. The containers run on the same cluster in Belgium, but their data is not yet part of snapshots.

Where does the site run, physically and legally?expand_more

Physically on VibeDeploy's own Kubernetes cluster in Belgium, a single region without a global edge network. Legally with Tnet Comm.V, whose terms are governed by Belgian law, inside the EU.

More tool workflows

Put your ChatGPT work into production

14-day free trial, no credit card. Your own domain and snapshots included. Runs on EU infrastructure.